From: "Herman, Géza" <geza.herman@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Strange shell mode performance
Date: Wed, 14 Oct 2020 12:49:06 +0200 [thread overview]
Message-ID: <e1a9c41d-3fd5-07f7-9282-c3529d610d1e@gmail.com> (raw)
Hi all,
I'm experiencing strange shell (comint) mode performance. If I cat a 10
MB file, it takes 1:20 to cat it. Emacs uses only 30% cpu. But, if I
press enter after I send the cat command, it speeds up, and it only
takes 8 sec (emacs cpu usage goes up to 100%).
Same thing: if I execute "seq 100000" in a small emacs window, it takes
~3 seconds. But, if I press enter after executing seq, it takes only 0.4
sec (this is not 100% reproducible, sometimes pressing enter doesn't
make a difference).
(I executed comint-clear-buffer before measurements)
It happens with 26.3 and ~3-week-old master branch as well, without any
extra config (emacs -Q).
Any ideas what causes this? Would it be possible to always have the
better performance without needing to press enter?
Thanks,
Geza
next reply other threads:[~2020-10-14 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 10:49 Herman, Géza [this message]
2020-10-14 17:32 ` Strange shell mode performance Stefan Monnier
2020-10-21 1:27 ` Robert Thorpe
2020-10-21 10:27 ` 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
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=e1a9c41d-3fd5-07f7-9282-c3529d610d1e@gmail.com \
--to=geza.herman@gmail.com \
--cc=help-gnu-emacs@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.
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).