From: Ted Zlatanov <tzz@lifelogs.com>
To: James Cloos <cloos@jhcloos.com>
Cc: Jake Colman <colman@ppllc.com>, ding@gnus.org
Subject: Re: Exchange Updating Info Problem
Date: Thu, 10 Apr 2008 08:12:24 -0500 [thread overview]
Message-ID: <86od8h6eh3.fsf@lifelogs.com> (raw)
In-Reply-To: <m3fxtuix54.fsf@lugabout.jhcloos.org> (James Cloos's message of "Wed, 09 Apr 2008 16:35:44 -0400")
On Wed, 09 Apr 2008 16:35:44 -0400 James Cloos <cloos@jhcloos.com> wrote:
>>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:
Ted> For me it generates a long list of integers (UIDs) on an Exchange
Ted> 2007 server (see at end). Are you seeing something different? If
Ted> it's just the 15K article UID numbers,
JC> Parsing those 15k digit strings into ints and then compressing them into
JC> ranges can take a lot of CPU when done in elisp.
JC> Especially when there are gaps.
Sure, but can it be avoided? I don't think the Gnus flags map directly
to IMAP flags, so it's possible there are SEEN messages that need to be
retrieved. I think someone with in-depth knowledge of the relevant
nnimap and imap code should comment.
In addition, I don't think processing a list 15,000 integers is too slow
with Emacs Lisp on a modern machine.
The other issue is that the SEARCH SEEN itself takes a long time, over a
minute according to Jake's calculation. See his followup. So the
number of UIDs may be a red herring.
Ted
next prev parent reply other threads:[~2008-04-10 13:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 16:41 Jake Colman
2008-04-08 21:44 ` Ted Zlatanov
2008-04-09 2:28 ` Jake Colman
2008-04-09 16:26 ` Jake Colman
2008-04-09 20:30 ` Ted Zlatanov
2008-04-09 20:35 ` James Cloos
2008-04-10 13:12 ` Ted Zlatanov [this message]
2008-04-10 14:51 ` James Cloos
2008-04-10 18:18 ` Jake Colman
2008-04-10 18:55 ` Ted Zlatanov
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=86od8h6eh3.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=cloos@jhcloos.com \
--cc=colman@ppllc.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).