Closed
Bug 582463
Opened 14 years ago
Closed 7 years ago
Places spends a large amount of time in MatchAutoCompleteFunction::OnFunctionCall()
Categories
(Toolkit :: Places, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jrmuizel, Unassigned)
Details
On startup after I start typing in URL bar and places seems to spend a very large amount of time hanging my browser. I profiled it and 90% of the time was in sqlite3_step under which we spent 50% of the time in MatchAutoCompleteFunction.
Comment 1•14 years ago
|
||
Note: it's highly unlikely that you are hanging in that seeing as how it's not running on the main thread. I should maybe add some assertions just to make sure about that though...
Reporter | ||
Comment 2•14 years ago
|
||
It's true, the time was not being spent on the main thread. Perhaps something on the main thread is waiting for something on the storage thread to complete?
Comment 3•14 years ago
|
||
We've had a few of these bugs crop up recently, so possible :/
Reporter | ||
Comment 4•14 years ago
|
||
As an aside, do we have any way of exposing performance information on what sqlite is doing. i.e. statistics on how often we hit and miss in the page cache. I often see sqlite3_step etc. show up in profiles but it's hard to do much with the results or to tell how efficient sqlite is being.
Comment 5•14 years ago
|
||
Not that I am aware of.
Comment 6•7 years ago
|
||
not actionable. We are moving more and more to the async thread, so it should slowly improve along the way, but there' still work to do.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•