From: Dave Liebreich <pixiebob@bigfoot.com>
Subject: Re: pop3 *very* slow?
Date: Thu, 07 Oct 1999 19:11:21 -0700 [thread overview]
Message-ID: <199910080211.TAA28148@oberon.dnai.com> (raw)
In-Reply-To: Stainless Steel Rat's message of "07 Oct 1999 20:14:34 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * 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.
ok.
> Two, the first sleep does not come up until the message being downloaded is
> ~20kB.
None of the messages are over 20kB. All are quite a bit under 20kB.
> Three, the Numero Uno cause of "slow" POP is not the client, but because
> mail is being left on the server.
I don't leave the mail on the server.
I used the elp stuff and found that for a single short message, pop3-retr
was taking 3 seconds.
fetchmail on the same machine for the same message took < .5 seconds.
:-(
Thanks for the suggestions, though.
-Dave
p.s. just looked again at the code:
(while (not (re-search-forward "^\\.\r\n" nil t))
(accept-process-output process 3)
...
)
so that's where the 3 seconds comes from. Is anyone else using this pop
function to get their mail, and if so, do you see each message take 3
seconds?
next prev parent reply other threads:[~1999-10-08 2:11 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
1999-10-08 2:11 ` Dave Liebreich [this message]
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=199910080211.TAA28148@oberon.dnai.com \
--to=pixiebob@bigfoot.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 NNTP newsgroup(s).