Open Bug 1347223 Opened 8 years ago Updated 10 months ago

Prioritize cache requests for the active tab

Categories

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

enhancement

Tracking

()

Tracking Status
firefox55 --- affected

People

(Reporter: mayhemer, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Since this can change at runtime, we can't just add another queue for the active tab. We must pick events by handle status which must be added a toplevel win id. This is just a quick thought, tho.
Assignee: nobody → honzab.moz
Whiteboard: [necko-active]
See Also: → 1348242
Impl details: the event queue will move to file handle. we will pick handles by priority (multiple factors) and execute the event first in the queue on a proper thread. There will not be possible to run more than one event of the same handle at the same time. But events from multiple handles may run concurrently on other threads.
Releasing this bug for the moment. I'll try to find an owner.
Assignee: honzab.moz → nobody
Whiteboard: [necko-active]
Whiteboard: [necko-next]
Priority: -- → P4
No longer blocks: CDP
Priority: P4 → P2
(In reply to Honza Bambas (:mayhemer) from comment #1) > Impl details: the event queue will move to file handle. we will pick > handles by priority (multiple factors) and execute the event first in the > queue on a proper thread. There will not be possible to run more than one > event of the same handle at the same time. But events from multiple handles > may run concurrently on other threads. Hey I would love to work on this, could you nudge towards relevant code/homework?
Hi, thanks for the offer, however, this bug will be fixed as part of a larger effort that has not been planned yet. We want to design even smarter queuing for cache requests regarding not only active tab activeness but also according the original request priority and number of other factors. hence, for now, this is a very low priority bug for Necko.
Priority: P2 → P5
Severity: normal → S3
Whiteboard: [necko-next] → [necko-triaged]
Blocks: necko-cache
You need to log in before you can comment on or make changes to this bug.