Closed
Bug 668355
Opened 12 years ago
Closed 12 years ago
Measure plugin enumeration with telemetry
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla7
People
(Reporter: taras.mozilla, Unassigned)
References
Details
(Whiteboard: [inbound])
Attachments
(2 files, 2 obsolete files)
826 bytes,
patch
|
taras.mozilla
:
review+
|
Details | Diff | Splinter Review |
2.16 KB,
patch
|
justin.lebar+bug
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Reporter | ||
Comment 1•12 years ago
|
||
Attachment #542953 -
Flags: review?(mh+mozilla)
Reporter | ||
Comment 2•12 years ago
|
||
This measures time spent on enumeration. As far as I can tell .javaEnabled is the leading trigger of plugin enumeration. This should confirm it.
Attachment #542958 -
Flags: review?(joshmoz)
Comment 3•12 years ago
|
||
Comment on attachment 542953 [details] [diff] [review] raii helper Review of attachment 542953 [details] [diff] [review]: ----------------------------------------------------------------- ::: toolkit/components/telemetry/Telemetry.h @@ +75,5 @@ > + > +private: > + const ID id; > + const TimeStamp start; > +}; I think this would also work with something like: template <int id> class Timer { public: Timer(): start(TimeStamp::Now()) {} ~Timer() { Accumulate(ID(id), (TimeStamp::Now() - start).ToMilliseconds()); } private: const TimeStamp start; }; In practice, with compiler optimizations, I'm not sure it would make any difference, though. (except in debug builds where we build without optimization)
Attachment #542953 -
Flags: review?(mh+mozilla) → review+
Reporter | ||
Comment 4•12 years ago
|
||
Template suggestion makes using this brilliant. Thanks.
Attachment #542953 -
Attachment is obsolete: true
Attachment #543285 -
Flags: review+
Reporter | ||
Comment 5•12 years ago
|
||
Updated with template change
Attachment #542958 -
Attachment is obsolete: true
Attachment #543286 -
Flags: review?(joshmoz)
Attachment #542958 -
Flags: review?(joshmoz)
Reporter | ||
Comment 6•12 years ago
|
||
Josh, I would appreciate a quick review on this. Would be good to get some wider coverage on plugin overhead in released versions in firefox(since we are merging soon)
Comment 7•12 years ago
|
||
Comment on attachment 543286 [details] [diff] [review] telemetry for addon scanning This looks fine to me, although I'd prefer Telemetry::Timer were called AutoTimer to emphasize the fact that it's RAII.
Attachment #543286 -
Flags: review?(joshmoz) → review+
Reporter | ||
Comment 8•12 years ago
|
||
http://hg.mozilla.org/integration/mozilla-inbound/rev/3a5af9d36fb1 http://hg.mozilla.org/integration/mozilla-inbound/rev/4504b65f69db
Whiteboard: [inbound]
Would be nicer if this were AutoTimer to match our RAII naming conventions.
Reporter | ||
Comment 10•12 years ago
|
||
(In reply to comment #9) > Would be nicer if this were AutoTimer to match our RAII naming conventions. ok since there are two votes, I'll change it in a followup.
Reporter | ||
Comment 11•12 years ago
|
||
(In reply to comment #9) > Would be nicer if this were AutoTimer to match our RAII naming conventions. http://hg.mozilla.org/integration/mozilla-inbound/rev/0d425ab8eb13
Comment 12•12 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/4504b65f69db http://hg.mozilla.org/mozilla-central/rev/3a5af9d36fb1 http://hg.mozilla.org/mozilla-central/rev/0d425ab8eb13
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla7
Updated•1 year ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•