Bug 24627
| Summary: | Large SVG documents have performance issues | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Kevin Ballard <kevin> |
| Component: | SVG | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | bfulgham, emacemac7 |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Mac | ||
| OS: | OS X 10.5 | ||
| URL: | http://code.haskell.org/~dons/images/svg/hackage-circo.svg | ||
| Bug Depends on: | 14015 | ||
| Bug Blocks: | |||
Kevin Ballard
Rendering a large SVG document in WebKit has irritating performance implications. The following document was used to observe this behavior:
http://code.haskell.org/~dons/images/svg/hackage-circo.svg
(there are some other large SVG documents in the same directory)
Any attempt to interact with the page causes a significant CPU spike. For example, clicking away to another app causes a second delay before the window deactivates (and similarly for reactivating). Even just clicking causes a CPU spike even though the document doesn't define any click handling.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Eric Seidel (no email)
I think this is partially due to https://bugs.webkit.org/show_bug.cgi?id=14015 (we seem to be painting more than we're displaying?). It's also probably partially due to the SVG depending on stroke hittesting. Or at least we seem to be hit-testing some path's stroke quite a bit, which is slow.
Eric Seidel (no email)
We also seem to hit-test the SVG every time, even if the hittest result isn't needed. I think the major slowness seen in mouse-move is due to the fact that we're hit-testing every time. We could invent a solution where the hit-testing wasn't done until the result was needed.
Brent Fulgham
It's difficult to confirm this bug without a test case. We don't believe there is an ongoing issue here. If you do feel there is a problem, please REOPEN this bug and include a test case illustrating the issue.