From: Andrea Corallo <akrl@sdf.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 41194@debbugs.gnu.org
Subject: bug#41194: 28.0.50; [feature/native-comp] fibn benchmark exhausts memory
Date: Sun, 14 Jun 2020 16:19:06 +0000 [thread overview]
Message-ID: <xjfh7vdvcw5.fsf@sdf.org> (raw)
In-Reply-To: <877dw9k73y.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Sun, 14 Jun 2020 17:19:29 +0200")
Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
> Andrea Corallo <akrl@sdf.org> writes:
>
>> 5a55a845a7 * Implement 'maybe_gc_or_quit' to allow correct GC in compiled Lisp
>> 34ed9d2498 * Introduce latches
>>
>> are fixing here this issue, now running fibn at speed 2 the memory
>> consuptions stays constant.
>
> Alright, feedback time!
>
> Commits:
> - master: 82a632edc8b80bf16d9b9f205474bf9724b084c0
> - feature/native-comp: 5a55a845a7c426e82e8a6a6d02bc4a39992871e3
>
>
> The Good News
> =============
>
> - I can compile the branch without adding files to the default
> blacklist,
>
> - compilation (-j1) now only takes less than 6 hours instead of 3 days
> (compared with 1.5 hour on master),
>
> - at no point during compilation did the system swap; in fact, I could
> probably have risked a -j2 build,
>
> - elisp-benchmarks doesn't show any obvious performance regression
> (… though see Bad News).
>
> For details on memory usage during compilation, see attached memory
> profile (to compare with bug#41077#28).
Hi Kévin,
this is very good new thanks! If I read correctly we are always under
about 600MB as memory consumption is this correct?
>
> Few files take more than 3 minutes to compile now:
>
> ELC+ELN emacs-lisp/comp.el 0:09:49
> ELC+ELN org/org.el 0:03:39
> ELC+ELN ../lisp/window.el 0:03:16
> ELC+ELN emacs-lisp/bytecomp.el 0:03:16
>
> For details on performance, see attached tables for master and
> feature/native-comp, respectively (to compare with bug#41077#40).
>
>
>
>
> The Bad News
> ============
>
> - fibn still exhausts memory,
> - now pidigits does too.
>
>
>
>
> I've only tried the default comp-speed (2) so far. I've attached the
> results of M-x disassemble on the functions in fibn.el and pidigits.el.
I suspect we are still looking at a speed 3 run. How comp-speed was set
for the test?
I ask that because for now speed 3 is written into the stone within
elisp-benchmarks.el, yeah... :/ and so has to be manually changed there.
Thanks!
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2020-06-14 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 20:47 bug#41194: 28.0.50; [feature/native-comp] fibn benchmark exhausts memory Kévin Le Gouguec
2020-06-09 22:24 ` Andrea Corallo
2020-06-10 7:55 ` Kévin Le Gouguec
2020-06-13 15:00 ` Andrea Corallo
2020-06-13 18:17 ` Kévin Le Gouguec
2020-06-14 15:19 ` Kévin Le Gouguec
2020-06-14 16:19 ` Andrea Corallo [this message]
2020-06-14 20:47 ` Kévin Le Gouguec
2020-06-14 21:45 ` Andrea Corallo
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=xjfh7vdvcw5.fsf@sdf.org \
--to=akrl@sdf.org \
--cc=41194@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
/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).