[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: indirect threading for bytecode interpreter
From: |
Stefan Monnier |
Subject: |
Re: indirect threading for bytecode interpreter |
Date: |
Mon, 21 Sep 2009 10:46:09 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) |
>>> I've profiled (using oprofile) Emacs running this a few times;
>>> typical results show mark_object at 10-12% of runtime. It is
>>> probably pretty easy to reproduce this with a variety of elisp
>>> programs.
>> So no matter how hard we try, we won't gain more than about 10%
>> speed-up trying to optimize the GC. Doesn't sound like a great
>> motivator.
> The 10% occur in bursts of unresponsiveness. If such a burst is halved
> in size, the total runtime improvement will not be impressive, but the
> responsiveness gets quite better.
That is true. To help solve this, we should aim to move towards
a concurrent GC (i.e. a GC that's actually likely to be slower, but
won't cause unresponsiveness).
Stefan
- Re: indirect threading for bytecode interpreter, (continued)
Re: indirect threading for bytecode interpreter, Dan Nicolaescu, 2009/09/18
- Re: indirect threading for bytecode interpreter, Tom Tromey, 2009/09/18
- Re: indirect threading for bytecode interpreter, Dan Nicolaescu, 2009/09/20
- Re: indirect threading for bytecode interpreter, Tom Tromey, 2009/09/20
- Re: indirect threading for bytecode interpreter, Stefan Monnier, 2009/09/21
- Re: indirect threading for bytecode interpreter, David Kastrup, 2009/09/21
- Re: indirect threading for bytecode interpreter, joakim, 2009/09/21
- Re: indirect threading for bytecode interpreter,
Stefan Monnier <=
- Re: indirect threading for bytecode interpreter, Tom Tromey, 2009/09/21