From: Lars Ingebrigtsen <larsi@gnus.org>
To: Herman@debbugs.gnu.org, Géza <geza.herman@gmail.com>
Cc: 44007@debbugs.gnu.org
Subject: bug#44007: 26.3; Strange shell mode performance
Date: Sat, 29 Jan 2022 15:38:00 +0100 [thread overview]
Message-ID: <87k0eid2uv.fsf@gnus.org> (raw)
In-Reply-To: <ae78c410-3232-ee38-84d0-7bfde16a1cc8@gmail.com> ("Herman, Géza"'s message of "Fri, 28 Jan 2022 23:33:47 +0100")
"Herman, Géza" <geza.herman@gmail.com> writes:
> How much time does "seq 100000" take for you? Does it use 100% cpu?
emacs -Q
M-x shell
seq 100000
takes very little time for me -- perhaps 0.2s?
If I add a zero, it takes about five seconds, but hitting RET in the
middle doesn't affect the speed.
> Maybe the OS matters here (how the read() syscall behaves): I'm on
> debian linux (sid).
I'm on Debian/bookworm...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-01-29 14:38 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 [this message]
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
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=87k0eid2uv.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44007@debbugs.gnu.org \
--cc=Herman@debbugs.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.