From: storm@cua.dk (Kim F. Storm)
Cc: offby1@blarg.net, Eli Zaretskii <eliz@elta.co.il>,
David Kastrup <dak@gnu.org>,
emacs-devel@gnu.org
Subject: Re: Fix for slow process output processing (please test).
Date: 07 Jan 2004 01:40:51 +0100 [thread overview]
Message-ID: <m34qv8fv58.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <uwu86c7gr.fsf@jasonrumney.net>
Jason Rumney <jasonr@gnu.org> writes:
> I have tried running the code, but I'm not sure I understand this well
> enough to interpret the results. With adaptive buffering on, we get
> more 1024 byte blocks, but we get nothing for Time: 0 (which may be a
> symptom of the noticeable delay that was reported?), and we also have
> a Time: 9, which I think might mean it is taking longer overall. The
> numbers are all in at least the high hundreds for both tests, so maybe
> Windows is doing some buffering behind the scenes anyway.
I just made a small adjustment to the adaptive read buffering
algorithm, which I think will make it behave better on Windoze
(without making it behave worse with Linux kernels).
Please test the new version, and see if it behaves better than before.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-01-07 0:40 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
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 [this message]
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=m34qv8fv58.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=dak@gnu.org \
--cc=eliz@elta.co.il \
--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).