Closed
Bug 1267904
Opened 9 years ago
Closed 9 years ago
Add telemetry for WorkerMainThreadRunnable
Categories
(Core :: DOM: Workers, defect)
Core
DOM: Workers
Tracking
()
RESOLVED
FIXED
mozilla49
Tracking | Status | |
---|---|---|
firefox49 | --- | fixed |
People
(Reporter: ehsan.akhgari, Assigned: baku)
Details
(Whiteboard: [tw-dom] btpp-active)
Attachments
(1 file)
23.46 KB,
patch
|
khuey
:
review+
|
Details | Diff | Splinter Review |
We need to start collecting telemetry for MainThreadWorkerControlRunnable to measure how long various things that we proxy to the main thread take in the wild. Based on this we can get information about what cases are real world performance issues that we need to fix.
I'm imagining that we'd make the consumer of MainThreadWorkerControlRunnable pass in an identifier of some sort so that we can differentiate between the telemetry histograms for all of the consumers, both existing ones and the ones that we add in the future. The ID can just be the histogram ID.
Updated•9 years ago
|
Whiteboard: [tw-dom]
I don't know what you think you are measuring but MainThreadWorkerControlRunnable is almost certainly not what you want.
Reporter | ||
Comment 2•9 years ago
|
||
The goal is to measure how long it takes to proxy work to the main thread and get the results back on the worker side. Baku suggested this class, if this isn't the right place can you please update the summary to make it point to the right thing? Thanks!
Well there's not just one class to look at ... But WorkerControlRunnables are used for bookkeeping, not script observable functionality, and MainThreadWorkerControlRunnable is just a WorkerControlRunnable that can be dispatched from the main thread (instead of the parent thread).
I'd start by looking at every time we spin up a sync loop, but there is probably more than just that do be done.
Assignee | ||
Comment 4•9 years ago
|
||
Assignee: nobody → amarchesini
Attachment #8746172 -
Flags: review?(khuey)
Updated•9 years ago
|
Whiteboard: [tw-dom] → [tw-dom] btpp-active
Summary: Add telemetry for MainThreadWorkerControlRunnable → Add telemetry for WorkerMainThreadRunnable
Comment on attachment 8746172 [details] [diff] [review]
tele.patch
Review of attachment 8746172 [details] [diff] [review]:
-----------------------------------------------------------------
::: dom/workers/WorkerRunnable.cpp
@@ +585,5 @@
> WorkerMainThreadRunnable::Dispatch(ErrorResult& aRv)
> {
> mWorkerPrivate->AssertIsOnWorkerThread();
>
> + TimeStamp startTime = TimeStamp::Now();
NowLoRes?
::: dom/workers/WorkerRunnable.h
@@ +444,5 @@
>
> private:
> NS_IMETHOD Run() override;
> +
> + const nsCString mTelemetryKey;
Place this with the other member variables above please.
@@ +464,1 @@
> {}
Please move this ctor out of line into WorkerRunnable.cpp
::: toolkit/components/telemetry/Histograms.json
@@ +10594,1 @@
> }
I don't know enough about this to know whether this is right or not ... but it looks reasonable ...
Please add khuey@mozilla.com to the alert_emails.
Attachment #8746172 -
Flags: review?(khuey) → review+
Comment 7•9 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox49:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
You need to log in
before you can comment on or make changes to this bug.
Description
•