[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: scratch/accurate-warning-pos: Solid progress: the branch now bootstr

From: Paul Eggert
Subject: Re: scratch/accurate-warning-pos: Solid progress: the branch now bootstraps.
Date: Mon, 26 Nov 2018 18:48:49 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.3.1

On 11/26/18 10:43 AM, Alan Mackenzie wrote:
read the thread "Thoughts on getting correct line
numbers in the byte compiler's warning messages", which began here on

I read that thread, but to be honest my eyes began glazing over. I'm sure I missed some points.

The slowdown seems to be chrystallising out at 20 - 25% while byte
compiling, and 5 - 20% otherwise.

This may be significant, but is it really important?  Most of the time,
Emacs is waiting for the next key depression anyway.

And most of the time, my office at work is empty. That doesn't mean I don't care how well my office performs when a half-dozen people squeeze into it and try to get work done (which happened multiple times today...). Emacs regularly reacts too slowly for me when I use it in ordinary interaction, and I'd rather not see it get significantly slower.

As a data point, my 1.5 year old machine is about 150% faster (per core)
than its predecessor.
My desktop uses a circa 2010 design and is no doubt significantly slower than your machine. No doubt that partly explains why I'm more sensitive about performance issues.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]