From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: ‘read-line’ benchmark
Date: Wed, 26 Jan 2011 23:09:16 +0100 [thread overview]
Message-ID: <87hbcve2r7.fsf@gnu.org> (raw)
Hello!
I pushed a micro-benchmark, which I used to compare the new
implementation of ‘read-line’ (commit
e578faea202a4e6eeb32e81e489b59119a2e02a0) to the previous one (before
a2c36371ce3de246bdb892afd50915ecf450df47):
* before:
("ports.bm: rdelim: read-line" 1000 user 5.2)
* after:
("ports.bm: rdelim: read-line" 1000 user 3.72)
A 30% improvement, yay! (Indeed, we had reports of unexpected web
server speedups on IRC today. ;-))
Thanks,
Ludo’.
reply other threads:[~2011-01-26 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87hbcve2r7.fsf@gnu.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).