From: Martin Ward <martin@gkc.org.uk>
To: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org
Subject: Re: Serious performance issues with 1.9.0
Date: Thu, 16 Jul 2009 11:16:21 +0100 [thread overview]
Message-ID: <200907161116.21975.martin@gkc.org.uk> (raw)
In-Reply-To: <87bpnlawi9.fsf@arudy.ossau.uklinux.net>
On Thursday 16 Jul 2009 08:59, Neil Jerram wrote:
> Martin Ward <martin@gkc.org.uk> writes:
> > Running a test program on Guile 1.8.7 takes 100 seconds CPU time.
> > On Guile 1.9.0 (beta) the same program takes 237 seconds CPU time!
>
> I wonder if that's because the code is being auto-compiled? Do you
> get a better result if you set environment variable GUILE_AUTO_COMPILE
> to 0 ?
This is with Guile 1.9.1, running on a slightly different program:
GUILE_AUTO_COMPILE 1 takes 204 seconds
GUILE_AUTO_COMPILE 0 takes 213 seconds
The only file in ~/.cache is guile-1.9.1/test-suite/lib.scm.go
Guile 1.8.7 takes 81 seconds on this example.
SCM 5e5 takes 18 seconds.
Hobbit-compiled code: less than 1 second.
> > For comparison:
> >
> > Gambit v4.4.4 takes 60 seconds.
> > SCM version 5e5 takes 20.7 seconds.
>
> We're working on it!
>
> > Hobbit compiled code running under SCM takes 1.1 seconds!
> >
> > There was some talk a few years ago about integrating the Hobbit
> > compiler with Guile: but nothing seems to have come of it.
>
> No, that line of work fizzled out. It may come back again in the more
> general compilation and language transformation framework that we now
> have.
If guile is intended to be a "proper" language: suitable for production use
and not just for playing with toy programs, then a decent compiler
is essential.
I had to hack hobbit just to get separate compilation to work!
--
Martin
martin@gkc.org.uk http://www.cse.dmu.ac.uk/~mward/ Erdos number: 4
G.K.Chesterton web site: http://www.cse.dmu.ac.uk/~mward/gkc/
next prev parent reply other threads:[~2009-07-16 10:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 10:07 Serious performance issues with 1.9.0 Martin Ward
2009-07-16 7:59 ` Neil Jerram
2009-07-16 8:44 ` Neil Jerram
2009-07-16 10:16 ` Martin Ward [this message]
2009-07-17 15:16 ` Ludovic Courtès
2009-07-17 17:27 ` Martin Ward
2009-07-17 18:10 ` Ludovic Courtès
2009-07-19 13:56 ` Martin Ward
2009-07-19 22:03 ` Andy Wingo
2009-07-20 12:48 ` Martin Ward
2009-07-24 10:23 ` Andy Wingo
2009-07-20 22:00 ` Ludovic Courtès
2009-07-26 12:01 ` Andy Wingo
2009-08-11 22:31 ` 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=200907161116.21975.martin@gkc.org.uk \
--to=martin@gkc.org.uk \
--cc=bug-guile@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).