Open Bug 1016984 Opened 10 years ago Updated 2 years ago

Too much I/O for simple IndexedDB transactions

Categories

(Core :: Storage: IndexedDB, defect, P5)

28 Branch
x86
Windows XP
defect

Tracking

()

UNCONFIRMED

People

(Reporter: antigonos, Unassigned)

Details

Attachments

(1 file)

Attached file Simple test file
Hi, the problem is that even for simple IndexedDB transactions there seems to be a lot of HDD I/O operations.

Eg. try the test file attached: pressing the Put button (which puts only one value into the object store) causes a lot of read/write operations.
Procmon shows that hundreds of KBs are read and written even for a single press.
If you press the Put many times, Procexp shows a throughput of >1MB/s.
The telemetry page shows a lot of slow SQL queries with the text: 	Untracked SQL for 301792106ttes.sqlite (average 170ms).

Trying Chrome, only a few bytes are read/written there for each press, and the throughput is also minimal.

Also tried the To-Do-List sample from the web, with the same result.

Maybe the problem is, that the SQLite file is always closed and reopened for each new transactions? Wondering, if it could be opened at the first use, and closed only when the DB objects goes out of scope (or similar)?
One small more info (just found this pref):
With toolkit.telemetry.debugSlowSql enabled the telemetry shows:
168(ms) COMMIT TRANSACTION /* 301792106ttes.sqlite */
Component: General → DOM: IndexedDB
Product: Firefox → Core
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: