Closed
Bug 719968
Opened 13 years ago
Closed 9 years ago
Add hard faults to xperf talos output
Categories
(Testing :: Talos, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mak, Unassigned)
References
Details
Increase in hard faults may bring to lot of additional reads. So would be really interesting to measure it.
Comment 1•13 years ago
|
||
Currently we collect the HARD_FAULT provider:
http://hg.mozilla.org/build/talos/file/ca816866e975/talos/xperf.config#l106
I believe I need the stackwalk parameter "HardFault", as found here:
http://msdn.microsoft.com/en-us/library/windows/desktop/ff191012%28v=vs.85%29.aspx
Let me know if this looks right and I can get a recent .etl file and run some stuff by hand.
Comment 2•9 years ago
|
||
This bug has been around for almost 4 years, if we don't plan to work on it in the next couple of months, I would like to close it out. Please speak up if there are reasons to keep it open.
Flags: needinfo?(mak77)
Reporter | ||
Comment 3•9 years ago
|
||
As I said in bug 719965, it's up to the Perf team. I think the same considerations apply here.
Hard Faults is an interesting metric, since it tells we are not being efficient in memory usage and thus the system has to fallback to disk. Though, in this case I fear the measurement may end up being too noisy and dependent on the tinderbox memory status. Especially when using cloud boxes, it may not be very meaningful.
It would be fare more expensive than flushes to make this measurement reliable, so this is more likely a wontfix.
Flags: needinfo?(mak77) → needinfo?(vladan.bugzilla)
Comment 4•9 years ago
|
||
I'll let Aaron make the call here. This seems more difficult than bug 719965 and our focus is elsewhere for now, so I'm leaning toward closing it
Flags: needinfo?(vladan.bugzilla) → needinfo?(aklotz)
Comment 5•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(aklotz)
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•