Right now, the persistent cache uses a single disk file to store the content of each cached URL. As a result, a page with lots of images may need to open and read dozens of cache files. Due to a low-performance filesystem, this is especially slow on the Mac - my benchmarks show that the 4.x cache is almost two orders of magnitude slower on the Mac then on NT. Also, since most web files are small (less than 15K), the cache generates thousands of tiny files, increasing disk fragmentation and reducing storage efficiency (since small file sizes are rounded up to the disk's block size). A solution would be to create a single "flat" database file that stored all cached content. The flat database would need to handle multiple simultaneous writes, meaning that the stored data for one URL will not be guaranteed to be contiguous. It must also be able to append to cached content and truncate content to a specified length. This essentially amounts to a filesystem-within-a-filesystem. The full API specifications can be found here: http://lxr.mozilla.org/seamonkey/source/netwerk/cache/public/nsINetDataCache.idl http://lxr.mozilla.org/seamonkey/source/netwerk/cache/public/nsINetDataCacheReco rd.idl

Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache component.

Assigning fur's cache bugs to Gordon. He can split them up with davidm.

Moving post beta bugs to M18 which is now the post-beta milestone.

Moving to target milestone FUTURE.

Marking this a dup of bug 72507 *** This bug has been marked as a duplicate of 72507 ***

Verified dupe