зеркало из https://github.com/mozilla/gecko-dev.git
ab686fa4f7
If all sampling-related features ("Native Stacks", "JavaScript", and "Native
Leaf Stack") are OFF, the sampler loop will not record any stack samples, not
even from labels, which should reduce the profiler overhead significantly.
This means that the sampling rate could be slowed down (up to 5s interval), to
help reduce the power consumption incurred by wake-ups for sampling.
Markers are not affected by this, and will all be recorded as expected.
However counters (e.g., memory allocations) are still tied to sampling, so their
sampling resolution will be reduced to whatever sampling rate is chosen.
Some existing tests relied on stack sampling happening, so they now enable at
least "leaf". Bug 1579333 may revisit these tests for a better solution (if
possible).
Differential Revision: https://phabricator.services.mozilla.com/D46753
--HG--
extra : moz-landing-system : lando
|
||
|---|---|---|
| .. | ||
| BlocksRingBufferGeckoExtensions.h | ||
| ChildProfilerController.h | ||
| GeckoProfiler.h | ||
| GeckoProfilerReporter.h | ||
| ProfileJSONWriter.h | ||
| ProfilerChild.h | ||
| ProfilerCodeAddressService.h | ||
| ProfilerCounts.h | ||
| ProfilerMarkerPayload.h | ||
| ProfilerParent.h | ||
| shared-libraries.h | ||