Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Exchange Updating Info Problem
Date: Tue, 08 Apr 2008 22:28:53 -0400	[thread overview]
Message-ID: <76lk3noj6i.fsf@dev-d01.ppllc.com> (raw)
In-Reply-To: <86wsn86my5.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 08 Apr 2008 16:44:50 -0500")

>>>>> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:

   TZ> On Thu, 03 Apr 2008 12:41:15 -0400 Jake Colman <colman@ppllc.com> wrote: 
   Jake> If I enter an Exchange IMAP group with alot of read messages, Gnus
   Jake> takes
   Jake> an awfully long time to process.  My imap-log shows the following:
   TZ> ...
   Jake> The result if the "SEARCH SEEN" is a huuuuuge amount of data.  It
   Jake> totally floods my imap-log.
   TZ> ...
   Jake> The problem appears to be the SEARCH SEEN command.

   TZ> For me it generates a long list of integers (UIDs) on an Exchange 2007
   TZ> server (see at end).  Are you seeing something different?  If it's just
   TZ> the 15K article UID numbers, it's unlikely to be the main reason for the
   TZ> slowness on the Gnus side.  I see much more than that in other
   TZ> non-Exchange IMAP groups.  Could it be that Exchange itself is slow, or
   TZ> something else is causing the slowness in Gnus?  If you can run this
   TZ> IMAP command directly against the Exchange server, that would be great.

   TZ> Here's a function to run an IMAP ALL search (untested but copied from
   TZ> working code) which will pop up in the debugger a list of all the
   TZ> messages in the mailbox and two timestamps around the SEARCH operation.
   TZ> You may have to play with it:

   TZ>   (let ((user "you")              ; edit
   TZ> 	(server "yourserver")     ; these
   TZ> 	(password "yourpassword") ; parameters
   TZ> 	(mailbox "INBOX.test"))   ; first
   TZ>     (with-current-buffer (imap-open server nil 'ssl)
   TZ>       (imap-authenticate user password)
   TZ>       (imap-mailbox-select mailbox)      
   TZ>       (debug (format-time-string "before search: %T")
   TZ>              (imap-search "ALL") 
   TZ>              (format-time-string "after search: %T"))
   TZ>       (imap-close)))

   TZ> Hit `q' to close the debugger.  If this is fast, then the "UID SEARCH
   TZ> SEEN" IMAP command is probably fast too.

   TZ> Simon, if my approach is suspect, please let us know.

Ted,

When I evaled your function, I get the following error after it loads
the debugger:

Wrong type argument: stringp, nil

Is the imap-search command incorrect?

...Jake

-- 
Jake Colman
Director of Software Development
Principia Partners LLC
101 West Elm Street
Suite 620
Conshohocken, PA  19428
+1 (610) 755-9786
www.principiapartners.com



  reply	other threads:[~2008-04-09  2:28 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 [this message]
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
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=76lk3noj6i.fsf@dev-d01.ppllc.com \
    --to=colman@ppllc.com \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.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).