W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: Starting work on Indexed DB v2 spec - feedback wanted

From: Kyle Huey <me@kylehuey.com>
Date: Thu, 17 Apr 2014 23:48:22 -0700
Message-ID: <CAP045AqOuMwibd7RLn1Pj2dGB2ZV_VQ=zbXNau8UTzsXeeMyrQ@mail.gmail.com>
To: Ben Kelly <bkelly@mozilla.com>
Cc: Dale Harvey <dale@arandomurl.com>, Tim Caswell <tim@creationix.com>, Joshua Bell <jsbell@google.com>, "public-webapps@w3.org" <public-webapps@w3.org>, Ali Alabbas <alia@microsoft.com>
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 06:48:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:24 UTC