From: Tim Cross <tcross@nospam.une.edu.au>
Subject: Re: remote X11/GNU emacs/ssh: Incredible slowness loading libs
Date: 01 Oct 2002 17:31:54 +1000 [thread overview]
Message-ID: <87adlyaa39.fsf@blind-bat.une.edu.au> (raw)
In-Reply-To: xcvk7l347l8.fsf@famine.OCF.Berkeley.EDU
tfb@famine.OCF.Berkeley.EDU (Thomas F. Burdick) 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. 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.
>
> 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. 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.
While this may not solve the problem, it might improve performance if
you also use something like dxcp to get some additional compression of
X protocol packets. also, since you are doing X over an ssh
connection, try playing with the ssh compression levels. Also try
executing other X applications and see if they have the same
slowness. I would also turn off any "features" which you don't
need/use like the toolbar. Also, make sure the fonts you are using are
available on both machines - sometimes you can get really slow
performance if the remote font specified for emacs is not available
locally or is available, but mapping takes additional time
etc. Although it might sound crazy, it may also be worth doing some
traceroutes to check where the packets are going to get to your
system.
Good luck
T
next prev parent reply other threads:[~2002-10-01 7:31 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
2002-10-01 7:31 ` Tim Cross [this message]
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=87adlyaa39.fsf@blind-bat.une.edu.au \
--to=tcross@nospam.une.edu.au \
/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).