emacs-devel
[Top][All Lists]
Advanced

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

Re: Time to merge scratch/correct-warning-pos into master, perhaps?


From: Andrea Corallo
Subject: Re: Time to merge scratch/correct-warning-pos into master, perhaps?
Date: Mon, 07 Feb 2022 17:36:50 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Sun, 06 Feb 2022 20:40:41 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: larsi@gnus.org, mattiase@acm.org, gregory@heytings.org,
>>  monnier@iro.umontreal.ca, emacs-devel@gnu.org
>> 
>> Oh, one other thing: the Internet is full with very detailed tutorials
>> for how to use perf in different scenarios, so I suggest to look those
>> up if the tutorial that comes with the installation is not good
>> enough.
>
> Here's one I found useful at the time:
>
>    http://sandsoftwaresound.net/perf/perf-tutorial-hot-spots/
>
> It has a couple of examples that are relevant to what we want to do.

Hi all,

just to add: Alan if you are going to compare two builds with perf I'd
suggest to use two native compiled instances, with that using perf
you'll get information also on which specific Lisp function is taking
time.  I guess it might help the investigation.

Otherwise with bytecode for Lisp execution all time for perf is spent in
'exec_byte_code'.

Hope it helps.

Best Regards

  Andrea



reply via email to

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