[tahoe-lafs-trac-stream] [tahoe-lafs] #1530: automated comparative 'k' performance tests and graphs

[tahoe-lafs]

#1530: automated comparative 'k' performance tests and graphs
--------------------------------+---------------------------
 Reporter:  warner              |          Owner:  warner
     Type:  task                |         Status:  new
 Priority:  major               |      Milestone:  undecided
Component:  dev-infrastructure  |        Version:  1.9.0a1
 Keywords:                      |  Launchpad Bug:
--------------------------------+---------------------------
 Here's my plan for some automated performance tests I intend to build over
 the next few months:

 * use the four servers on loan from Atlas Networks, one as a client, three
 as storage servers
 * use the attached attachment:upload-kN.py to upload a bunch of files with
 various sizes and encoding parameters (actually just varying 'k' and
 leaving N/k constant, since I don't think N affects performance much and
 would increase the runtime drastically).
 * write a script which fetches the directory contents once to get all the
 filecaps, then randomly downloads files from it, keeping track of how long
 each one takes (also recording other download-result timing data)
 * push that data to a CouchDB server for long-term storage (probably on
 iriscouch.com because it's free for small datasets, but it's easy to move
 a CouchDB to a different server later)
 * write some static HTML, served by that same CouchDB server, that uses
 [http://mbostock.github.com/d3/ d3.js] to construct graphs. The script in
 the HTML will turn around and fetch the relevant data from the DB with
 XHR.
 * make a scatterplot of time vs k, then a candlestick chart

 Later, I hope to use the same approach to store+display performance data
 across revisions, like the speedtest and memtest data we're getting from
 the buildbot.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1530>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage