Open
Bug 1821691
Opened 1 year ago
Updated 1 month ago
Cancel remaining timers when http connections are all resolved
Categories
(Core :: Networking: HTTP, enhancement, P3)
Core
Networking: HTTP
Tracking
()
NEW
Performance Impact | low |
People
(Reporter: jesup, Unassigned)
References
(Depends on 1 open bug, Blocks 3 open bugs)
Details
(Keywords: perf:resource-use, Whiteboard: [necko-triaged][necko-priority-next])
https://share.firefox.dev/3yv1dWG
This shows a number of timers that should be possible to remove once the http connections are all resolved.
This can reduce power usage in idle cases (especially on mobile, but also probably laptops).
This would fall into the performance and tech-debt categories
Reporter | ||
Updated•1 year ago
|
Performance Impact: --- → ?
Comment 1•1 year ago
|
||
Here is a profile where the 'AddTimer' markers have stacks for the 'nsHttpConnectionMgr' timers: https://share.firefox.dev/3ZVF67x
Blocks: power-usage
Updated•1 year ago
|
Updated•1 year ago
|
Whiteboard: [necko-triaged]
Reporter | ||
Comment 2•1 year ago
|
||
Likely we'll need to retain one timer to close the socket after <whenever>
Comment 3•1 year ago
|
||
I can't see anything here hinting about meaningful performance impact. Clearing the flag
Performance Impact: ? → ---
Comment 4•1 year ago
|
||
ok, perhaps impact: low. The calculator isn't really good with this kinds of issues.
Performance Impact: --- → low
Keywords: perf:resource-use
Updated•9 months ago
|
Whiteboard: [necko-triaged] → [necko-triaged][necko-priority-next]
Updated•1 month ago
|
Points: --- → 8
You need to log in
before you can comment on or make changes to this bug.
Description
•