Open
Bug 1307504
(RCWN)
Opened 8 years ago
Updated 20 days ago
[meta] Tracking bug for network/cache racing
Categories
(Core :: Networking: Cache, task, P5)
Core
Networking: Cache
Tracking
()
NEW
People
(Reporter: mayhemer, Unassigned)
References
(Depends on 9 open bugs)
Details
(Keywords: meta, Whiteboard: [necko-quantum][necko-active])
Attachments
(1 obsolete file)
This bug is more about telemetry collection and establishing any decision logic on whether to load from network despite we have a (enough) fresh content in the cache when there is a good chance it would be faster when rather reload from the network (w/o revalidation). The simple start would be to have a new probe that shows a distribution between cache load time and network load time, both happening in parallel, broken by some basic set of preconditions we happen to know about the loading resource, like: priority class, estimated content type, size, ...? and maybe also: connection RTT, if known at the time of the request, connection type, ...?
Reporter | ||
Comment 1•8 years ago
|
||
After discussion in Vienna, we may have some more detailed plan. Let's use this as a tracking bug for all the particular tasks.
Assignee: nobody → honzab.moz
Summary: Experiment with racing network request against cached load → Tracking bug for network/cache racing
Whiteboard: [necko-active]
Reporter | ||
Comment 2•8 years ago
|
||
Sorry, wanted to assign to Michal (leader of this project)
Assignee: honzab.moz → michal.novotny
Updated•7 years ago
|
Whiteboard: [necko-active] → [necko-quantum][necko-active]
Comment 3•7 years ago
|
||
Bulk priority update: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Updated•5 years ago
|
Summary: Tracking bug for network/cache racing → [meta] Tracking bug for network/cache racing
Updated•5 years ago
|
Priority: P1 → P3
Updated•3 years ago
|
Assignee: michal.novotny → nobody
Severity: normal → N/A
Priority: P3 → --
Updated•3 years ago
|
Type: defect → task
Priority: -- → P5
Comment hidden (spam) |
Updated•20 days ago
|
Attachment #9383862 -
Attachment is obsolete: true
You need to log in
before you can comment on or make changes to this bug.
Description
•