unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de>
Cc: guile-devel@gnu.org
Subject: Re: status: separation of expansion/optimization/memoization/execution
Date: Sun, 4 Aug 2002 03:51:01 +0200 (CEST)	[thread overview]
Message-ID: <Pine.GSO.4.05.10208040340400.7239-100000@sallust.ida.ing.tu-bs.de> (raw)
In-Reply-To: <15691.51367.455100.152498@blauw.xs4all.nl>

On Sat, 3 Aug 2002, Han-Wen wrote:

> dirk@sallust.ida.ing.tu-bs.de writes:
> > The effect so far is, that booting guile takes noticably longer (at least
> > 15%), but for example executing the test-suite is almost as fast as before
> 
> How do you measure that effectively? I now installed my new-gc guile,
> and starting it up takes as long as it used to (the speed up seems to
> have been disappeared.) Isn't the benchmark suite a much better test?

I measured it using "time guile < /dev/null" and repeated it several
times.  Each time the execution time varies, thus I tried to make out a
general tendency.  And, sure, the benchmark suite would be a better test,
if it contained some relevant benchmarks.  This is, up to now, not the
case.

However, didn't you say that you had some nice benchmark application
called lilypond ;-)  If there was a significant change due to your gc
changes, I believe you would notice it, right?  However, performance
improvements are not the major objective of your current patches, at least
that's what I understand:  IMO the code cleanup is the important point
here.

Best regards,
Dirk


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-08-04  1:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02 22:42 status: separation of expansion/optimization/memoization/execution Dirk Herrmann
2002-08-02 23:15 ` Rob Browning
2002-08-02 23:47   ` Han-Wen
2002-08-02 23:20 ` Dale P. Smith
2002-08-03 12:12 ` Han-Wen
2002-08-04  1:51   ` Dirk Herrmann [this message]
2002-08-04  2:03     ` Han-Wen
2002-08-04  2:05     ` Tom Lord
2002-08-04  2:11       ` Tom Lord
2002-08-04  2:20       ` for example Tom Lord
2002-08-04  2:27       ` i know -- let's play bridge! Tom Lord
2002-08-04  2:46         ` Tom Lord
2002-08-04  2:50           ` Thomas Bushnell, BSG
2002-08-04  2:57             ` Tom Lord
2002-08-04  3:04               ` Thomas Bushnell, BSG
2002-08-04  3:43                 ` Tom Lord
2002-08-04  3:53                   ` Thomas Bushnell, BSG
2002-08-04  4:03                     ` Tom Lord
2002-08-04  4:10                     ` Tom Lord
2002-08-04  3:50                 ` Tom Lord
2002-08-04  3:55                 ` Tom Lord
2002-08-04  3:58                   ` Tom Lord
2002-08-05 18:15   ` status: separation of expansion/optimization/memoization/execution Marius Vollmer
2002-08-05 18:11 ` Marius Vollmer
2002-08-07 20:51   ` Dirk Herrmann
2002-08-10 13:01     ` Marius Vollmer
2002-08-14 19:30       ` Dirk Herrmann
2002-08-26 22:11         ` Marius Vollmer
2002-08-05 18:36 ` Neil Jerram
2002-08-07 20:55   ` Dirk Herrmann

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=Pine.GSO.4.05.10208040340400.7239-100000@sallust.ida.ing.tu-bs.de \
    --to=dirk@sallust.ida.ing.tu-bs.de \
    --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).