From: Andy Wingo <INVALID.NOREPLY@gnu.org>
To: Andy Wingo <wingo@pobox.com>,
Stefan Israelsson Tampe <stefan.itampe@gmail.com>,
bug-guile@gnu.org
Subject: [bug #30901] High runtime variance
Date: Fri, 17 Jun 2011 18:07:38 +0000 [thread overview]
Message-ID: <20110617-180738.sv20118.80577@savannah.gnu.org> (raw)
In-Reply-To: <20110609-160055.sv78157.36159@savannah.gnu.org>
Update of bug #30901 (project guile):
Status: None => Works For Me
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #2:
I too no longer see the high runtime variance, but that is with a different
machine, os, and newer guile. Pleasantly the same test runs in 1.25 seconds
here :)
Anyway, your suggestion sounds good Stefan. I will close as works-for-me.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30901>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
prev parent reply other threads:[~2011-06-17 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 19:49 [bug #30901] High runtime variance Andy Wingo
2011-06-09 16:00 ` Stefan Israelsson Tampe
2011-06-17 18:07 ` Andy Wingo [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=20110617-180738.sv20118.80577@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=stefan.itampe@gmail.com \
--cc=wingo@pobox.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 read-only IMAP folder(s) and NNTP newsgroup(s).