Our current performance suite is @ https://github.com/pouchdb/pouchdb/tree/master/tests/performance Its at a fairly abstract level above idb, and right now its not particularly clean, but it should be easy enough to get running, instructions @ https://github.com/pouchdb/pouchdb/blob/master/CONTRIBUTING.md We have only just started on and the tests may not be great representations, but early signs are chrome and firefox are quite comparable with chrome being noticeably faster for keyrange queries, and safari being orders of magnitude faster On 18 April 2014 07:48, Kyle Huey <me@kylehuey.com> wrote: > On Thu, Apr 17, 2014 at 5:16 PM, Ben Kelly <bkelly@mozilla.com> wrote: > > On 4/17/2014 5:41 PM, Kyle Huey wrote: > >> > >> On Thu, Apr 17, 2014 at 2:10 PM, Dale Harvey <dale@arandomurl.com> > wrote: > >>> > >>> No features that slow it down, as with Tim I also implemented the same > >>> thing > >>> in node.js and see much better perfomance against straight leveldb, > with > >>> websql still being ~5x faster than idb > >> > >> > >> Do you have benchmarks for this? When we've profiled IndexedDB > >> performance for Gaia apps in the past the issue is invariably that the > >> main thread event loop is busy and IndexedDB's responses have to go to > >> the end of a long line. > > > > > > I would hazard a guess that some of SQL's more feature rich constructs > allow > > you to do more in a single API call. This could mean you need to hit the > > event loop less often to accomplish the same amount of work in many > cases. > > > > Just a theory. > > > > Ben > > Yes, that's entirely possible. Which is why I would like to see a > testcase ;-) > > - Kyle >
Received on Friday, 18 April 2014 11:09:11 UTC