From: Arturo Borquez <aborquez@altavista.com>
To: caml-list@inria.fr
Subject: [Caml-list] partial function application perfomance
Date: 2 Dec 2001 16:11:03 -0800 [thread overview]
Message-ID: <20011203001103.15717.cpmta@c016.snv.cp.net> (raw)
Hi all camlers,
I've being doing some benchmarks, and one of my tests
measures partial function application perfomance. I was
surprised by results: 20+ times slower than a full
function application. I expected a greater time but 20
times is a lot more ... I've checked my program and
seems ok, indeed the results were correct. Is this
overhead normal to partial function applications?
Best regards.
Arturo
Find the best deals on the web at AltaVista Shopping!
http://www.shopping.altavista.com
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next reply other threads:[~2001-12-03 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 0:11 Arturo Borquez [this message]
2001-12-03 1:11 ` Jacques Garrigue
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=20011203001103.15717.cpmta@c016.snv.cp.net \
--to=aborquez@altavista.com \
--cc=caml-list@inria.fr \
/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;
as well as URLs for NNTP newsgroup(s).