-
kasperl@chromium.org authored
it for scripts too. In the context of Chromium, this should have a very positive impact on memory consumption for web apps that run multiple tabs from the same domain with a lot of the same JavaScript code. For now, the cache retirement policy is really simple: Whenever a mark-sweep collection is started we clear the cache. This guarantees that this change will not have a huge negative impact on memory consumption, but it may not be ideal. We should consider a more sophisticated LRU scheme. Review URL: http://codereview.chromium.org/1933 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@270 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
b5a72a16
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
v8.xcodeproj | ||
visual_studio | ||
js2c.py | ||
linux-tick-processor.py | ||
presubmit.py | ||
splaytree.py | ||
test.py | ||
tickprocessor.py | ||
utils.py | ||
windows-tick-processor.py |