Open Bug 1821691 Opened 2 years ago Updated 3 months ago

Cancel remaining timers when http connections are all resolved

Categories

(Core :: Networking: HTTP, enhancement, P3)

Product:
Core
Component:
Networking: HTTP
Type:
enhancement
Points:
8

Tracking

()

Project Flags:
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-queue])

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

Performance Impact: --- → ?

Here is a profile where the 'AddTimer' markers have stacks for the 'nsHttpConnectionMgr' timers: https://share.firefox.dev/3ZVF67x

Blocks: power-usage
Blocks: necko-tech-debt, necko-perf
Severity: -- → N/A
Priority: -- → P3
Whiteboard: [necko-triaged]

Likely we'll need to retain one timer to close the socket after <whenever>

I can't see anything here hinting about meaningful performance impact. Clearing the flag

Performance Impact: ? → ---

ok, perhaps impact: low. The calculator isn't really good with this kinds of issues.

Performance Impact: --- → low
Keywords: perf:resource-use
See Also: → 1829841
Duplicate of this bug: 1829841
Whiteboard: [necko-triaged] → [necko-triaged][necko-priority-next]
Depends on: 1889621
Points: --- → 8
Whiteboard: [necko-triaged][necko-priority-next] → [necko-triaged][necko-priority-queue]
You need to log in before you can comment on or make changes to this bug.