Comment #36 on issue 10727 by stolsvik: Very heavy cache-access makes for serious performance degradation http://code.google.com/p/chromium/issues/detail?id=10727
Just posting back that with 32MB disk cache size using the command line arg mentioned in comment 16 (--disk-cache-size=33554432), and some version 4, I find that Chrome handles very good! (I don't know whether it is the command arg or version 4 that does the real fixin', though..!) Google Chrome 4.0.223.16 (Official Build 30555) WebKit 532.3 V8 1.3.16.1 User Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/532.3 (KHTML, like Gecko) Chrome/4.0.223.16 Safari/532.3 -- 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 -~----------~----~----~----~------~----~------~--~---
