Question

Can anyone point me to an article on, or preferably provide some experience of performance of IndexedDB (ideally in Chrome) – what is the fetch, insert and update performance like?

There seems to be reasonable amount of opinion that its pretty much unusable for data sets of more than a few thousand records but I’m not sure if this isnt just due to a lack of indexing – surely conceptually it cant be slower than web storage as both presumably use key-value storage internally?

Thanks

Answer 1

I recently did some performance comparisons between WebSQL and IndexedDB. Surprisingly, IndexedDB won (which I wasn’t expecting).

http://blog.oharagroup.net/post/16394604653/a-performance-comparison-websql-vs-indexeddb

---

Edit: the above URL is down, but available on archive.org: http://web.archive.org/web/20160418233232/http://blog.oharagroup.net/post/16394604653/a-performance-comparison-websql-vs-indexeddb

In summary:

WebSQL takes on average between ~750-850ms to complete the query and render the results; and IndexedDB takes on average ~300-350ms to render the exact same results.