Open
Bug 1347223
Opened 8 years ago
Updated 2 years ago
Prioritize cache requests for the active tab
Categories
(Core :: Networking: Cache, enhancement, P5)
Core
Networking: Cache
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: mayhemer, Unassigned)
References
Details
(Whiteboard: [necko-next])
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.
Reporter | ||
Updated•8 years ago
|
Assignee: nobody → honzab.moz
Whiteboard: [necko-active]
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Comment 1•8 years ago
|
||
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.
Reporter | ||
Comment 2•8 years ago
|
||
Releasing this bug for the moment. I'll try to find an owner.
Assignee: honzab.moz → nobody
Reporter | ||
Updated•8 years ago
|
Whiteboard: [necko-active]
Reporter | ||
Updated•8 years ago
|
Whiteboard: [necko-next]
Reporter | ||
Updated•8 years ago
|
Priority: -- → P4
Comment 3•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P4 → P2
Comment 4•7 years ago
|
||
(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?
Reporter | ||
Comment 5•7 years ago
|
||
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
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•