From: "David Abrahams" <david.abrahams@rcn.com>
Subject: Re: remote X11/GNU emacs/ssh: Incredible slowness loading libs
Date: Mon, 30 Sep 2002 16:14:30 -0400 [thread overview]
Message-ID: <anadml$pvs$1@bob.news.rcn.net> (raw)
In-Reply-To: xcvk7l347l8.fsf@famine.OCF.Berkeley.EDU
"Thomas F. Burdick" <tfb@famine.OCF.Berkeley.EDU> wrote in message
news:xcvk7l347l8.fsf@famine.OCF.Berkeley.EDU...
> "David Abrahams" <david.abrahams@rcn.com> writes:
>
> You didn't say explicitly (I don't think), but you impleid that you're
> using Emacs 21. 21 is *much* *much* slower over a forwarded X11
> connection than 20.7 was.
Yes, I noticed that. I am using 21.x
> I'm not sure what's in all the network
> traffic, but it generates a lot. If I'm working over an ssh/X11 link,
> I never use 21.
Somebody must know what it's doing with all those packets (and how to turn
them off)! Anyone? Bueller?
> The other problem you could be having is dropped packets. ssh/X11
> connections in general seem to be really sensitive to dropped packets,
> and too many of them will cause the connection to just hang for a
> while. Combined with Emacs 21's chattiness, this can be really
> unpleasant.
>
> Finally, if the remote server is Linux 2.4, I'm sorry.
Linux, AIX, OSF, it doesn't seem to matter. In fact, the Linux machines I've
used tend to be the snappiest of the lot.
> I've noticed
> that its scheduler isn't very nice to interactive applications over an
> ssh/X11 connection. It seems to want to give them fewer timeslices of
> a longer duration than you'd want. I have had a much better time with
> Solaris, or Linux 2.2.
>
> --
> /|_ .-----------------------.
> ,' .\ / | No to Imperialist war |
> ,--' _,' | Wage class war! |
> / / `-----------------------'
> ( -. |
> | ) |
> (`-. '--.)
> `. )----'
Hmm, a talking cat. Isn't that a sign of the Apocalypse?
--
-----------------------------------------------------------
David Abrahams * Boost Consulting
dave@boost-consulting.com * http://www.boost-consulting.com
next prev parent reply other threads:[~2002-09-30 20:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 16:26 remote X11/GNU emacs/ssh: Incredible slowness loading libs David Abrahams
2002-09-29 20:21 ` Kai Großjohann
2002-09-29 20:52 ` David Abrahams
2002-09-29 23:00 ` Edward O'Connor
2002-09-29 23:31 ` David Abrahams
2002-09-30 9:11 ` David Kastrup
2002-09-30 12:04 ` David Abrahams
2002-09-30 12:48 ` David Kastrup
2002-09-30 13:52 ` David Abrahams
2002-09-30 19:10 ` Thomas F. Burdick
2002-09-30 20:14 ` David Abrahams [this message]
2002-10-01 7:31 ` Tim Cross
2002-10-01 10:42 ` David Abrahams
2002-10-01 11:36 ` David Kastrup
2002-10-01 12:15 ` David Abrahams
2002-10-02 7:42 ` Matthew Kennedy
2002-09-30 15:04 ` Heinz Rommerskirchen
2002-09-30 14:28 ` Kai Großjohann
2002-09-30 18:34 ` David Abrahams
2002-09-30 21:58 ` Krishnakumar B
2002-09-30 21:46 ` David Abrahams
2002-09-30 23:08 ` Krishnakumar B
2002-09-30 23:40 ` David Abrahams
2002-10-01 0:40 ` Christopher Browne
2002-10-01 0:13 ` David Abrahams
2002-10-01 2:28 ` Krishnakumar B
2002-10-01 2:57 ` David Abrahams
2002-10-01 15:06 ` Richard V. Molen
2002-10-01 15:25 ` David Abrahams
2002-10-01 16:59 ` Richard V. Molen
2002-10-01 16:43 ` David Abrahams
2002-10-01 18:10 ` Richard V. Molen
2002-09-29 21:26 ` Krishnakumar B
2002-09-29 22:16 ` David Abrahams
2002-10-03 18:30 ` frobware inc
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='anadml$pvs$1@bob.news.rcn.net' \
--to=david.abrahams@rcn.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.
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).