Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Cc: jas@extundo.com
Subject: Re: nnimap slowness
Date: Sat, 22 Mar 2003 22:20:02 -0500	[thread overview]
Message-ID: <uel4yrcpp.fsf@boost-consulting.com> (raw)
In-Reply-To: <iluof43waor.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sat, 22 Mar 2003 18:52:36 +0100")

Simon Josefsson <jas@extundo.com> writes:

> To find out what causes slowness for small data, you must tcpdump or
> ethereal the stream to see which side is delaying the transfer, or if
> it is the network that has high latency.  ELP data isn't that useful
> in this case.

I got myself a copy of Ethereal and captured packets from a `M-G', but
I have no clue yet as to how to get any useful information from what
I'm seeing...

...I hate to keep harping on this, but it really has the look/feel of
some inefficiency in what GNUs is doing.

Looking at the packets one more time it sure looks very much as though
GNUs is receiving the same sequence of packets (about 27K worth) twice
from the IMAP server, though it's pretty hard for me to tell
anything, especially peering through SSL encoding.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com




  parent reply	other threads:[~2003-03-23  3:20 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21 21:51 David Abrahams
2003-03-22  0:54 ` Simon Josefsson
2003-03-22  1:21   ` David Abrahams
2003-03-22  3:51     ` Simon Josefsson
2003-03-22 16:55       ` David Abrahams
2003-03-22 17:12         ` Simon Josefsson
2003-03-22 17:18           ` David Abrahams
2003-03-22 17:52             ` Simon Josefsson
2003-03-22 18:48               ` David Abrahams
2003-03-30 19:20                 ` Simon Josefsson
2003-03-30 22:12                   ` David Abrahams
2003-03-31 12:30                     ` Simon Josefsson
2003-03-31 22:31                       ` David Abrahams
2003-04-01 11:20                         ` Simon Josefsson
2003-03-31  1:13                   ` Krzysztof Jędruczyk
2003-03-31 12:33                     ` Simon Josefsson
2003-03-31 16:51                     ` Lars Magne Ingebrigtsen
2003-03-31 17:18                       ` Lars Magne Ingebrigtsen
2003-03-31 17:25                       ` Simon Josefsson
2003-04-13 13:45                       ` Krzysztof Jędruczyk
2003-04-18 13:50                         ` David Abrahams
2003-04-18 15:16                           ` David Abrahams
2003-04-19 18:34                             ` Kai Großjohann
2003-04-18 15:44                           ` David Abrahams
2003-04-19 18:35                             ` Kai Großjohann
2003-04-20  9:28                               ` David Abrahams
2003-04-18 19:01                           ` A.J. Rossini
2003-04-18 19:19                             ` David Abrahams
2003-04-19  6:28                               ` Steinar Bang
2003-04-19 20:07                               ` Frank Schmitt
2003-03-23  3:20               ` David Abrahams [this message]
2003-03-22 18:47         ` Jody Klymak
2003-03-24  9:12           ` Niklas Morberg

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=uel4yrcpp.fsf@boost-consulting.com \
    --to=dave@boost-consulting.com \
    --cc=jas@extundo.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).