132729 - offline searches on large, replicated mab is slow (UI blocks, too)

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Address Book & Contacts, defect)

Description

[(not reading, please use [e-mail] instead)]

offline searches on large, replicated mab is slow (UI blocks, too)

we kind of already knew this.

using rajiv's ldap replication code, I've now got a 10k .mab file with about 
26k entries.  (I replicated the netscape phonebook.)

when I go offline and try to quick search against it, the UI blocks and the 
search takes a long time.

I'm seeing the CPU get pinged for several seconds, and since the addressbook 
code runs on the UI thread, that explains what it blocks the UI.

note, this would happen with a large personal addressbook, it's just not likely 
you'd have a PAB of this size, where as with replication it's more likely

time to break out quantify!

Comment 1

[(not reading, please use [e-mail] instead)]

moving off to 1.0.1

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420