Comment 5 for bug 523285

Watching the PDF created with Inkscape 0.47 loading in the PDF viewer I can see that it takes a long time until every tiny clipped symbol of the diagram is calculated, clipped and finally rendered - it is almost an animated view of the PDF structure ;-).

What I fail to understand looking at the way the diagram in the SVG file is structured: there are 8198 tiny symbols (line, rect, circle and polygon entities) and each of it is clipped with a huge rectangular path of the size of the diagram itself (clipPath23). Depending how cairo export handles clip-paths (the structure could possibly trigger a bug in the export function) that means there are ~8200 big rectangles on top of each other, not visible in the end because the object they clip is much, much smaller. (I can't think of a reason why one would create this kind of inverted logical structure with Inkscape itself: (big) object A is clipped with (transformed or smaller) object B so that the clip-path B limits the rendered contents of object A to a certain region. I could be wrong though ;-)

The same structure is used for all labels (clipped lines and clipped text objects) of the x and y axis, but not for the legend (probably the part created with Inkscape).