From: David Kastrup <dak@gnu.org>
Cc: Eric Hanchrow <offby1@blarg.net>, emacs-devel@gnu.org
Subject: Re: Fix for slow process output processing (please test).
Date: 05 Jan 2004 16:57:14 +0100 [thread overview]
Message-ID: <x5y8smmlr9.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3oetjtjxi.fsf@kfs-l.imdomain.dk>
storm@cua.dk (Kim F. Storm) writes:
> Eric Hanchrow <offby1@blarg.net> writes:
> >
> > I've noticed that shell-mode on very recent (i.e., since after New
> > Year's) versions of CVS Emacs on Windows is quite slow, and the
> > CPU usage is high, for a second or two after I hit RET
> > (comint-send-input). I haven't yet investigated, but if this
> > sounds like it might be related to your patch (which I think, but
> > cannot right now confirm, is present on the Emacs in question),
> > let me know if I can give you any more information.
>
> Does the problem go away if you do
>
> M-: (setq process-adaptive-read-buffering nil) RET
>
> before starting shell-mode ?
>
> I suppose that process-adaptive-read-buffering isn't really needed
> on Windows,
Since Windows is slow, anyway?
> so we could just turn it off in lisp/term/w32-win.el.
I suppose the problem could be that the Windows equivalent of
"select" that Emacs uses does a busy wait without yielding the CPU.
Perhaps this depends on the size of the time slice.
So perhaps it would be nice for experiments to be able to set
process-adaptive-read-buffering to something more complicated, like a
property list setting some parameters, at least for the purpose of
debugging. It might help getting relevant feedback from those using
Windows. Maybe.
On another note, I just recalled that Linux has recently gained
something they called an "anticipative I/O scheduler" which means that
write requests will not cause the process to be scheduled away
immediately, but rather it gets a chance to produce more output (I
don't think that this related to the pipes here, though, but mostly
for disk writes). I don't know whether or not one should adapt the
buzz phrase "adaptive buffering" to rather use "anticipative" as the
latter is already "established" in a way.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-01-05 15:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-16 1:21 Fix for slow process output processing (please test) Kim F. Storm
2003-12-16 2:14 ` David Kastrup
2003-12-16 3:34 ` David Kastrup
2003-12-16 10:23 ` Kim F. Storm
2003-12-16 11:51 ` David Kastrup
2003-12-16 13:24 ` Kim F. Storm
2004-01-03 15:12 ` David Kastrup
2004-01-04 23:00 ` Kim F. Storm
2004-01-03 22:07 ` Eric Hanchrow
2004-01-04 22:42 ` Kim F. Storm
2004-01-05 15:57 ` David Kastrup [this message]
2004-01-05 19:09 ` Eli Zaretskii
2004-01-05 19:39 ` David Kastrup
2004-01-05 19:52 ` Jason Rumney
2004-01-05 23:28 ` Kim F. Storm
2004-01-05 23:16 ` Jason Rumney
2004-01-05 23:44 ` David Kastrup
2004-01-06 0:23 ` Jason Rumney
2004-01-07 0:40 ` Kim F. Storm
2004-01-05 23:35 ` Kim F. Storm
2004-01-05 22:50 ` David Kastrup
2004-01-06 0:09 ` Kim F. Storm
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=x5y8smmlr9.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=offby1@blarg.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).