Open Bug 1818467 Opened 3 years ago Updated 3 years ago

Memory telemetry should use existing background thread pool instead of the stream transport service's threadpool

Categories

(Core :: XPCOM, enhancement)

Product:
Core
Component:
XPCOM
Type:
enhancement

Tracking

()

People

(Reporter: Gijs, Unassigned)

Details

https://searchfox.org/mozilla-central/rev/75da1dd5d4b9b991f919a41594194eab93cdef62/xpcom/base/MemoryTelemetry.cpp#269-297

I think we can just use NS_DispatchBackgroundTask with the existing runnable.

As it is, perf profiles indicate we spin up a new thread on the transport service to service the runnable, which seems overkill.

Moving this to the component owning the instrumentation (see bug 1779138 et al)

Type: defect → enhancement
Component: Telemetry → XPCOM
Product: Toolkit → Core
You need to log in before you can comment on or make changes to this bug.