Re: Erratic timings

2016-01-04 Thread Parrot Raiser
> Could the jumps to >1 seconds be explained by automatic pre-compilation > taking place after > you re-compiled rakudo ? Why would that happen occasionally, after a number of executions of the same code? (If it was consistently the first run that was the long one, I'd be looking at that, but

Re: Erratic timings

2016-01-04 Thread Tobias Leich
Would be nice if someone could reproduce also. Am 04.01.2016 um 14:38 schrieb Parrot Raiser: Could the jumps to >1 seconds be explained by automatic pre-compilation taking place after you re-compiled rakudo ? Why would that happen occasionally, after a number of executions of the same code?

Re: Erratic timings

2016-01-04 Thread Parrot Raiser
The increase in "real" time was accompanied by changes in the other numbers. IIRC, I was offline at the time, so there shouldn't have been much else going on. Sorry to be so vague about the circumstances, but when you are surprised by what may or may not be a problem, securing the crime scene can

Re: Erratic timings

2016-01-04 Thread Tom Browder
On Mon, Jan 4, 2016 at 7:38 AM, Parrot Raiser <1parr...@gmail.com> wrote: >> Could the jumps to >1 seconds be explained by automatic pre-compilation >> taking place after >> you re-compiled rakudo ? > > Why would that happen occasionally, after a number of executions of > the same code? (If it

Re: Erratic timings

2016-01-04 Thread Parrot Raiser
On 1/4/16, Elizabeth Mattijsen wrote: > > FWIW, I have seen values that are off, but have always been able to trace it > back to my computer (stealthily or not) doing other things. > Thanks. Based on that, I'll assume it's not important unless it starts to happen regularly, in