From: Antoine Levitt <antoine.levitt@gmail.com>
To: ding@gnus.org
Subject: Re: pop3 speedup
Date: Mon, 26 Sep 2011 21:34:53 +0200 [thread overview]
Message-ID: <87pqinw10i.fsf@gmail.com> (raw)
In-Reply-To: <m3pqinw19y.fsf@stories.gnus.org>
26/09/11 21:29, Lars Magne Ingebrigtsen
> Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:
>
>> _exponential_? How does an algorithm for POP3 mail fetching with such a
>> complexity look like?
>
> The old algorithm counted all the messages in the buffer from the start
> repeatedly while waiting for them all to arrive. So if you fetched 1000
> messages, it would typically first count 10 messages, then it would
> count 20, then it would count 30, all the way up to 1000.
>
> Hm. Is that exponential?
Nope, it's n^2, polynomial (1 + 2 + 3 + 4 ... + n is about n^2/2).
next prev parent reply other threads:[~2011-09-26 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 18:37 Lars Magne Ingebrigtsen
2011-09-26 19:16 ` Matthias Andree
2011-09-26 19:29 ` Lars Magne Ingebrigtsen
2011-09-26 19:34 ` Antoine Levitt [this message]
2011-09-26 19:35 ` Lars Magne Ingebrigtsen
2011-09-26 19:55 ` Antoine Levitt
2011-09-26 20:09 ` Matthias Andree
2011-09-26 20:01 ` Matthias Andree
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=87pqinw10i.fsf@gmail.com \
--to=antoine.levitt@gmail.com \
--cc=ding@gnus.org \
/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).