ability to pause resource intensive global indexing/indexer (existing "disable" deletes previous indexes)

NEW
Unassigned

Status

--
enhancement
9 years ago
5 years ago

People

(Reporter: benjamingslade+mozilla, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0

I like the new indexer feature in TBird 3.0, but it's a performance hog.   When I tried to temporarily disable the indexer, then later reenable it (when my box has spare cycles), it starts reindexing all my email.  This takes several hours since I have years worth of email in archive folders.

So apparently, disabling the "Indexer" really means disable and *delete* existing indexes.

Reproducible: Always

Steps to Reproduce:
1. Enable the indexer the first time, let it finish.
2. Disable the indexer.
3. Reenable the indexer, it will reindex everything
Actual Results:  
Reenabling the indexer reindexes everything

Expected Results:  
Reenabling indexer should resume where it last finished

I have about 600 mbytes of old email in various local mail folders.

Comment 1

9 years ago
The reason that gloda does this is that it must keep track in its index of messages that change, and therefore need to be reindexed. If there is any period of time where it was not doing this tracking, then it cannot trust its indices, and therefore must start over.

I admit this sucks. Still, I think what you really want is a pause indexing feature. That would be fairly easy to add at an extension level. I'll consider adding that in my next refresh of GlodaQuilla.
(Reporter)

Comment 2

9 years ago
Re: I think what you really want is a pause indexing feature

Yes, I think that would be really useful.  Should I (you) close this ticket and I can open a new one specifically requesting a pause indexing feature?
(Reporter)

Comment 3

9 years ago
Are you saying you'd add a "pause indexing" feature to the "experimental" add-on GlodaQuilla? ("intended for developers and testers")   

I think adding a "pause indexing" checkbox next to the existing "Enable Global Search and Indexer" checkbox in the core Thunderbird product would be preferable.

(In reply to comment #1)
> ...I think what you really want is a pause indexing
> feature. That would be fairly easy to add at an extension level. I'll consider
> adding that in my next refresh of GlodaQuilla.

Comment 4

9 years ago
GlodaQuilla is rapidly morphing beyond the original "developer" target, as there are some glaring omissions in gloda management (such as the ability to restrict which folders get indexed, or the current request for a pause feature) that I have started to fix there. I still need to do some work on it though to make it production-ready (such as remove any existing indexing when a folder is de-indexed) before I move it out of experimental into public. But the answer to your question 'Are you saying you'd add a "pause indexing" feature to the "experimental" add-on GlodaQuilla? ("intended for developers and testers")' (which i took as mildly ironic) is yes.

As to the current bug, I would suggest that you morph it into a request to add the "pause" function by simply changing the summary. And yes I agree that pause should be part of core functionality, and that anything I do in GlodaQuilla is intended as a stopgap.
(Reporter)

Comment 5

9 years ago
Ok, thanks very much for the clear explanation and the quick response.

FYI, "intended for developers and testers" was just quoting https://addons.mozilla.org/en-US/thunderbird/addon/9873 , no irony intended.

I've changed the title of this ticket and made it an enhancement request.
Severity: normal → enhancement
OS: Windows XP → All
Hardware: x86 → All
Summary: If I disable, then reenable the indexer, it reindexes everything → The user should be able to pause the resource intensive indexer (existing "disable" deletes previous indexes)
Version: unspecified → 3.0

Comment 6

9 years ago
Confirming. If you have a new profile the initial indexing ties up substantial resources, or if you restart after a while and a lot of messages came in since the last download or synchronization. Maybe have a "Pause" button in the Activity Manager, or at some other easy to reach place?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Version: 3.0 → Trunk
(Reporter)

Comment 7

9 years ago
Actually, I think you misread the description of the problem here.   If you restart indexing, it doesn't make any difference how many recent messages have come in, the restarted indexing will process all emails, including reprocessing emails that were previously indexed.

But in any case, the pause indexing button sounds like a good idea.

(In reply to comment #6 by rsx11m)
> Confirming. If you have a new profile the initial indexing ties up substantial
> resources, or if you restart after a while and a lot of messages came in since
> the last download or synchronization. Maybe have a "Pause" button in the
> Activity Manager, or at some other easy to reach place?

Comment 8

5 years ago
(In reply to Ben Slade (append 030516 to subj to get thru) from comment #7)
> Actually, I think you misread the description of the problem here.   If you
> restart indexing, it doesn't make any difference how many recent messages
> have come in, the restarted indexing will process all emails, including
> reprocessing emails that were previously indexed.

I've never noticed such behavior, and I have at times turned off indexing. So I'm thinking "existing "disable" deletes previous indexes" is inaccurate. 

That said, anyone who sees resource usage causing more than insignificant impact to user response should file a bug against the behavior so it an be addressed.
Summary: The user should be able to pause the resource intensive indexer (existing "disable" deletes previous indexes) → ability to pause resource intensive global indexing/indexer (existing "disable" deletes previous indexes)
You need to log in before you can comment on or make changes to this bug.