On Mon, Mar 14, 2005 at 01:48:23AM +, Mark Stosberg wrote:
> On 2005-03-14, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> > On Mon, Mar 14, 2005 at 01:25:16AM +, Mark Stosberg wrote:
> >> I'm sorry-- I could have made this more productive by posting my own
> >> Benchmark
> >> code in the
On 2005-03-14, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 14, 2005 at 01:25:16AM +, Mark Stosberg wrote:
>> I'm sorry-- I could have made this more productive by posting my own
>> Benchmark
>> code in the first place. Look what happens when cmpthese is used. The
>> results look
On Mon, Mar 14, 2005 at 01:25:16AM +, Mark Stosberg wrote:
> I'm sorry-- I could have made this more productive by posting my own Benchmark
> code in the first place. Look what happens when cmpthese is used. The
> results look nonsensical to me:
Hmm. I guess the comparison isn't taking into a
On 2005-03-13, Michael G Schwern <[EMAIL PROTECTED]> wrote:
>
> We can just check.
>
> $ perl -MBenchmark -wle 'timethis(10, sub { `perl -wle "rand for 1..100"`
> })'
> timethis 10: 11 wallclock secs ( 0.01 usr 0.00 sys + 8.64 cusr 0.14 csys =
> 8.79 CPU) @ 1000.00/s (n=10)
>
> So the tim
On Sun, Mar 13, 2005 at 09:04:03PM +0100, Francisco Olarte Sanz wrote:
> I've checked the Benchmark module docs, and it's not too clear ( for me
> ),
> but I think they measure user/system time of your proccess. If you are
> executing external code via system/backticks etc.. this is normal
On Sunday 13 March 2005 00:43, Mark Stosberg wrote:
> > There is also a benchmarking module cunningly named "Benchmark" which you
> > should have a look at.
> Now now, I mentioned in the message I looked at 'Benchmark' first and it
> didn't work. I got the sense it might have only been timing the
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Sunday 13 March 2005 00:43, Mark Stosberg wrote:
> On Sat, Mar 12, 2005 at 03:29:32PM -0800, Michael G Schwern wrote:
> > Well, if you're just going to look at the wall clock, why use the
> > shell?
>
> Err...because I forgot about the simple 'time' com
On Sat, Mar 12, 2005 at 03:29:32PM -0800, Michael G Schwern wrote:
>
> Well, if you're just going to look at the wall clock, why use the shell?
Err...because I forgot about the simple 'time' command?
> my $start_time = time;
> `$bin diff 1/1 2>&1`;
> my $end_time = time;
>
On Sat, Mar 12, 2005 at 11:02:45PM +, Mark Stosberg wrote:
> My solution?
>
> my $out = `time $bin diff 1/1 2>&1`;
>
># XXX Parsing of time output may be fragile
>$out =~ m/\s*([\d\.]*\s+real.*)/;
>
> Ouch.
>
> Perhaps my whole approach is wrong. Am I overlooking a good open sou
darcs [1] is slow in a few places, and I'm working on benchmarking tool
in Perl to help monitor the performance. I'm got some questions about
the best way to proceed.
1. http://www.darcs.net/
So far: I've divided the task into a couple specific problems:
A. What repos to use for testing?
B. A
10 matches
Mail list logo
