Open
Bug 998324
Opened 11 years ago
Updated 7 months ago
Profile the pouchdb performance test suite
Categories
(Core :: Storage: IndexedDB, task, P5)
Core
Storage: IndexedDB
Tracking
()
NEW
People
(Reporter: khuey, Unassigned)
Details
(Keywords: perf, Whiteboard: dom-lws-bugdash-triage)
PouchDB has a performance test suite: https://github.com/pouchdb/pouchdb/tree/master/tests/performance. Instructions at: https://github.com/pouchdb/pouchdb/blob/master/CONTRIBUTING.md
Dale says:
> 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
We should figure out what's going on and whether the issues are implementation problems or API design problems.
Comment 1•11 years ago
|
||
Cheers, these performance tests have just started and will be getting a lot of work coming up, but I want to make sure they are useful for being able to introspect whats going on both in and below PouchDB. If anyone needs help getting them up and running can needinfo me or catch me on IRC
We have written a database with the same semantics on top of indexeddb, websql, leveldb and interestingly enough there is a version using an leveldb abstraction on top of indexeddb as well, so it should provide pretty interesting comparisons between them.
Comment 2•11 years ago
|
||
And first thing ill do is get these tests online somewhere so yall dont need to install or muck around with pouch, should have it done for monday.
I will try to write a blog post about the internal architecture so you have a better idea of what its doing
Comment 3•11 years ago
|
||
I went ahead and hosted the performance tests here: http://pouchtest.com/tests/performance/test.html
It should auto-update to PouchDB master every day at midnight EST, and the command-line options described here still apply: https://github.com/pouchdb/pouchdb/blob/master/CONTRIBUTING.md#performance-tests-in-the-browser
The "temp-views" test tends to hang pretty badly (in all browsers), but you can skip it by appending ?grep=persisted-views .
Updated•7 years ago
|
Priority: -- → P5
Updated•2 years ago
|
Severity: normal → S3
Updated•7 months ago
|
Type: defect → task
Whiteboard: dom-lws-bugdash-triage
You need to log in
before you can comment on or make changes to this bug.
Description
•