If you haven’t realized already your Chrome browser is slowing down. Really, it is. The culprit of this particular browser rot is caused by the inordinate amount of disk fragments generated within the Chrome browser cache.

According to the bug reference published Jan 17, 2009, several users have reported this as a growing epidemic; some completely removing the web browser from their system to resolve their overall system degradation. All seem to point to the same source of their hard drive fragments; Google Chrome browser cache.

I too found it odd that Google Chrome cache files were always at the top of my list of files reported as the most fragmented. Literally hundreds to thousands of fragments can reside within a single Google Chrome cache file.

There seems to be no definitive answer from Google Chrome developers on this issue. It also appears that the issue is worse for Mac OSX users. As of right now, I’m using build 5.0.375.126 and just defragged my drive; fragments which mostly resided in the Chrome cache folder.

So I propose a test where browsers are speed tested after initial install. Tested again after significant browser usage (over 100 websites visited). Tested a 3rd time after the browser cache has been emptied (another 100 websites). Lastly, tested a 4th time after the hard drive has been defragmented. This should give us a good baseline to determine if the Chrome browser does indeed slow down due to disk defragmentation.

Tags: Buggy Software, Cache, Chrome, Google

This entry was posted on August 19, 2010 at 11:55 am. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Posted in Geektopia by RobK410 No Comments Yet