From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: Robert Pluim <rpluim@gmail.com>
Cc: 61490@debbugs.gnu.org
Subject: bug#61490: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768
Date: Thu, 16 Feb 2023 19:48:35 +0300 [thread overview]
Message-ID: <2bee6d8548acde05ef32f2c46119f16380e5b817.camel@yandex.ru> (raw)
In-Reply-To: <87pma9mxxe.fsf@gmail.com>
On Thu, 2023-02-16 at 16:29 +0100, Robert Pluim wrote:
> > > > > > On Thu, 16 Feb 2023 18:05:09 +0300, Konstantin Kharlamov
> > > > > > <Hi-Angel@yandex.ru> said:
>
> Konstantin> Originally discovered by Tyler Dodge in his article
> "Significant Garbage
> Konstantin> Collection Improvement For Emacs".
>
> Konstantin> While testing this change on Archlinux system with Intel i5-
> 7200U CPU,
> Konstantin> average time of garbage collection gets reduced by ≈25%. Other
> users
> Konstantin> report improvements up to 50%. While monitoring PSS of emacs
> with and
> Konstantin> without customizations loaded before and after the patch, no
> Konstantin> statistically significant differences were discovered. So
> overall, this
> Konstantin> change is a win.
>
> I havenʼt tested it yet, but it looks reasonable.
>
> Procedural nit: if you put the bug number in the commit message rather
> than the Subject, then 'git am' will strip the [PATCH v2] prefix for
> us.
I am not sure I understood. I did not put the bug number in the subject at all,
it is probably done by debbugs. E.g. if you look at this v2 patch in a browser
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61490#20 the "Subject" line
displayed there does not contain a bug number.
I can add a bug number to the body the next time, but I'm not sure it would make
debbugs stop adding the prefix.
next prev parent reply other threads:[~2023-02-16 16:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 20:00 bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Konstantin Kharlamov
2023-02-13 20:00 ` bug#61489: [PATCH 1/1] " Konstantin Kharlamov
[not found] ` <handler.61489.B.167631844622733.ack@debbugs.gnu.org>
2023-02-13 20:05 ` bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵) Konstantin Kharlamov
2023-02-14 3:29 ` Eli Zaretskii
2023-02-14 6:45 ` Konstantin Kharlamov
2023-02-14 6:56 ` Konstantin Kharlamov
2023-02-14 8:20 ` Robert Pluim
2023-02-14 8:22 ` Konstantin Kharlamov
2023-02-14 8:29 ` Konstantin Kharlamov
2023-02-14 13:26 ` Eli Zaretskii
2023-02-15 7:03 ` bug#61489: Open a bug report with git-send-email (was: bug#61489: Acknowledgement ([PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵)) Kévin Le Gouguec
2023-02-13 22:30 ` bug#61489: [PATCH 1/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵ Ihor Radchenko
2023-02-16 15:07 ` bug#61489: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768 Konstantin Kharlamov
2023-02-23 15:30 ` Konstantin Kharlamov
2023-02-23 15:49 ` Robert Pluim
2023-02-23 15:53 ` Konstantin Kharlamov
2023-02-23 15:57 ` bug#61490: " Robert Pluim
2023-02-23 16:05 ` Konstantin Kharlamov
2023-02-23 16:34 ` Robert Pluim
2023-02-23 16:41 ` bug#61489: bug#61490: " Eli Zaretskii
2023-02-24 10:50 ` Robert Pluim
2023-02-27 10:30 ` bug#61490: " Konstantin Kharlamov
2023-02-23 16:40 ` Eli Zaretskii
2023-03-04 11:26 ` Eli Zaretskii
2023-03-04 15:00 ` Eli Zaretskii
2023-03-04 15:33 ` Konstantin Kharlamov
2023-03-04 18:58 ` Konstantin Kharlamov
2023-03-04 19:53 ` Eli Zaretskii
2023-03-04 19:58 ` Konstantin Kharlamov
2023-03-05 5:47 ` Eli Zaretskii
[not found] ` <handler.61490.B.167631845222751.ack@debbugs.gnu.org>
2023-02-13 20:05 ` bug#61490: Acknowledgement ([PATCH 0/1] Increase BLOCK_ALIGN from 2¹⁰to 2¹⁵) Konstantin Kharlamov
2023-02-16 4:59 ` bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2¹â°to 2¹ⵠRichard Stallman
2023-02-16 6:46 ` Konstantin Kharlamov
2023-02-16 9:31 ` Gregory Heytings
2023-02-21 5:22 ` bug#61490: [PATCH 0/1] Increase BLOCK_ALIGN from 2ùâ°to 2ùâµ Richard Stallman
2023-02-16 15:05 ` bug#61490: [PATCH v2] Increase BLOCK_ALIGN from 1024 to 32768 Konstantin Kharlamov
2023-02-16 15:29 ` Robert Pluim
2023-02-16 16:48 ` Konstantin Kharlamov [this message]
2023-02-16 17:00 ` Konstantin Kharlamov
2023-02-16 17:02 ` Robert Pluim
2023-03-03 10:44 ` 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=2bee6d8548acde05ef32f2c46119f16380e5b817.camel@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=61490@debbugs.gnu.org \
--cc=rpluim@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 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.