Comment #28 on issue 10727 by [email protected]: Very heavy cache-access makes for serious performance degradation http://code.google.com/p/chromium/issues/detail?id=10727
Yes, what you did should have been fine, and the result should not be affected by the lack of responsiveness that your system experience. The problem is that this particular measurement is taken only when the cache is going to evict entries so as a prerequisite the cache has to be full (hence the request to use the biggest saved cache). At that time, I'm trying to see if the cache is already busy to prevent adding extra load, and I'm also logging that load. A full cache (current vs max size from the stats) should probably feel the need to evict something when asked to load 40 tabs - unless everything is stored in the cache :(. I just wanted to see what was the number for your system, but it's not that big of a deal because we already know that the system is loaded by the time it takes to do stuff. I've been too busy with other stuff, but at some point we'll implement request throttling to avoid most of this issue. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
