Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: pop3 *very* slow?
Date: 07 Oct 1999 20:14:34 -0400	[thread overview]
Message-ID: <m3d7uqso7p.fsf@peorth.gweep.net> (raw)
In-Reply-To: Dave Liebreich's message of "Thu, 07 Oct 1999 14:54:37 -0700"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Dave Liebreich <pixiebob@bigfoot.com>  on Thu, 07 Oct 1999
| and it's *very* slow.  Are the following lines in pop3.el really necessary?

One, yes, those sleeps are necessary.  Without them Emacs hangs on large
messages.

Two, the first sleep does not come up until the message being downloaded is 
~20kB.  By comparison, the average message on ding is between 4kB and 8kB,
less than half that initial threshold.  Given that, the 1-second pause a
20kB message incurs (and the 5-second pause a 500kB message causes) is
negligible.

Three, the Numero Uno cause of "slow" POP is not the client, but because
mail is being left on the server.  Every time you open your POP drop, the
server must make a copy of the spool file to properly lock it.  The larger
the spool file, the longer it takes to copy, and the slower your response
from the server will be.  Try deleting those messages if there are any and
see if that helps.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE3/Tdqgl+vIlSVSNkRAuKVAJsF7GckxB1vsXqWewblJJSNIH9c8ACdFKby
222SoFb0YJx1D/VyWpJMrHw=
=nmnY
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@peorth.gweep.net>    \ If Happy Fun Ball begins to smoke, get
Minion of Nathan - Nathan says Hi! \ away immediately. Seek shelter and cover
PGP Key: at a key server near you!  \ head.


  reply	other threads:[~1999-10-08  0:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-07 21:54 Dave Liebreich
1999-10-08  0:14 ` Stainless Steel Rat [this message]
1999-10-08  2:11   ` Dave Liebreich
1999-10-08  5:17   ` Dave Liebreich
1999-10-08 23:24     ` Stainless Steel Rat
1999-10-08 20:31   ` Greg Stark
1999-10-08 23:26     ` Stainless Steel Rat

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3d7uqso7p.fsf@peorth.gweep.net \
    --to=ratinox@peorth.gweep.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.
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 NNTP newsgroup(s).