Open
Bug 599980
Opened 11 years ago
Updated 3 years ago
favicon protocol handlers could use a cloned read-only connection
Categories
(Toolkit :: Places, defect, P3)
Toolkit
Places
Tracking
()
NEW
People
(Reporter: sdwilsh, Unassigned)
References
Details
(Keywords: perf)
We should stop having lock contention and let the annotation protocol use it's own read-only database connection. Also means less stuff happening on primary connection's background thread. Bonus: with WAL (bug 573492) it means writers and readers can happen at the same time. Parallelism FTW.
Updated•4 years ago
|
Priority: -- → P3
Updated•3 years ago
|
Summary: Annotation/favicon protocol handler should use a cloned read-only connection → favicon protocol handlers could use a cloned read-only connection
You need to log in
before you can comment on or make changes to this bug.
Description
•