This is the mail archive of the
guile@cygnus.com
mailing list for the Guile project.
Re: the viability of translators, and Guile itself
>>>>> "Mikael" == Mikael Djurfeldt <mdj@mdj-pc.nada.kth.se> writes:
Mikael> Guile's evaluator in itself is fast as lightning and only maybe 10-30%
Mikael> slower than current SCM, which is one sign that the implementation is
Mikael> good at least in some respects. (And since Guile's and SCM's
Mikael> evaluators are *very* similar, there are no limits in the architecture
Mikael> which prevents moving the ecache code over to Guile making it as fast
Mikael> as SCM.)
I believe that the guile *interpreter* compares well to other scheme
*interpreters* but does it hold when comparing interpreted guile to
compiled rscheme or bigloo or whatever?
Having a fast interpreter is good enough for many things and most
early project phases, but if one wants to write larger applications,
with demnands on performance, one will also need to care about the
maximum performance that can be achieved, following the traditional
wisdom of the develop-debug-profile-optimize cycle.
There is hope the hobbit compiler may be able to be good enough to
remedy the situation, but there is still quite some work to be done
here too.
I am trying to find time to do some benchmarking to study the effects
of compilation between different scheme implementations, but has so far
been unsuccesfull.
Another thing badly needed (along with better debugging support) is of
course profiling tools. I am working on this, but my initial
implementation has some problems that needs to be fixed.
---------------------------+--------------------------------------------------
Christian Lynbech | Telebit Communications A/S
Fax: +45 8628 8186 | Fabrikvej 11, DK-8260 Viby J
Phone: +45 8628 8177 + 28 | email: chl@tbit.dk --- URL: http://www.tbit.dk
---------------------------+--------------------------------------------------
Hit the philistines three times over the head with the Elisp reference manual.
- petonic@hal.com (Michael A. Petonic)