From: Tom Lord <lord@regexps.com>
Cc: hanwen@cs.uu.nl
Subject: Re: lazy sweeping.
Date: Sun, 28 Jul 2002 21:31:40 -0700 (PDT) [thread overview]
Message-ID: <200207290431.VAA08976@morrowfield.regexps.com> (raw)
In-Reply-To: <15684.32520.154258.348830@blauw.xs4all.nl> (message from Han-Wen on Mon, 29 Jul 2002 01:32:24 +0200)
Nothing spectacular. But now checkout ... the startup time!
(this is the time for starting guile, and then pressing ^D)
This is not a very good measure of effective start-up time in
SCM-based (incremental graph translation) Schemes. Odds are you have
a lot of untranslated code in that image, and when I add my
application code, you'll have even more untranslated code. Substitute
anything useful for that ^D, and the real costs will start to become
more apparent, especially if your application involves long-running
processes.
SCM performs pretty damn well if what you want is a fast
edit-rerun-debug cycle for CAE and symbolic math tasks, especially
with the special GC for environments. It's also great if you have an
`eval'-intensive application.
Unexec helps, though I've noted substantial qualitative differences
between unexec _before_ running through most execution paths
vs. _after_: incremental translation in action.
Heck, you want _really_ fast start up time? Read the first line of
input to Guile before doing _anything_ else, doing a short-circuit
exit if the first line is just EOF. That'll be really fast ;-)
-t
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-29 4:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 23:32 lazy sweeping Han-Wen
2002-07-29 0:07 ` Michael Livshin
2002-07-29 9:48 ` Han-Wen Nienhuys
2002-07-29 10:14 ` Michael Livshin
2002-07-29 12:40 ` Han-Wen Nienhuys
2002-07-29 13:00 ` Michael Livshin
2002-07-29 13:06 ` Han-Wen Nienhuys
2002-07-30 10:09 ` Han-Wen
2002-07-30 12:10 ` Michael Livshin
2002-07-29 4:31 ` Tom Lord [this message]
2002-07-29 15:17 ` Han-Wen Nienhuys
2002-07-29 13:16 ` Mikael Djurfeldt
2002-07-29 13:22 ` Han-Wen Nienhuys
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=200207290431.VAA08976@morrowfield.regexps.com \
--to=lord@regexps.com \
--cc=hanwen@cs.uu.nl \
/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).