39 lines
1.7 KiB
Plaintext
39 lines
1.7 KiB
Plaintext
MBOX-Line: From tss at iki.fi Thu Dec 21 15:08:00 2006
|
|
To: imap-protocol@u.washington.edu
|
|
From: Timo Sirainen <tss@iki.fi>
|
|
Date: Fri Jun 8 12:34:38 2018
|
|
Subject: [Imap-protocol] Command cancellation
|
|
In-Reply-To: <alpine.WNT.0.81.0612201323310.3064@Shimo-Tomobiki.panda.com>
|
|
References: <1166644158.22214.365.camel@hurina>
|
|
<alpine.WNT.0.81.0612201323310.3064@Shimo-Tomobiki.panda.com>
|
|
Message-ID: <1166742480.22214.496.camel@hurina>
|
|
|
|
On Wed, 2006-12-20 at 14:12 -0800, Mark Crispin wrote:
|
|
> On Wed, 20 Dec 2006, Timo Sirainen wrote:
|
|
> > I wanted an ability to stop an ongoing SEARCH command, so that it'd be
|
|
> > possible to add a "Cancel search" button in the client.
|
|
>
|
|
> How long do searches take in your server?
|
|
|
|
Actually the search itself isn't really the problem here, it's the text
|
|
search index building which is much slower than the search.
|
|
|
|
Because most users don't use SEARCH in all of their mailboxes (if any),
|
|
I'm delaying the initial building until the user does SEARCH for the
|
|
first time. If the mailbox is large, it's going to take time. With my
|
|
computer it's currently indexing only 1,5MB/s (CPU limited).
|
|
|
|
I did think about simply doing a normal search first, and then start
|
|
building the indexes on the background so the future searches will be
|
|
fast. Maybe I'll do that also later.
|
|
|
|
(I'm here talking about an indexer that supports substring searches so
|
|
it'll work with standard TEXT and BODY searches)
|
|
-------------- next part --------------
|
|
A non-text attachment was scrubbed...
|
|
Name: signature.asc
|
|
Type: application/pgp-signature
|
|
Size: 196 bytes
|
|
Desc: This is a digitally signed message part
|
|
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20061222/eeb18b29/attachment.sig>
|