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 which case I will tr
> On 04 Jan 2016, at 15:17, Parrot Raiser <1parr...@gmail.com> wrote:
>
> 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 y
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
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 was
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? (I
> 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 it'
> On 03 Jan 2016, at 21:52, Parrot Raiser <1parr...@gmail.com> wrote:
>
> While running simple tests with essentially empty Perl6 programs, I
> noticed some odd variations in run timing. Occasionally, when a test
> was repeated, it would take something like 3 times as long as the
> previous run.
While running simple tests with essentially empty Perl6 programs, I
noticed some odd variations in run timing. Occasionally, when a test
was repeated, it would take something like 3 times as long as the
previous run.
Using the "time" command confirmed the phenomenon, but showed no
patterns I could