Bug 67325
| Summary: | By default, WebKit2 has an enabled but 0-capacity page cache, which results in unnecessary work on many navigations | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Adam Roben (:aroben) <aroben> |
| Component: | WebKit Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ap, bdakin, beidson, ggaren, sam |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Adam Roben (:aroben)
WebKit2 defaults to having the page cache enabled. It also defaults to CacheModelDocumentViewer, which specifies that the page cache's capacity should be 0. This means that on most navigations we create a CachedPage and then immediately destroy it. This seems silly, and might also have a negative effect on performance.
I haven't looked to see whether WebKit1 has the same issue, but it seems likely.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |