Update loadtests to speak onepw protocol.

[rfk]

Fortunately, this vastly simplifies the code!

[rfk]

@dannycoates r?

[rfk]

$ make bench
./loadsrunner.sh --users=20 --duration=1800 --agents=5 --include-file=./loadtests.py --python-dep=hawkauthlib loadtests.LoadTest.test_auth_server
[========================================================================] 100%
Duration: 1809.12 seconds
Hits: 1037195
Started: 2014-01-21 05:24:15.030781
Approximate Average RPS: 573
Average request time: 0.17s
Opened web sockets: 0
Bytes received via web sockets : 0

Success: 17700
Errors: 0
Failures: 6

6 occurrences of: 
    <type 'exceptions.AssertionError'>: 500 != 400  File "/usr/lib64/python2.6/unittest.py", line 278, in run    

That's not bad.

[rfk]

The 6 errors are all from calls to /account/create and all occurred pretty early in the loadtest run, when it would have been creating users at a higher rate in order to ramp up the pool of existing users. Possibly scrypt worker overload, possibly database overload - we need way to ship the full "tracebacks" for these to the logbox for analysis.

[rfk]

Yep, a second 30-minute test runs clean, so the error must have been due to extra account-creation load on an empty database.

[dannycoates]

Awesome! r+

I'm very interested in those errors too.

[jbonacci]

👍