https://issues.apache.org/ooo/show_bug.cgi?id=124313

Armin Le Grand <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #3 from Armin Le Grand <[email protected]> ---
The unusual thing about that SVG is that it uses 146 clip-path definitions, it
looks as if every single graphic component is clipped against the world. This
means that for every repaint all this 146 clip regions have to be set up and
clipping is an expensive operation.
I have experimentally taken out all 146 clip usages from the file and it looks
exactly the same, being much faster in handling (as fast as expected). I would
suggest that software creating SVG should only create clip regions which are
really needed (which are actually clipping something).
The 2nd possibility is to check all clip regions to be applied at SVG import if
they actually clip something at all, but this is a 2nd level approach and will
increasle SVG import fore evervone; avoiding creating unnecessary clip actions
initially would of course be much better and would create smaller, more
effective SVG files, too.
Nonetheless all is interpreted correctly and the SVG is a correct SVG, too. For
AOO rendering/cost of clipping may get less with system-dependent renderers in
the future.

So we have three aspects:
- Supefluous clip-path statements which (obviously) clip nothing -> should not
be created
- Possibility to detect these at SVG import and to not apply them -> will
increase SVG import time for everyone
- Possibility to speedup clip region operations -> possible in the future

I am not sure what to do here. Even when opening the orig and my modded test
version in FireFox you can see a remarkable slowdown with the original. The
GeoGebra developers should be noted to create only needed clip regions.

@Regina: Do you have contact to that guys, or can you check if their SVG
creation evtl. has options to not create clip-path's for every graphic element
by default which always seem to include the whole graphic?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.

Reply via email to