From: Eli Zaretskii <eliz@elta.co.il>
Subject: Re: high-latency, high-bandwidth link => slow startup
Date: 13 Aug 2003 14:54:52 +0200 [thread overview]
Message-ID: <uoeytwwdf.fsf@elta.co.il> (raw)
In-Reply-To: <81wudhhlyi.fsf@shasta.cs.uiuc.edu> (message from Lars Clausen on Wed, 13 Aug 2003 05:48:53 -0500)
> Newsgroups: gnu.emacs.help
> From: Lars Clausen <lrclause@cs.uiuc.edu>
> Date: Wed, 13 Aug 2003 05:48:53 -0500
>
> [...] the startup time is horrible. It
> can take several minutes to start up Emacs + Gnus, whereas locally it takes
> a matter of seconds, and even on a text-only terminal of equivalent latency
> and lower bandwidth is it much faster. What is it about remote X that
> makes the startup so slow? Can Emacs be tweaked to work better in
> high-bandwidth/high-latency situations (which I would think would become
> more common as more people get high-bandwidth connections and remote use
> becomes more common)? I'm not doing graphics-heavy stuff, maybe font
> loading is a problem?
IIRC, the PROBLEMS file has an entry that lists some ``popular''
network-related reasons for slow startup, and a couple of
recommendations for speeding it up. Perhaps one of the
recommendations will help you.
prev parent reply other threads:[~2003-08-13 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 10:48 high-latency, high-bandwidth link => slow startup Lars Clausen
2003-08-13 12:54 ` Eli Zaretskii [this message]
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=uoeytwwdf.fsf@elta.co.il \
--to=eliz@elta.co.il \
/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).