From: Andreas Schwab <schwab@suse.de>
Cc: "Jan D." <jan.h.d@swipnet.se>
Subject: Re: Any idea about what makes Emacs slow reading on pipes?
Date: Fri, 16 May 2003 23:00:51 +0200 [thread overview]
Message-ID: <jellx67gjg.fsf@sykes.suse.de> (raw)
In-Reply-To: <x54r3uka7z.fsf@lola.goethe.zz> (David Kastrup's message of "16 May 2003 20:38:56 +0200")
David.Kastrup@t-online.de (David Kastrup) writes:
|> "Jan D." <jan.h.d@swipnet.se> writes:
|>
|> > >
|> > > The following exhibits abysmal speed within Emacs:
|> > >
|> > > (let (process-connection-type) (switch-to-buffer (generate-new-buffer
|> > > "*test*"))(erase-buffer)(start-process "test" (current-buffer) "sh"
|> > > "-c" "hexdump -v /dev/zero|dd bs=1 count=100k")(erase-buffer))
|> >
|> > ...
|> >
|> > > The system I see this in is
|> > > GNU Emacs 21.3.50.3 (i686-pc-linux-gnu)
|> > > a RedHat 9 system, but I have seen this in practically every Linux
|> > > system up to now. Is this a Linux-specific problem, or do others see
|> > > this as well?
|> >
|> > I could not reproduce this on a slackware (version unknown, but libc 6)
|> > or a Mandrake 9.0 system. Maybe running under strace can give some
|> > indication of the system call that takes time (if that is the issue)?
|>
|> Here is a more elaborate test file
Tried on ppc-suse-linux, I get constant throughput of 1024 characters at a
time. On MacOS X (through MOL) I get varying packet sizes between 97 and
1024.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-05-16 21:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 13:08 Any idea about what makes Emacs slow reading on pipes? David Kastrup
2003-05-16 13:55 ` Andreas Schwab
2003-05-16 17:18 ` Kevin Rodgers
2003-05-16 17:34 ` David Kastrup
2003-05-16 18:38 ` Kevin Rodgers
2003-05-16 18:49 ` David Kastrup
2003-05-16 17:48 ` Jan D.
2003-05-16 18:38 ` David Kastrup
2003-05-16 20:23 ` Jan D.
2003-05-16 21:00 ` Andreas Schwab [this message]
2003-05-16 23:17 ` Satyaki Das
2003-05-17 1:50 ` Kim F. Storm
2003-05-17 0:34 ` David Kastrup
2003-05-18 0:31 ` Kim F. Storm
2003-05-17 23:07 ` Stefan Monnier
2003-05-17 23:39 ` David Kastrup
2003-05-18 2:09 ` Stefan Monnier
2003-05-18 8:45 ` Kai Großjohann
2003-05-18 10:12 ` David Kastrup
2003-05-18 19:04 ` Richard Stallman
2003-05-18 19:46 ` David Kastrup
2003-05-19 7:33 ` Kai Großjohann
2003-05-19 8:24 ` David Kastrup
2003-05-18 8:46 ` Kai Großjohann
2003-05-18 10:03 ` David Kastrup
2003-05-18 15:09 ` Kai Großjohann
2003-05-18 15:36 ` David Kastrup
2003-05-18 15:50 ` Kai Großjohann
2003-05-18 16:28 ` David Kastrup
2003-05-19 7:26 ` Kai Großjohann
2003-05-19 8:09 ` David Kastrup
2003-05-18 19:03 ` Richard Stallman
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=jellx67gjg.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=jan.h.d@swipnet.se \
/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).