From: Andrea Corallo <acorallo@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: robertstephenboyer@gmail.com, Eli Zaretskii <eliz@gnu.org>,
69480@debbugs.gnu.org
Subject: bug#69480: Emacs Lisp needs, for its great 'native-compile', 'declare' and 'the' for fixnums and arrays.
Date: Fri, 01 Mar 2024 11:10:21 -0500 [thread overview]
Message-ID: <yp1le722as2.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87ttlqt3z6.fsf@gmx.net> (Stephen Berman's message of "Fri, 01 Mar 2024 15:35:09 +0100")
Stephen Berman <stephen.berman@gmx.net> writes:
> On Fri, 01 Mar 2024 09:07:54 -0500 Andrea Corallo <acorallo@gnu.org> wrote:
>
>> Stephen Berman <stephen.berman@gmx.net> writes:
>>
>>> On Fri, 01 Mar 2024 15:41:24 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>>>
> [...]
>>>> My suggestion was to compare profiles in the byte-compiled and
>>>> native-compiled cases.
>>>>
>>>> Btw, are you running both cases in the same session? If so, don't:
>>>> restart Emacs and run the other case instead.
>>>
>>> Ok, I've now done that. Here's the report for the run with native
>>> compilation:
>>>
>>> 12599 95% - command-execute
>>> 12487 95% - funcall-interactively
>>> 12486 95% - eval-expression
>>> 12485 95% - #<compiled -0x5db3e1955cb81d1>
>>> 12485 95% - #<compiled -0x8a5cf032951a0fe>
>>> 12480 95% - eval
>>> 12480 95% - progn
>>> 12367 94% - benchmark-call
>>> 12367 94% - #<lambda 0x8c97b8cb7bd82>
>>> 12367 94% build-sieve
>>> 113 0% - emacs-lisp-native-compile-and-load
>>> 113 0% - emacs-lisp-native-compile
>>> 113 0% - native-compile
>>
>> IIUC this is profiling the native compilation itself.
>>
>> BTW I'd suggest the profile is done with perf (and running batch).
>
> I don't have perf installed, but I build the kernel from source, so I
> guess I could build and install perf, but...
>
>> Given you see on your machine similar times for native and byte compiled
>> the expected outcome should be tha tthe time is spent in some C routine
>> of our core.
>
> If you consider ~12.7 (native-compiled) and ~9.6 (byte-compiled),
> similar for this benchmark, and since Eli said it's expected that
> native-compiled elisp can be slower than byte-compiled elisp for some
> programs, then I guess I can just accept that for this case, the
> difference between my timings is within a reasonable margin of error and
> not due to some problem with my libgccjit (which I also built and
> installed myself).
I doubt the correctness of your measure. Some points:
1- Your benchmark results shows you are measuring the compilation
process as well.
2- As Eli mentioned you should always start from on a freshly started
session (probably running batch).
3- You should also do several measures of the same test to estimate the
noise and, as consequence, the accuracy of your measure. The reason is
that there are many sources of noise on a running system (OS, paging,
CPU throttle due to thermal conditions etc...). These sources of noise
can have a big impact.
Measuring performance in reliable way is more tricky than what most
people think :)
Thanks
Andrea
next prev parent reply other threads:[~2024-03-01 16:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 19:40 bug#69480: Emacs Lisp needs, for its great 'native-compile', 'declare' and 'the' for fixnums and arrays Robert Boyer
2024-02-29 20:10 ` Eli Zaretskii
2024-02-29 20:54 ` Robert Boyer
2024-02-29 22:10 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 6:45 ` Eli Zaretskii
2024-02-29 21:04 ` Robert Boyer
2024-03-01 11:28 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 12:18 ` Andrea Corallo
2024-03-01 12:33 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 12:45 ` Eli Zaretskii
2024-03-01 13:07 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 13:41 ` Eli Zaretskii
2024-03-01 13:53 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 14:07 ` Andrea Corallo
2024-03-01 14:35 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 16:10 ` Andrea Corallo [this message]
2024-03-01 19:36 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 16:34 ` Eli Zaretskii
2024-03-01 19:36 ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-01 12:40 ` Eli Zaretskii
2024-03-01 12:34 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yp1le722as2.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=69480@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=robertstephenboyer@gmail.com \
--cc=stephen.berman@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).