Closed Bug 111036 Opened 23 years ago Closed 22 years ago

Cache DOM and layout in addition to page source

Categories

(Core :: Layout, enhancement, P4)

x86
Linux
enhancement

Tracking

()

RESOLVED DUPLICATE of bug 84286
Future

People

(Reporter: zlynx, Assigned: attinasi)

Details

(Keywords: helpwanted, perf, Whiteboard: [bae:20011211])

I think it would speed up cache hits on large pages quite a bit if the HTML
render and DOM processing didn't need to be done each time.  If all the
information needed to render the document was also saved in the cache then
document processing could start from that point.

I can see that this isn't being done now because when I load a page with a very
long table from cache, I can see the columns adjusting themselves as rows with
unusually wide columns are loaded.  The page takes 10 seconds to load without
cache and still takes 6 seconds to load with cache.  Internet Explorer on
similar hardware (actually, a VMware session) can load the same page from cache
in less than 2 seconds.
Changing component and owner.
Assignee: gordon → attinasi
Component: Networking: Cache → Layout
QA Contact: tever → petersen
This might be related to bug 33269.
Keywords: perf
This seems like a footprint nightmare....

Note that we do not cache HTML in the memory cache (just in the disk cache) so
this could be a large part of the difference you see... (yes, there is a bug on
this, no I don't have the number offhand).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Target Milestone: --- → Future
adding the helpwanted keyword to see if someone in mozilla could jump in and 
help on this one, otherwise it may take some time for the assigned engineer to 
review this request.
Keywords: helpwanted
Priority: -- → P4
Whiteboard: [bae:20011211]
This would be a duplicate of bug 38486, except this bug refers to the cache in
general whereas 38486 is just about the memory cache.
Keywords: mozilla1.0+
I strongly recommend that we NOT try to get this change made for Mozilla 1.0

Aside from the fact that we ar lacking resources to do it, it would potentially
destabilize Gecko, and would have potential memory footprint issues that we have
not even begun to explore yet.

By what criterion was this marked Mozilla1.0+ anyway?  It is currently marked
'future, enhancement, P4'.
Keywords: nsbeta1-
This bug sounds very similar to Bug 84286, should one of these get duped?
not gonna happen for 1.0
Keywords: mozilla1.0+mozilla1.0-

*** This bug has been marked as a duplicate of 84286 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
No longer blocks: 33269
You need to log in before you can comment on or make changes to this bug.