[deepak-kumar]

I used to be a Firefox fan but not anymore, I made chrome my default browser and I am highly satisfied. Now I use FF just to test while developing things. I love lightness of chrome and have shifted all dev related work to chrome. I wont be surprised if chrome becomes the first choice all the developers in next couple of years.

[venomsnake]

On a side note the only problem i had with chrome is that you cannot disable disk cache. The problem was easily solved with junctions to /Device/Null for the Cache and MediaCache folder.

[robocat]

Not sure if this is valid but:

User Bapabooiee:

Well, you guys are in luck (BTW, great work-around, Xenofon), since Chrome now has two startup switches that you can use:

--disk-cache-dir and --disk-cache-size

Simply close Chrome, right-click your Chrome shortcut, click Properties, and then in the field labeled "Target:", make it look something like this:

"...chrome.exe" --disk-cache-dir="CACHE_DIR" --disk-cache-size=N

Where 'CACHE_DIR' is the new cache location, and 'N' is the cache size limit, in bytes.

Use whichever switch you need, or both. Keep in mind, however, that these features may not be completely stable yet. But you probably shouldn't have any problem with using them.

And to anyone who's interested, I caught gander of the existence of these switches directly from a source code file for Chrome. See here:

http://src.chromium.org/svn/trunk/src/chrome/common/chrome_s...

Hope this helps!

[forgotAgain]

Thanks! I'm trying it now. The caching directives work. Hopefully this will fix the performance issues I've been seeing with Chrome the past two months.

The issues I'm talking about are constant disk access and freezing the entire machine when I open multiple tabs simultaneously.

[jonknee]

You can disable cache though, is that not what you wanted?