3 ms·

At this point we are unlikely to switch to leveldb, work on that has stopped. During integration and testing for leveldb we made a lot of progress on sqlite opt

by joshmoz 14y ago

At this point we are unlikely to switch to leveldb, work on that has stopped. During integration and testing for leveldb we made a lot of progress on sqlite optimzation and the leveldb advantage diminished significantly, if not disappeared. (Notice that the bug you referenced hasn't had any real progress since it was filed in August 2011, and work has stopped on the parent bug for integrating leveldb.) I don't know much about the particular performance problem you're referencing, but I doubt it is as simple as sqlite not being fast enough.

MatthewPhillips 14y ago
I write an indexedDB library and have 25 unit tests that have multiple operations per test, let's say an average of only 2 per test. So about 50 operations, mostly just get or put. Chrome takes about 1 (when warm) to 1.5 (cold start) seconds to run all of the tests, Firefox takes 3.5 (warm) to 5 (cold). IE10 is phenomenally fast, less than a half a second even when cold. This is some combination of slowness from pulling js from the cache, raw js speed, and indexedDB speed. I assumed it was mostly the latter but I could be wrong.
- daleharvey 14y ago
  I was about to agree with you, for PouchDB I have a test suite of 460 tests which take around 20 - 30 seconds and are mostly indexedDB operations, I remember having to increase some timeouts to have tests pass in Firefox But I just ran the test suite again and after a few runs, there was little difference in timing, firefox even came faster a few times. And this is in latest stable, I cant test nightly yet due to some api changes, and I know there was a lot of work done on idb performance improvements last week. Pleasantly surprised
  - MatthewPhillips 14y ago
    Just out of curiosity, have you tested IE10 and if so what were your results?
    - daleharvey 14y ago
      I havent, but do plan on doing so soon
- khuey 14y ago
  Can you post your test suite in a bug on bugzilla.mozilla.org? We'd like to profile this.

by joshmoz 14y ago

MatthewPhillips 14y ago

I write an indexedDB library and have 25 unit tests that have multiple operations per test, let's say an average of only 2 per test. So about 50 operations, mostly just get or put. Chrome takes about 1 (when warm) to 1.5 (cold start) seconds to run all of the tests, Firefox takes 3.5 (warm) to 5 (cold). IE10 is phenomenally fast, less than a half a second even when cold. This is some combination of slowness from pulling js from the cache, raw js speed, and indexedDB speed. I assumed it was mostly the latter but I could be wrong.

daleharvey 14y ago
I was about to agree with you, for PouchDB I have a test suite of 460 tests which take around 20 - 30 seconds and are mostly indexedDB operations, I remember having to increase some timeouts to have tests pass in Firefox But I just ran the test suite again and after a few runs, there was little difference in timing, firefox even came faster a few times. And this is in latest stable, I cant test nightly yet due to some api changes, and I know there was a lot of work done on idb performance improvements last week. Pleasantly surprised
- MatthewPhillips 14y ago
  Just out of curiosity, have you tested IE10 and if so what were your results?
  - daleharvey 14y ago
    I havent, but do plan on doing so soon
khuey 14y ago
Can you post your test suite in a bug on bugzilla.mozilla.org? We'd like to profile this.