all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: robertstephenboyer@gmail.com, 69480@debbugs.gnu.org, acorallo@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 15:41:24 +0200	[thread overview]
Message-ID: <86jzmmqdbv.fsf@gnu.org> (raw)
In-Reply-To: <8734tauml5.fsf@gmx.net> (message from Stephen Berman on Fri, 01 Mar 2024 14:07:50 +0100)

> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: acorallo@gnu.org,  bug-gnu-emacs@gnu.org,  robertstephenboyer@gmail.com,
>   69480@debbugs.gnu.org
> Date: Fri, 01 Mar 2024 14:07:50 +0100
> 
> On Fri, 01 Mar 2024 14:45:39 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
> 
> >> It's still slower with native compilation than with byte compilation on
> >> my machine, unlike on yours.  Do you have any idea why?
> >
> > Maybe your system takes time to allocate memory?  This program
> > allocates almost 850MB of memory on my system, so maybe yours starts
> > paging?
> 
> I see a similar allocation, but I have 16 GB of RAM (~12 of which were
> free when I ran the benchmark), so I think that shouldn't be an issue.
> 
> > Anyway, profiling could give some hints.
> 
> That says almost all memory and CPU are consumed by `build-sieve':

This is skewed, use cpu profiling instead of "memory" profiling.

> But I don't see how that bears on the difference between native and byte
> compilation in my timings versus yours and Andrea's.

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.





  reply	other threads:[~2024-03-01 13:41 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86jzmmqdbv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=69480@debbugs.gnu.org \
    --cc=acorallo@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.