[pypy-dev] recent speed results

[Gasper Zejn]

I think moving to a non-VM is the only option. In a company where I used to 
work we had similar problems. All of the virtualization solutions' clocks just 
keep drifting back and forth and no useful performance data could be gathered 
unless the execution time was really long.

Kr,
Gašper

On Thursday 06 May 2010 14:08:51 Miquel Torres wrote:
> Yeah, I would tend to agree with Armin, it does seem to be the VM.
> Mmmh,  std dev does double compared to previous results, but it is still
> not that huge.
> 
> Moving to a non-VM machine would be a bit plus IMHO.
> 
> Cheers,
> Miquel
> 
> 
> 2010/5/6 Armin Rigo <arigo at tunes.org>
> 
> > Hi,
> > 
> > On Tue, May 04, 2010 at 07:59:17PM -0600, Maciej Fijalkowski wrote:
> > > Anyone has any clue where recent noise comes from? I could not
> > > pinpoint any single revision.
> > 
> > That really looks like some external factor, e.g. the machine is
> > overloaded.  Maybe we should move benchmarking to tannit.  It would mean
> > that the results cannot be followed across the move, but at least tannit
> > is a non-virtual machine on which we can ensure some consistent total
> > usage.
> > 
> > The drawback of picking tannit is that it's unclear what will occur to
> > it after the end of the current funding period.  Other choices have
> > other drawbacks -- e.g. wyvern is old (and not representative of today's
> > performance) and might die unexpectedly any year now.
> > 
> > 
> > A bientot,
> > 
> > Armin.
> > _______________________________________________
> > pypy-dev at codespeak.net
> > http://codespeak.net/mailman/listinfo/pypy-dev