From: Eli Zaretskii <eliz@gnu.org>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
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 20:20:33 +0200 [thread overview]
Message-ID: <83r2bd46j2.fsf@gnu.org> (raw)
In-Reply-To: <f9af51ec-a43d-7053-52ff-8267aeaedc41@yandex.ru> (message from Konstantin Kharlamov on Mon, 11 Mar 2019 00:19:45 +0300)
> 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.
next prev parent reply other threads:[~2019-03-11 18:20 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 [this message]
2019-03-11 18:40 ` Konstantin Kharlamov
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=83r2bd46j2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34809@debbugs.gnu.org \
--cc=hi-angel@yandex.ru \
/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.