Prev: (lack of) Helpfulness of Perl error messages.
Next: libwww-perl authorization problem
From: brian d foy on 19 Feb 2010 19:47
In article <j8OdnWeEAuNg9ODWnZ2dnUVZ8nhi4p2d(a)brightview.co.uk>, bugbear
<bugbear(a)trim_papermule.co.uk_trim> wrote:


> Is there a standard benchmark, used (perhaps)
> when people port Perl to different CPUs/OS/compilers?

Use perlbench. It's a bit underdocumented, but I show some examples
in Mastering Perl. :)
From: bugbear on 20 Feb 2010 03:40
brian d foy wrote:
> In article <j8OdnWeEAuNg9ODWnZ2dnUVZ8nhi4p2d(a)brightview.co.uk>, bugbear
> <bugbear(a)trim_papermule.co.uk_trim> wrote:
>
>
>> Is there a standard benchmark, used (perhaps)
>> when people port Perl to different CPUs/OS/compilers?
>
> Use perlbench. It's a bit underdocumented, but I show some examples
> in Mastering Perl. :)

I installed perlbench, but it seems to have
a frankly tiny test set (6 tests), as I posted
in this thread.

I'm looking for actual benchmarks, not a benchmark
"framework".

For the same reason the CPAN "Benchmark" is
not what I want.

BugBear
From: Ben Morrow on 20 Feb 2010 06:39

Quoth bugbear <bugbear(a)trim_papermule.co.uk_trim>:
> Ben Morrow wrote:
> >
> > There is perlbench on CPAN, but I believe it's not considered to be as
> > representative as it used to be.
>
> I downloaded this (shortly after my first post).
> I must be missing something - it only runs 8 tests, none
> of which look very "general";
> perl-5.10.0 (DEBUGGING)
> @bugbear-dell
> app/podhtml 674.190 ms �-11.429
> startup/noprog 2.484 ms �-2.098
> statement/func-call-empty-5arg 1.058 �s �-0.020
> statement/func-call-empty-2arg 670.138 ns �-20.012
> statement/func-call-empty-1arg 397.798 ns �-7.001
> statement/func-call-empty-0arg 215.374 ns �-2.893
> statement/assign-int 68.174 ns �-1.229
> statement/inc 46.290 ns �-1.217
>
> is there a separate Module of tests, with perlbench being
> just a harness?

You're running perlbench-runtests. Try perlbench-run instead, passing it
paths to several different perl binaries. Obviously this means you have
to have all the perls you want to compare on the same machine, so you
can't easily compare, say, perl-on-linux and perl-on-win32. It would be
very hard to get a meaningful comparison in that case anyway.

Ben

From: bugbear on 22 Feb 2010 05:40
Ben Morrow wrote:
> Quoth bugbear <bugbear(a)trim_papermule.co.uk_trim>:
>> Ben Morrow wrote:
>>> There is perlbench on CPAN, but I believe it's not considered to be as
>>> representative as it used to be.
>> I downloaded this (shortly after my first post).
>> I must be missing something - it only runs 8 tests, none
>> of which look very "general";
>> perl-5.10.0 (DEBUGGING)
>> @bugbear-dell
>> app/podhtml 674.190 ms �-11.429
>> startup/noprog 2.484 ms �-2.098
>> statement/func-call-empty-5arg 1.058 �s �-0.020
>> statement/func-call-empty-2arg 670.138 ns �-20.012
>> statement/func-call-empty-1arg 397.798 ns �-7.001
>> statement/func-call-empty-0arg 215.374 ns �-2.893
>> statement/assign-int 68.174 ns �-1.229
>> statement/inc 46.290 ns �-1.217
>>
>> is there a separate Module of tests, with perlbench being
>> just a harness?
>
> You're running perlbench-runtests. Try perlbench-run instead, passing it
> paths to several different perl binaries. Obviously this means you have
> to have all the perls you want to compare on the same machine, so you
> can't easily compare, say, perl-on-linux and perl-on-win32. It would be
> very hard to get a meaningful comparison in that case anyway.

That's exactly what I need to do - I need a measure of "perl power"
on various boxes.

You're quite right about perlbench-run - it does EXACTLY
what I want.

BugBear
From: brian d foy on 23 Feb 2010 14:52
In article <29udnbY9VdqPPeLWnZ2dnUVZ8h-dnZ2d(a)brightview.co.uk>, bugbear
<bugbear(a)trim_papermule.co.uk_trim> wrote:

> brian d foy wrote:
> > In article <j8OdnWeEAuNg9ODWnZ2dnUVZ8nhi4p2d(a)brightview.co.uk>, bugbear
> > <bugbear(a)trim_papermule.co.uk_trim> wrote:

> > Use perlbench. It's a bit underdocumented, but I show some examples
> > in Mastering Perl. :)

> I installed perlbench, but it seems to have
> a frankly tiny test set (6 tests), as I posted
> in this thread.

Well, the idea is to write tests that matter to you and run them
against the perls that you want to use. You see how perl performs
against that stuff you are actually going ot use with it.
First  |  Prev  | 
Pages: 1 2
Prev: (lack of) Helpfulness of Perl error messages.
Next: libwww-perl authorization problem