Closed Bug 21258 Opened 25 years ago Closed 23 years ago

Support multiple physical caches with one logical cache entry

Categories

(Core :: Networking: Cache, defect, P3)

defect

Tracking

()

VERIFIED INVALID
Future

People

(Reporter: fur, Assigned: gordon)

References

Details

(Keywords: perf)

Writing to a cache entry either writes to the memory cache or the disk cache,
but not both.  Particularly on the Mac, the memory cache is far, far faster than
the disk cache.  We could benefit a lot from writing to both the memory cache
and the disk cache at the same time.  When locating cached content, we would
check the memory cache first and then look in the disk cache.

Also, a cache entry cannot refer to a different underlying cache for reading and
writing.  The search order when locating a URI in the cache should be:

  1) Memory Cache
  2) Disk Cache
  3) Read-only extension cache, e.g. CD-ROM cache

But, the cache that is written into should be independent of which cache data is
read from.  For example, a cache read might read something from the CD-ROM
cache, but a subsequent write to the same logical cache entry might go into the
memory cache or the disk cache.
Blocks: 20845
Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache
component.
Target Milestone: M15
Can be done after beta.
Assigning fur's cache bugs to Gordon. He can split them up with davidm.
Keywords: perf
Summary: [Perf] Support multiple physical caches with one logical cache entry → Support multiple physical caches with one logical cache entry
Target Milestone: M15 → M17
Moving post beta bugs to M18 which is now the post-beta milestone.
Target Milestone: M17 → M18
Target Milestone: M18 → Future
*** Bug 73932 has been marked as a duplicate of this bug. ***
This was one suggestion for improving performance using the old cache
architecture.  The new cache has it's own set of performance bugs.  Marking INVALID.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
VERIFIED:
gone
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.