Closed Bug 706847 Opened 9 years ago Closed 5 years ago
Add profiling to peptest
Peptest currently tells us how much unresponsiveness there is, but not where it comes from. The work done by Dietrich (https://etherpad.mozilla.org/responsiveness-profiling) can potentially be leveraged.
Benoit Girard is working on a built in profiler that looks like should be fairly simple to integrate: http://benoitgirard.wordpress.com/2011/11/08/firefox-built-in-profiler/
Benoit, Dietrich, can we decide on which profiler we want to move forward with here and integrate it into peptest and/or m-c? Peptest is almost through the releng deployment steps, so we are very close to having this be something we can run 24/7 in the buildbot automation.
Is there more documentation on this profiler? As far as SPS goes the initial release is not really aimed to be used for automated testing. It's meant to be used for developers. I'd be curious to hear more about Dietrich's profiler.
Summary: Determine what is causing unresponsiveness → Add profiling to peptest
(In reply to Benoit Girard (:BenWa) from comment #3) > As far as SPS goes the initial release is not really aimed to be used for > automated testing. It's meant to be used for developers. The use case we are looking at is more for devs to figure out how to fix a test that regressed in responsiveness. Profiling might even be disabled when tests are run by buildbot. So I think SPS may still be suitable.
I'm not working on a profiler. I stopped after talking to Andrew about the work he was doing. What I was doing was for correlating hangs/pauses with JS stack, and is detailed here: https://etherpad.mozilla.org/responsiveness-profiling
(In reply to Benoit Girard (:BenWa) from comment #3) Just to revise my previous comment the profiler has made significant improvements and I'm looking into integrating it into more automated test run. Feel free to discuss this with me when you have time to look at this.
I understand peptests have been turned off for some time, is this still a useful bug?
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.