Closed
Bug 491353
Opened 15 years ago
Closed 12 years ago
Modify sampling profiler to weight samples by affect on responsiveness
Categories
(Developer Infrastructure :: Source Code Analysis, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cjones, Unassigned)
References
Details
When starting to process an event from the main loop, Firefox will grab the current time (|start|). Each time the profiler takes a sample, it also reads the current time (|curr|), and adjusts the weight of the sample by
f(curr-start)
Likely we will want f to be discontinuous. Up to a tolerated latency (100 ms?), it should return a weight of 1. After that, the samples should probably be weighted by a function that grows exponentially to match the user's frustration.
Reporter | ||
Comment 1•15 years ago
|
||
(In reply to comment #0)
> Likely we will want f to be discontinuous.
s/discontinuous/non-differentiable/. Been a while since high school calculus.
Reporter | ||
Comment 2•12 years ago
|
||
Cleopatra UI does this, in effect.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Core → Firefox Build System
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•