Open
Bug 1907364
Opened 2 months ago
Updated 1 month ago
ProxyResolution thread can use significant CPU on high request documents
Categories
(Core :: Networking: Proxy, enhancement, P2)
Core
Networking: Proxy
Tracking
()
NEW
People
(Reporter: acreskey, Unassigned, NeedInfo)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [necko-triaged][necko-priority-next] )
It was observed in Bug 1904284 that we can spend a lot of CPU cycles in the ProxyResolution thread if there are a lot of requests.
Profile: https://share.firefox.dev/4bGMGZk
Kershaw suggest that we could optimize this as we did in bug 1392272 (reverted in bug 1749501):
However, I do see an opportunity here. From the all-thread sample, I notice that the ProxyResolution thread uses ~30% CPU resources. I think it would be beneficial to revisit bug 1392272 (which was reverted in bug 1749501) to avoid reading system proxy settings for every HTTP request.
|
Reporter | |
Updated•2 months ago
|
Blocks: necko-perf
See Also: → 1904284
|
||
Updated•2 months ago
|
Severity: -- → N/A
Points: --- → 8
Rank: 2
Priority: -- → P2
Whiteboard: [necko-triaged][necko-priotity-review]
|
||
Updated•2 months ago
|
Whiteboard: [necko-triaged][necko-priotity-review] → [necko-triaged][necko-priority-review]
|
||
Updated•2 months ago
|
Flags: needinfo?(kershaw)
|
||
Updated•1 month ago
|
Whiteboard: [necko-triaged][necko-priority-review] → [necko-triaged][necko-priority-next]
You need to log in
before you can comment on or make changes to this bug.
Description
•