From: Dmitry Gutov <dmitry@gutov.dev>
To: Herman@debbugs.gnu.org, Géza <geza.herman@gmail.com>,
"Eli Zaretskii" <eliz@gnu.org>
Cc: 44007@debbugs.gnu.org
Subject: bug#44007: 26.3; Strange shell mode performance
Date: Tue, 7 Nov 2023 00:47:16 +0200 [thread overview]
Message-ID: <0a570b23-5e7a-1203-d331-afd97a0aa018@gutov.dev> (raw)
In-Reply-To: <87zfzrx8hy.fsf@gmail.com>
On 06/11/2023 15:37, Herman@debbugs.gnu.org wrote:
>
> I think it is a bug because Emacs doesn't try to read again if one
> read() was successful. My hacky solution fixes that. With the extra
> cost of one read syscall. But we can do better: we can avoid it if the
> first read call already read 'nbyte' bytes, then there is no need to
> call another read().
FWIW, when I tested different options for bug#66020 (see for example
https://debbugs.gnu.org/66020#58), increasing the default buffer size is
anyway the simplest way to get to top performance without sacrificing
reliability.
There are some patches attached in the subsequent message, BTW, that one
could try out.
next prev parent reply other threads:[~2023-11-06 22:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 9:53 bug#44007: 26.3; Strange shell mode performance Herman, Géza
2020-10-15 14:10 ` Eli Zaretskii
2020-10-15 14:34 ` Herman, Geza
2020-10-16 8:25 ` Andreas Röhler
2022-01-28 15:26 ` Lars Ingebrigtsen
2022-01-28 22:33 ` Herman, Géza
2022-01-29 6:52 ` Eli Zaretskii
2022-01-29 14:38 ` Lars Ingebrigtsen
2022-01-29 16:10 ` Herman, Géza
2023-11-05 16:46 ` Herman, Géza
2023-11-06 12:08 ` Eli Zaretskii
2023-11-06 12:28 ` Herman, Géza
2023-11-06 13:22 ` Eli Zaretskii
2023-11-06 13:37 ` Herman, Géza
2023-11-06 14:40 ` Eli Zaretskii
2023-11-06 15:00 ` Herman, Géza
2023-11-06 16:52 ` Eli Zaretskii
2023-11-06 17:25 ` Herman, Géza
2023-11-06 22:47 ` Dmitry Gutov [this message]
2020-10-16 10:44 ` Herman, Géza
2020-10-16 10:55 ` Eli Zaretskii
2020-10-16 12:23 ` Herman, Géza
2020-10-17 12:48 ` Herman, Géza
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=0a570b23-5e7a-1203-d331-afd97a0aa018@gutov.dev \
--to=dmitry@gutov.dev \
--cc=44007@debbugs.gnu.org \
--cc=Herman@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=geza.herman@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.