348639 - Investigate why Tp2 numbers on argo spike every so often

Status: RESOLVED FIXED

(Webtools Graveyard :: Tinderbox, defect)

Description

[Adam Guthrie]

Every once in a while the Tp2 times on argo spike to around 2500 ms where on average they're usually around high 400s. This makes the graphs rather unreadable since the y-axis's range is so large.

rhelmer says he's working on this.

Comment 1

[Robert Helmer [:rhelmer]]

(In reply to comment #0)
> Every once in a while the Tp2 times on argo spike to around 2500 ms where on
> average they're usually around high 400s. This makes the graphs rather
> unreadable since the y-axis's range is so large.
> 
> rhelmer says he's working on this.

Just for clarification - the test machine is bl-bldlnx01, and is testing argo's binaries. Tp2 is the mozilla/tools/performance/pageload/ test running on a local Apache instance.

My guess is that this is something local to the test machine and not the binary.

Comment 2

[J. Paul Reed [:preed]]

Looks like this is fixed. I don't see spikes in the graph, and we turned a bunch of cronjobs off.