Comment #31 on issue 10727 by stolsvik: Very heavy cache-access makes for serious performance degradation http://code.google.com/p/chromium/issues/detail?id=10727
Any progress on this? Question: Do you guys at Google working on Chrome have SSD drives or similar superfast stuff? Or maybe you have 8 GB memory? Or maybe you ONLY work on Chrome, so that the OS can use all of its 2 GBs on disk cache? See, .5 GB and plenty above which must be ground through on every open of a tab, on every load of an image, or WHATEVER like this, is WAY TOO MUCH. The size of the caches SLAMS upwards right after I've deleted ALL the databases - they end up on hundreds of megs after opening just a couple of hundred pages. Even with whatever indexing you can come up with, this WILL be problematic, if I have any idea of how a database works with its files: You might find _where_ all the different data resides with only one or two reads - or maybe all the indices are cached. BUT, then you actually have to read it off of the disk. And as long as you don't have plenty of memory laying around, this WILL lead to the hard disk having to move its head to the correct cylinder and wait for the sector to pass under its read head. I can't seem to find a simpler way to try to convey this: .5 and way above files WILL lead to thrashing on every fetch, and VERY degraded performance, unless you have extremely fast hardware, or very much RAM. -- 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 -~----------~----~----~----~------~----~------~--~---
