[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: guile-vm 0.3
From: |
Keisuke Nishida |
Subject: |
Re: guile-vm 0.3 |
Date: |
Tue, 03 Apr 2001 17:08:01 -0400 |
User-agent: |
Wanderlust/2.4.0 (Rio) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) Emacs/21.0.99 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) |
At 03 Apr 2001 13:10:28 -0500,
Rob Browning wrote:
>
> And I think there's also the possibility that a hybrid, combining JIT
> and byte-code might be a really interesting approach. For some parts
> of your code, the memory compression of bytecoding might be a big win,
> and for the tightest inner loops, you might want Lightning.
That's interesting. Probably we can do it in the long run.
> I wonder if you could hook up the system with a profiler so that
> during development guile could identify the critical sections and try
> each approach, eventually choosing the one that's fastest. Then you
> might need a way to annotate your code so that when you load normally,
> guile will choose the right one by default.
>
> Another interesting possibility would be a run-time profiler that
> compiled a cached subset of the most frequently called functions --
> this might be good for a guile webserver or database that computed in
> "phases".
Possible, but I think we shouldn't think about this sort of
optimization right now.
Kei
- Re: guile-vm 0.3, (continued)
- Re: guile-vm 0.3, Marius Vollmer, 2001/04/12
- Re: guile-vm 0.3, Keisuke Nishida, 2001/04/12
- Re: guile-vm 0.3, Marius Vollmer, 2001/04/12
- Re: guile-vm 0.3, Rob Browning, 2001/04/12
- Re: guile-vm 0.3, Marius Vollmer, 2001/04/12
Re: guile-vm 0.3, Keisuke Nishida, 2001/04/01
Re: guile-vm 0.3, Evan Prodromou, 2001/04/03