http://pouchdb.github.io/dashboard/ is currently using a sample of data from http://pouchdb.cloudant.com/performance_results, switch it to using live data

For the real or aspiring designers

Every time I think of a dashboard I think of the panic dashboard, black background with strong colours, would love for ours to look as good

https://www.google.co.uk/search?q=panic+dashboard&safe=off&client=firefox-nightly&hs=7aS&rls=org.mozilla:en-US:unofficial&channel=fflb&source=lnms&tbm=isch&sa=X&ei=npROU9vWD-qw7AbDnoHYDw&ved=0CAoQ_AUoAw&biw=1277&bih=861

Can be mocked up seperately or just experimented in code, just wanted to open an issue for it

Since there's lots of browsers being represented it'd be good to be able to toggle only those you're interested in.
There has been suggestions about specific pouchdb builds targeting subsets so it'd be great to be able to show the performance data to users for targeted builds.

right now they are hardcoded in https://github.com/pouchdb/dashboard/blob/gh-pages/dashboard.js#L64

So theres a few ways we need to change the data reported

1. We need to change the _id to be date so _all_docs can be queried by date, right now we can do that in memory, but its slow and wont scale, eventually we will need views, but right now just ordering by date should get us enough
2. need to specify the browser that the tests were run in
3. Need to add the commit hash to drill down

This should be a fairly simple PR to https://github.com/pouchdb/pouchdb/blob/master/bin/test-browser.js

allow the viewer to choose a range of dates to view, so not all data is clustered on the graph.

Looking at some other perf graphs it's really nice to be able to drill into the seperate nodes on the graph and get exactly which commit and data it represents.
Some examples:
http://bench.topcoat.io/
http://arewefastyet.com/

PouchDB covers a lot of bases but most web developers I've talked to don't know much about the databases that ship with browsers or their market share.

If we could visualise this for a user it'll give them a clear understanding of who they're supporting, my proposal is something similar to http://www.iwanttouse.com/ but specific to pouchdb.

This could also potentially tie into the performance data so we could have performance to browser share ratio, you want to know what the performance will be like for the majority of your users without having to research indexeddb etc.