From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Learning to write interpreted code
Date: Thu, 09 Aug 2007 17:07:35 +0200 [thread overview]
Message-ID: <87odhgoifc.fsf@chbouib.org> (raw)
In-Reply-To: 877io4pxt7.fsf@chbouib.org
ludo@gnu.org (Ludovic Courtès) writes:
> So I went ahead and removed the `not' within the loop, rewriting
> `(if (not c) a b)' to `(if c b a)', and voilà:
>
> % cumulative self
> time seconds seconds name
> 8.88 1.19 1.08 xdr-basic-type-size
> 5.14 0.74 0.62 xdr-basic-type-type-pred
> 4.21 0.68 0.51 xdr-basic-type-encoder
> 3.74 1.64 0.45 +
> 3.74 0.45 0.45 eq?
> [...]
> Total time: 12.11 seconds (167/100 seconds in GC)
>
> An order of magnitude faster!
Actually, `statprof' is magnifying the effect on total run time since I
can hardly notice a 10% difference when running the thing without
statprof...
Sorry for the noise.
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2007-08-09 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 14:49 Learning to write interpreted code Ludovic Courtès
2007-08-09 15:07 ` Ludovic Courtès [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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87odhgoifc.fsf@chbouib.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).