FollowupID: 543568 Submitted:
Wednesday, Jan 02, 2008 at 18:17
ExplorOz Team - David posted:
Hi John,
I found out in many corporate environments that high cache values caused performance degradation due to the time it took for the cache lookups to complete. Some machines local processing of large caches takes ages (I have seen some more than 1/2 sec) hence several hundred image objects on a page will cause a cache lookup for every image so every 50 little 1KB images in a large cache using worst figures (from my testing) can take 25 seconds or more just to perform local cache lookup - then download if non existant or render from cache.
About 8 months ago MS changed the recommendation to less than 250MB (as shown on the IE settings page).
The other logic is that you should not really be carrying that much cache as most of it will be out of date anyway and require re-download so the extra lookup time is realy a waste. I setup 150 to 250MB on all my systems and on most of my client networks, sometimes even less down to 10-50MB on some networks. It all depends on the network however there is NO reason for a small business/home machine to have a setting larger than 250MB.
IE6 used a percentage of disk space and when you upgrade to IE7 it keeps that figure. We must remember IE6 was released in the time of 20GB being a huge disk drive and settings of percent were 5-10% now 200GB is average and the caches have become way to large.
Anyway hope this helps and explains it a little.
 Click Image to Enlarge |
| David (DM) & Michelle (MM)
------------------------------------------------
Always working, not enough travelling ;-) |