Yeah, that can be seen in the fact that chaos's std dev for pypy-c is not as large as for pypy-c-jit, in fact it is perfectly normal.
Btw. for easily spotting big std dev values maybe they should be highlighted in red. What would a maximum reasonable value for std dev would be (compared to total time)? 2010/4/20 Maciej Fijalkowski <[email protected]> > Hi Carl, Hi Miquel. > > Cool job! > > On Tue, Apr 20, 2010 at 12:29 PM, Carl Friedrich Bolz <[email protected]> > wrote: > > Hi Miquel, > > > > On 04/20/2010 07:14 PM, Miquel Torres wrote: > >> Changes you may notice are geared towards easing the identification of > >> the cause of performance changes: > >> - Std deviation was added to the DB, overview table and timeline > >> tooltips. This way we can rule out fluctuations in the measuring as a > >> cause for a big change. It has to be pointed out though, that this is > >> only as useful as the way the std dev is being computed. (there you go, > >> Carl Friedrich ;-) > > > > Yay, that's incredibly cool! Let's hope that eventually the graph > > library supports errors too, so we can add them graphically. Anyway, I > > already found some fun things about the benchmarks, so thanks a lot! > > (e.g. the std dev of chaos is very large, which is not really a good > thing) > > Of course it's large, because as mentioned above the way we compute it > doesn't make sense. We have an average over consecutive runs which > include warmup (less and less so over the course). > > Cheers, > fijal > _______________________________________________ > [email protected] > http://codespeak.net/mailman/listinfo/pypy-dev >
_______________________________________________ [email protected] http://codespeak.net/mailman/listinfo/pypy-dev
