Here is a graph showing the problem: http://graphs.mozilla.org/graph.html#tests=[[275,132,37]]&sel=1400579353000,1400752153000 Here is a bit more about responsiveness: https://wiki.mozilla.org/Buildbot/Talos/Tests#Responsiveness I did some retriggers to help filter out any noise in the values: https://tbpl.mozilla.org/?tree=Fx-Team&fromchange=a3a74829a5cf&tochange=a6dcd4c2fb6b&jobname=Windows%20XP%2032-bit%20fx-team%20talos%20tp5o
oh, to be clear this is caused by: http://hg.mozilla.org/integration/fx-team/rev/c3b86a5d52b6
Summary: 6.37% tp5 responsiveness regression on winxp from bug 973535, on May 21 (fx32) → 6.37% tp5 responsiveness regression on winxp from bug 973532, on May 21 (fx32)
As with bug 1014789, I have no clue what's going on :/
Might be related to bug 881590?
this is a really old bug, but the regression is still valid: http://graphs.mozilla.org/graph.html#tests=%5B%5B275,53,37%5D%5D&sel=none&displayrange=365&datatype=running we have shipped with this, I am not sure if we should do anything else here. Tim, thoughts? shall we close this?
Sorry, I'm not sure I understand this graph. Is higher better here?
higher is worse, we want responsiveness to be low. This is quite an old issue by now.
ping - shall we close this as wontfix?
(In reply to Joel Maher (:jmaher) from comment #7) > ping - shall we close this as wontfix? Yeah, I'm not sure what to do about this now :/
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.