From: Andy Wingo <wingo@pobox.com>
To: Luca Saiu <positron@gnu.org>
Cc: bug-guile@gnu.org
Subject: Re: High run time variance
Date: Wed, 04 Aug 2010 21:51:26 +0200 [thread overview]
Message-ID: <m3hbja2m2p.fsf@unquote.localdomain> (raw)
In-Reply-To: <4BB0D0A7.7080505@gnu.org> (Luca Saiu's message of "Mon, 29 Mar 2010 18:09:11 +0200")
On Mon 29 Mar 2010 18:09, Luca Saiu <positron@gnu.org> writes:
> To sum up, within each run the computation time of (fibo n) is the same,
> but the time varies widely from one run to another. This anomaly seems
> to have become much more accentuated in 1.9.
I suspect this is related to the GC issues brought up recently on
guile-user. Something is being misidentified as a Scheme object.
We'll poke this problem once we have a heap profiler.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-08-04 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 16:09 High run time variance Luca Saiu
2010-03-30 9:16 ` Ludovic Courtès
2010-03-30 12:35 ` Luca Saiu
2010-03-30 13:01 ` Ludovic Courtès
2010-03-30 15:05 ` Luca Saiu
2010-08-04 19:51 ` Andy Wingo [this message]
2010-08-05 13:42 ` Luca Saiu
2010-08-05 14:45 ` Andy Wingo
2010-08-05 16:21 ` Luca Saiu
2010-08-05 17:43 ` Andy Wingo
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=m3hbja2m2p.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=positron@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).