Using the temp-views
performance test in the standard PouchDB benchmarks (see TESTING.md), which builds up a secondary index and then queries it. So it tests the whole process of building the index as well as doing a paginated read a couple times (although the bulk of the time spent is in building).
2013 MacBook Air running OS X Yosemite 10.10.1. IE 11 is running on Windows 7 within VirtualBox. Node tests were run using Node 0.10.28.
Browser/environment | Adapter | Before (ms) | After (ms) | Improvement |
---|---|---|---|---|
Chrome 39 | IndexedDB | 16608 | 10343 | 37.7228% |
Firefox 36 | IndexedDB | 39344 | 19510 | 50.4118% |
Safari 8 | WebSQL | 9228 | 5594 | 39.3801% |
IE 11 | IndexedDB | 44810 | 19232 | 57.081% |
Node 0.10 | LevelDB | 6178 | 3674 | 40.5309% |
The next version of PouchDB should be even faster for map/reduce builds, due to pouchdb/mapreduce#241 and pouchdb/mapreduce#243. Preliminary results indicate an additional 13% (Chrome), 27% (Node) and 52% (Firefox) improvement.