Summary: | Add performance tests for URL parsing | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> | ||||
Component: | New Bugs | Assignee: | Eric Seidel (no email) <eric> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | abarth | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Other | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Eric Seidel (no email)
2011-02-05 02:54:56 PST
I'm omitting the urls file from the uploaded patch since it's too big. :( Created attachment 81352 [details]
Patch
Committed r77739: <http://trac.webkit.org/changeset/77739> Some figures: We call KURL::parse() about 2000 times when loading gmail.com (a logged in account). Since our benchmark parses apple.com 200000 times in under 400ms, it seems URL parsing is not a huge perf concern at the moment. Based on those numbers, we're spending about 4ms in URL parsing while loading gmail (that's a very rough estimate). Or using the figures from the english url corpus, a rough estimate of time spent loading gmail parsing urls would be 6.5 ms. In either case, these are not huge numbers. |