Open
Bug 1903603
Opened 9 months ago
Updated 2 months ago
Remove IndexedDB Transaction scheduling queue
Categories
(Core :: Storage: IndexedDB, enhancement, P3)
Core
Storage: IndexedDB
Tracking
()
NEW
People
(Reporter: jjalkanen, Assigned: jjalkanen)
References
Details
Attachments
(1 file)
Currently, when all the threads available for IndexedDB's ConnectionPool are busy, the transactions are placed in a scheduling queue from where the completion handlers of the running tasks pick them up for execution. After the thread management of the ConnectionPool was changed to rely on TaskQueues on nsThreadPool, this step could possibly be offloaded to the TaskQueue. Each TaskQueue is attached to a database, and serializes all the transactions concerned with a single database, without another queue.
|
Assignee | |
Comment 1•9 months ago
|
||
Each connection already queues up the transactions in a task queue.
|
||
Comment 2•2 months ago
|
||
The last comment in phab is very easy to address, can we land the patch in this cycle ?
Flags: needinfo?(jjalkanen)
You need to log in
before you can comment on or make changes to this bug.
Description
•