From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/51100 Path: main.gmane.org!not-for-mail From: David Abrahams Newsgroups: gmane.emacs.gnus.general Subject: Re: nnimap slowness Date: Sun, 30 Mar 2003 17:12:40 -0500 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1049062410 31686 80.91.224.249 (30 Mar 2003 22:13:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 30 Mar 2003 22:13:30 +0000 (UTC) Original-X-From: owner-ding@hpc.uh.edu Mon Mar 31 00:13:29 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18zl3Q-0008Eo-00 for ; Mon, 31 Mar 2003 00:13:29 +0200 Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=lists) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 18zl39-0003K8-00; Sun, 30 Mar 2003 16:13:11 -0600 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sun, 30 Mar 2003 16:14:14 -0600 (CST) Original-Received: from stlport.com (stlport.com [64.39.31.56]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id QAA10451 for ; Sun, 30 Mar 2003 16:14:03 -0600 (CST) Original-Received: from [146.115.123.42] (account dave HELO PENGUIN.boost-consulting.com) by stlport.com (CommuniGate Pro SMTP 3.5.9) with ESMTP id 216875; Sun, 30 Mar 2003 14:12:55 -0800 Original-To: ding@hpc.uh.edu In-Reply-To: (Simon Josefsson's message of "Sun, 30 Mar 2003 21:20:20 +0200") User-Agent: Gnus/5.090016 (Oort Gnus v0.16) Emacs/21.3.50 (i386-msvc-nt5.1.2600) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:51100 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:51100 Thanks for following up, Simon... Simon Josefsson writes: > David Abrahams writes: > >>> For small data, the cause is much more likely to be server slowness or >>> network latency, so please send try sending a 5MB attachment or >>> something. >> >> OK, here: > > Function Name Call Count Elapsed Time Average Time > ================================== ========== ============ ============ > gnus-summary-reselect-current-group 1 8.132 8.132 > gnus-summary-rescan-group 1 8.132 8.132 > nnimap-request-group 2 6.43 3.215 > imap-send-command-wait 14 6.339 0.4527857142 > imap-wait-for-tag 14 6.339 0.4527857142 > nnimap-request-update-info-internal 2 6.2989999999 3.1494999999 > imap-search 11 5.927 0.5388181818 > gnus-group-get-new-news-this-group 1 4.055 4.055 > gnus-summary-read-group 1 3.586 3.586 > gnus-group-read-group 1 3.586 3.586 > gnus-summary-read-group-1 1 3.586 3.586 > gnus-select-newsgroup 1 3.526 3.526 > gnus-activate-group 1 3.465 3.465 > gnus-request-group 1 2.965 2.965 > gnus-retrieve-headers 2 0.58 0.29 > ... > > It seems the IMAP SEARCH command is causing the delay (most of the > nnimap related delay is in imap-search), suggesting that the server > opens large messages when the SEARCH command is invoked. This is > unnecessary, since Gnus only searches for flags (unseen, seen, ticked, > etc). Perhaps you could forward this observation (after verifying it > in the source) The source of what? > to the IMAP server administrator/developers to have them improve > searches for flags. We're using Communigate Pro, for what that's worth to you. -- Dave Abrahams Boost Consulting www.boost-consulting.com