Comment #32 on issue 10727 by stolsvik: Very heavy cache-access makes for serious performance degradation http://code.google.com/p/chromium/issues/detail?id=10727
What about introducing timers for all type of operations? (Maybe a bit like java does with its "target based garbage collection metrics" or whatever they're called): Start, when the browser is fresh, to collect statistics for all types of operations, particularly fetching a file (from the time it was first requested to it is fully available, however it is fetched). Then, when the cache starts to fill, one would assume these times (averages, obviously) should become LOWER. Once this isn't true anymore, that the times that operations are taking starts to edge HIGHER, the cache size is optimal, or should be lowered (E.g. as java apparently does with its heap if you target low gc pauses?). The system should obviously not stop there: Since things can change - maybe the network was saturated, maybe lots of other stuff was going on on the machine - this process should go on all the time, so that the operations-time-minima continuously is located. Hopefully the minima is a wide U-like thing, so that one can skate up and down in the pipe continuously without the user being much affected. (Obivously, for the sake of mankind on a global scale, all things being equal, a bigger cache is preferred to using the network - so let this skating hover more to the "big cache" than to the "more network" side of the U) -- 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 -~----------~----~----~----~------~----~------~--~---
