From: skaller <skaller@users.sourceforge.net>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Memory allocation nano-benchmark.
Date: 12 Feb 2005 11:44:52 +1100 [thread overview]
Message-ID: <1108169091.3474.16.camel@pelican.wigram> (raw)
In-Reply-To: <20050211210729.GA466@first.in-berlin.de>
On Sat, 2005-02-12 at 08:07, Oliver Bandel wrote:
> > [skaller@pelican] ~>time ./zmem 250
> >
> > real 0m3.110s
> > user 0m2.820s
> > sys 0m0.240s
> >
> > [skaller@pelican] ~>time ./zmem 250
> >
> > real 0m27.732s
> > user 0m2.750s
> > sys 0m0.340s
>
>
> Two runs, no difference?
> Are you sure zmem and zmem are the same?
Yes, its the same binary.
>
> IMHO
>
> > real 0m3.110s
> > user 0m2.820s
> > sys 0m0.240s
>
> and
>
> > real 0m27.732s
> > user 0m2.750s
> > sys 0m0.340s
>
> differ...
Not significantly in user time. Remember this
is not a serious measurement.
> > table.(i).(j).(k) <- (i+1)*(j+1)*(k+1)
> >
> > Using bigarray (c_layout):
> >
> > real 0m27.948s
> > user 0m0.770s
> > sys 0m0.500s
> >
> > .. 4 times faster.
>
> ?
>
> What is faster than what?!
The code using ordinary arrays runs in 2.8 seconds,
using bigarray 0.7 seconds. 4 x 0.7 = 2.8.
bigarray is 4 times faster to write than three level
ordinary array.
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
next prev parent reply other threads:[~2005-02-12 0:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 15:15 Christian Szegedy
2005-02-10 14:47 ` [Caml-list] " Frédéric Gava
2005-02-10 15:19 ` skaller
2005-02-10 16:36 ` Frédéric Gava
2005-02-10 17:56 ` Frédéric Gava
2005-02-10 19:56 ` Christian Szegedy
2005-02-10 23:58 ` Frédéric Gava
2005-02-11 9:22 ` Frédéric Gava
2005-02-11 13:04 ` skaller
2005-02-11 13:33 ` skaller
2005-02-11 21:07 ` Oliver Bandel
2005-02-12 0:44 ` skaller [this message]
2005-02-15 14:17 ` Frédéric Gava
2005-02-15 19:19 ` Christian Szegedy
2005-02-15 20:51 ` Jon Harrop
2005-02-16 8:19 ` Ville-Pertti Keinonen
2005-02-16 9:54 ` Jon Harrop
2005-02-16 10:56 ` Ville-Pertti Keinonen
2005-02-11 0:55 ` skaller
2005-02-10 14:56 ` Jon Harrop
2005-02-10 15:32 ` Ville-Pertti Keinonen
2005-02-10 14:59 ` John Prevost
2005-02-10 16:50 ` Marwan Burelle
2005-02-10 19:20 ` Christian Szegedy
2005-02-10 19:40 ` Jon Harrop
2005-02-11 11:26 ` Oliver Bandel
2005-02-12 13:42 ` Christian Szegedy
2005-02-11 1:04 ` skaller
2005-02-11 11:28 ` Oliver Bandel
2005-02-12 0:01 ` Guillaume
2005-02-12 0:36 ` skaller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1108169091.3474.16.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@yquem.inria.fr \
--cc=oliver@first.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox