Re: Elisp native profiler

[Paul Eggert]

On 10/01/2012 07:48 AM, Eli Zaretskii wrote:
> Here's one data point: on a Windows XP system based on Core i7 CPU at
> 3.4GHz, running the profiler in an optimized build makes one of the 8
> cores fully (90%) busy.

That doesn't sound good.  Is this the main thread, the one that
runs the Emacs interpreter?  Then presumably it's running at roughly
10% of effectiveness.  And if it's *not* the main thread, there
are some race condition gotchas; the profiler signal handler
should not run in parallel with the garbage collector.

It's quite worrisome that a simple counting operation, done every 15 ms,
should nearly peg a core.  Something seems amiss.