Bug 100880
| Summary: | Try to avoid computing overlap rectangles if we are not testing overlap | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ahmad.saleem792, eric, tonikitoo, zalan |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://ie.microsoft.com/testdrive/performance/robohornetpro/ | ||
Simon Fraser (smfr)
Bug 98800 shows lots of time spent computing overlap regions, but we never actually test against them in this case. Should figure out if we can avoid computing them in the first place.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ahmad Saleem
Test Case - https://testdrive-archive.azurewebsites.net/performance/robohornetpro/
It is pretty fast now a days:
Chrome Canary 111 - 3.4xx seconds
Safari Technology Preview - 3.12 seconds
Firefox Nightly 110 - 1.75w seconds
Do we need to tweak it further?