From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34809@debbugs.gnu.org
Subject: bug#34809: 27.0.50; Too small number of samples in (benchmark-run-compiled …)
Date: Mon, 11 Mar 2019 21:40:58 +0300 [thread overview]
Message-ID: <1552329658.3183.0@yandex.ru> (raw)
In-Reply-To: <83r2bd46j2.fsf@gnu.org>
Thanks for testing! The bug can be closed since, as I mentioned in
prev. mail, updating to kernel 5.0 fixes it.
В Пн, мар 11, 2019 at 9:20 ПП (PM), Eli Zaretskii
<eliz@gnu.org> написал:
>> From: Konstantin Kharlamov <hi-angel@yandex.ru>
>> Date: Mon, 11 Mar 2019 00:19:45 +0300
>>
>> Result of (benchmark-run-compiled …) has suspiciously unevenly
>> distributed numbers. E.g. it might give all 100% to garbage
>> collector,
>> as if no other code was ran. This was found as part of thread about
>> slow
>> lexical-binding, and I was asked to report it.¹
>>
>> 1:
>> http://lists.gnu.org/archive/html/help-gnu-emacs/2019-03/msg00056.html
>>
>> # Steps to reproduce (in terms of terminal commands):
>> 1. wget
>>
>> https://gitlab.freedesktop.org/libinput/libinput/raw/9a2d6f55b1276da11dd9b2c4c8e22a405576dfea/src/libinput.h
>> 2. emacs -Q --eval "(progn (find-file \"./libinput.h\")
>> (profiler-start 'cpu) (benchmark-run-compiled 10
>> (c-font-lock-fontify-region 0 (point-max))) (profiler-report))"
>>
>> ## Expected:
>> Some of percentages should be inside cc-mode code.
>>
>> ## Actual:
>> - ... 1 100%
>> Automatic GC 1 100%
>
> Not reproducible on my system (I get a reasonable profile, with over
> 100 lines, which points to font-lock-fontify-keywords-region and
> c-find-decl-spots as two likely bottlenecks).
>
> So I think Glenn is right, and this has something to do with your
> kernel.
prev parent reply other threads:[~2019-03-11 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 21:19 bug#34809: 27.0.50; Too small number of samples in (benchmark-run-compiled …) Konstantin Kharlamov
2019-03-10 23:24 ` Glenn Morris
2019-03-11 17:01 ` Konstantin Kharlamov
2019-03-11 18:20 ` Eli Zaretskii
2019-03-11 18:40 ` Konstantin Kharlamov [this message]
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=1552329658.3183.0@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=34809@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).