From: Kenneth Knowles <kknowles@berkeley.edu>
To: "Vladimir N. Silyaev" <vsilyaev@mindspring.com>
Cc: caml-list@inria.fr
Subject: [Caml-list] Re: Lazy vs closure
Date: Wed, 19 May 2004 06:09:28 -0700 [thread overview]
Message-ID: <20040519130928.GA25420@tallman.kefka.frap.net> (raw)
In-Reply-To: <20040519062157.GA65076@server.vns.oc.ca.us>
Your test_lazy creates a new lazy value each time. The thing that might make
Lazy faster than closure (or rather, _should_ make it faster) is if you evaluate
the same value multiple times, because it is only computed once. The slowdown
compared to closures is probably the bookkeeping necessary for this memoizing.
Kenn
On Tue, May 18, 2004 at 11:21:57PM -0700, Vladimir N. Silyaev wrote:
> After reading list and seeing statement that lazy/Lazy.force is faster then
> closure/apply, I've decided to run microbenchmark with both.
> Results are rather confusing:
> Byte code - Lazy is three times slower than closure
> Native code (x86) - it's either coredumps or leaks memory
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2004-05-19 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 6:21 [Caml-list] " Vladimir N. Silyaev
2004-05-19 7:04 ` David Brown
2004-05-19 7:32 ` Vladimir N. Silyaev
2004-05-19 7:59 ` David Brown
2004-05-19 9:10 ` skaller
2004-05-19 13:11 ` Kenneth Knowles
2004-05-19 13:09 ` Kenneth Knowles [this message]
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=20040519130928.GA25420@tallman.kefka.frap.net \
--to=kknowles@berkeley.edu \
--cc=caml-list@inria.fr \
--cc=vsilyaev@mindspring.com \
/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).