Closed Bug 77218 Opened 24 years ago Closed 24 years ago

Disk cache and memory cache settings are the same as 4.x in 1997

Categories

(Core :: Networking: Cache, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED FIXED
mozilla0.9.1

People

(Reporter: hyatt, Assigned: hyatt)

References

Details

Our default disk cache and memory cache sizes are ridiculously low. We're still using the same settings used by 4.0 in 1997 in an age of 500mb hard drives and 32mb of memory. I'm filing this bug to make sure we increase both cache sizes to take advantage of the fact that most people (even on 266mhz or lower) machines have plenty of disk and memory. I'd suggest raising the memory cache to 4096 MB and the disk cache to 50 MB.
I'd like to suggest that the disk cache setting reflect actual disk space used, though, at least on Windows systems. For example, if I have 10 files in my cache, each 100 bytes in size, it seems to me that Mozilla (and Netscape 4.x), treats this as 10 * 100 = 1000 bytes. But because of the FAT file system, this may actually be 10 * 4K = 40Kbytes. So if the disk cache limit were raised to 50MB, I would hope that this is *really* 50MB. In summary, instead of using a file's size when doing the calculations, I'd like to see the size rounded up to the next multiple of the cluster size.
my suggestion is to move mem-cache default size to 5meg (with a 4meg softlimit) and move the disk cache up to 50 Meg and additionally support a small configurable % of an increasingly growing hard disk :-)
The one problem I have with using a percentage of disk space is the same one I have with the Windows trash can. Namely, with a big enough disk, even 1% may be more than I actually want to allocate. Unless you want to get into fractional percentages :)
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.1
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
They have plenty of memory if they're running Mozilla! ;)
Blocks: 56612
I hope the origonal reporter is kidding about 4096MB mem-cache sizes. Must be running on a 64-bit machine ;-) Anyway, isn't this better solved by running a webcache, e.g., squid alongside? Or at least by benchmarking --- I doubt a 4GB mem-cache will do any good, especially in the days of fast disks. Perhaps with 80GB disks these days, we ought to allow a different strategy: Allow the cache to grow boundlessly, but prune objects that have not been used in the last x days. There is really no much reason to worry about the size of your web cache if you have 70GB of free space on your drive.
default sizes have been set to 4M mem and 40M disk last I checked verified
Status: RESOLVED → VERIFIED
*** Bug 193911 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.