Closed
Bug 622559
Opened 14 years ago
Closed 3 years ago
Make asynchronous history loading more asynchronous
Categories
(Camino Graveyard :: History, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: stuart.morgan+bugzilla, Unassigned)
Details
Starting with the patch for bug 506345, we start loading history asynchronously at startup. Unfortunately, the initial setup piece has a step that takes a long time with a large history. From my comment in the other bug (using cl's ginormous history file):
"Calling SetContainerOpen during the initial setup takes me 15 seconds, so
that's where the problem is. I'm not sure how much can be done about that...
maybe doing N queries with time ranges of some number of days."
We should see if we can do this for 2.1, since it is a regression for people with large histories. I don't think I'd block for it though, since it seems like having other history operations (opening the History menu and the History manager) not take a super-long time once launched is a win that hopefully helps balance it out. We'll see how the feedback is and decide priority accordingly.
|
Reporter | |
Comment 1•14 years ago
|
||
I'm not realistically going to get to this for 2.1. It doesn't seem like it's been a pain point for too many people; hopefully it won't be for the final release either. If it is, I'll try to prioritize it for 2.1.x.
Target Milestone: Camino2.1 → ---
|
||
Comment 2•3 years ago
|
||
This bug lies at rest in the graveyard.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•