769796 - Remove fetchCount and lastFetched information from all cache entries

Status: NEW

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

Description

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

Since we update these properties every time a cache entry is read, we end up having to write the cache entry's metadata back out to disk. Since this information is low-value (AFAICT), and expensive to update on disk, we should just remove it.

Comment 1

[Honza Bambas (:mayhemer)]

I was hoping to use this information for better eviction politic and weighting of potential 304 response.  BTW, aren't these metadata already used for something like this?

Comment 2

[Thinker Li [:sinker]]

If we still need this for something like eviction, we can reduce the impact comes with updates by writing back lazily.

Comment 3

[Honza Bambas (:mayhemer)]

(In reply to Thinker Li [:sinker] from comment #2)
> If we still need this for something like eviction, we can reduce the impact
> comes with updates by writing back lazily.

I have no problem with that.

Comment 4

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 5

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 6

[Jens Stutte [:jstutte]]

Bulk-downgrade of unassigned, untouched DOM/Storage bug's priority.

If you have reason to believe, this is wrong, please write a comment and ni :jstutte.