Hi all,
Thanks to those who filled out the doodle to indicate your availability for
the next Parrot Developer Summit. The slots with the fewest conflicts were at
the same time on different weeks. I've closed the doodle poll and marked
Saturday the 14th at 1PM UTC as the official date for the
For a week, kid51 and myself have been debugging the
tt1931-nci-parameters-deprecation branch. After having discovered and
fixed a number of issues, one problem remains. Some build stages and
tests (generally NQP or PCT programs), when run automatically under
make, consistently trigger an assertion
Hello.
On Wed, May 4, 2011 at 6:29 AM, Patrick R. Michaud wrote:
> Version T1 T2 T3 T4 Fastest vs 2011.01
> --
> bench-s1 -- core.pm:
> 2011.01/3.0 (ms2) 254 279 278 275
Howdy,
Thank you moritz++, this is very valuable data.
Is there any way you can generate similar data for small, specific subsets of
the spectests? Such as, subsets for OO, String, Float and Integer performance.
That way, we can pinpoint which subsystems are having performance regressions.
I wou
On 03/05/11 22:29, Patrick R. Michaud wrote:
Our current guess is that something happened between 3.0 and 3.1
to significantly slow down Parrot, and then the gms GC managed to
claw back much (but not all) of the gains for Rakudo spectests
and build time on my machine.
The slowdown in 3.1 is pro
On Tue, May 03, 2011 at 09:45:45PM +1000, Vasily Chekalkin wrote:
> And there is rakudo's build time excerts for "core.pm" test. All
> builds were configured with "--makefile-timing --gen-parrot".
On my system, core.pm consistently takes longer under Parrot 3.3 (gms)
than it does on Parrot 3.0 (ms
Hi all,
so, I've done some timings of rakudo compilation times.
A picture says more than 1000 words, so please take a look at the file
in the attachement. In case some stupid filter strips it out, you an
also find it here:
http://moritz.faui2k3.org/tmp/rakudo-perl-2011-05-03.png
The x axis needs
Hello.
So, there is results:
Rakudo 2011.01, roast 8447ca8:
Files=542, Tests=27340, 2338 wallclock secs ( 9.09 usr 1.63 sys +
2217.65 cusr 53.14 csys = 2281.51 CPU)
Rakudo 2011.04, roast 7309150:
Files=549, Tests=27695, 2097 wallclock secs ( 9.28 usr 1.72 sys +
1986.99 cusr 41.89 csys = 2039.8
On May 3, 2011, at 8:16 AM, Patrick R. Michaud wrote:
The size/content of the (bundled) spectests between 2011.01 and
2011.04 doesn't seem to have changed significantly.
Would it be possible to create a subset of the spectests that have
not changed over, say, the past 12 months and are c
Hello.
On Tue, May 3, 2011 at 10:16 PM, Patrick R. Michaud wrote:
> On Tue, May 03, 2011 at 09:45:45PM +1000, Vasily Chekalkin wrote:
>>
>> ("make spectest" will definetely be comparision of apples to oranges.
>> There are plenty of failures on 2011.01 atm)
>
> I'm using the spectest that was bun
On Tue, May 03, 2011 at 09:45:45PM +1000, Vasily Chekalkin wrote:
>
> ("make spectest" will definetely be comparision of apples to oranges.
> There are plenty of failures on 2011.01 atm)
I'm using the spectest that was bundled with the 2011.01 release.
There shouldn't be any failures there -- but
Hello.
And there is rakudo's build time excerts for "core.pm" test. All
builds were configured with "--makefile-timing --gen-parrot".
Rakudo 2011.01, Parrot 3.0 GC MS2:
time /home/bacek/src/rakudo-2011-01/parrot_install/bin/parrot
src/gen/perl6.pbc --target=pir --stagestats \
src/gen/
Hello.
It's quite comprehensive investigation. But I have few comments/notes.
1. MS2 was landed way before 3.0. I don't remember exact dates but it
doesn't really matter.
2. Yes, GMS consumes less memory than MS/MS2. Just because of nature of GenGC.
3. I'm still don't quite understand why Rakudo
13 matches
Mail list logo
