Labour Updated

Iโ€™ve had more time to work on Labour (originally posted here, inspired by this and that), the WSGI Server Durability Benchmark. Iโ€™m relatively happy with progress so far, and will probably try to โ€˜marketโ€™ Labour a bit shortly. Two things that are still sorely missing from Labour (and are blocking me from posting some news of it to mailing lists et al) are better reporting facilities (read: flashy graphs) and mod_wsgi support.

That said, Labour can already benchmark nine WSGI Servers with a single commandline just seconds after you pull it off the sourcecode repository, and thatโ€™s something (do note that youโ€™d have to have the servers installed, Labour can benchmark all installed servers but wonโ€™t install them for you). The output is still not pretty, but you can unfold the item below to see sample results from an invocation of Labour. Do note that being a library, this is just one test configuration out of several. So while itโ€™s possible to see numbers-divided-by-second-real-quick for all the benchmark junkies out there, if you want to do anything meaningful, you better read the README file (awwโ€ฆ).
[sourcecode wraplines=โ€falseโ€ collapse=โ€trueโ€ gutter=โ€falseโ€]
4 test(s) against 9 server(s) finished.

Report of request failure percent and requests/sec:
| Server | Plain | Heavy Sleep | Light Sleep | SIGSEGV |
| Cogen | f%: 0.00; RPS: 168.85 | f%: 0.00; RPS: 10.00 | f%: 0.00; RPS: 83.98 | Failed |
| CherryPy | f%: 0.00; RPS: 476.51 | f%: 0.00; RPS: 30.78 | f%: 0.00; RPS: 269.99 | Failed |
| Eventlet | f%: 0.00; RPS: 672.88 | f%: 0.00; RPS: 22.98 | f%: 0.00; RPS: 250.41 | Failed |
| Tornado | f%: 0.00; RPS: 995.38 | f%: 0.00; RPS: 43.49 | f%: 0.00; RPS: 501.09 | Failed |
| Twisted | f%: 0.00; RPS: 761.19 | f%: 0.00; RPS: 77.99 | f%: 0.00; RPS: 544.19 | Failed |
| WSGIRef | f%: 0.00; RPS: 1427.46 | f%: 0.00; RPS: 61.07 | f%: 0.00; RPS: 536.52 | Failed |
| FAPWS3 | f%: 0.21; RPS: 2337.54 | f%: 0.00; RPS: 66.70 | f%: 0.00; RPS: 886.85 | Failed |
| Gevent | f%: 0.19; RPS: 2038.89 | f%: 0.00; RPS: 65.99 | f%: 0.00; RPS: 711.75 | Failed |
| Paster | f%: 0.17; RPS: 1866.36 | f%: 0.00; RPS: 152.45 | f%: 0.00; RPS: 1306.86 | Failed |

We see that Labour benchmarked nine servers with four different tests. Each test starts the server and hits it with a certain number of HTTP Requests. The requests cause the Labour WSGI Application (contained in the server) to do all sorts of trouble. For example, the Plain test in the table above is comprised of 99% requests that will return normally (200 OK and a body) and 1% of requests that will return 404 NOT FOUND. The SIGSEGV test, on the other hand, is made of 50% OK requests and 50% requests that cause a SIGSEGV signal to be sent to whichever process running out application. The two sleeping tests cause the application to sleep(), eating up server workers, the heavy test more often and for longer times than the lighter variant.

Each cell in the result table contains two numbers โ€“ the percentage of โ€˜failedโ€™ responses accumulated in the test, and the number of responses per second. In a Labout test, a โ€œfailedโ€ response is an HTTP response which doesnโ€™t match whatโ€™s expected from the Behaviour specified in the HTTP request that triggered it. For example, if we asked the server to respond with 404 NOT FOUND and the server responded 200 OK, thatโ€™s considered a failure. Some Behaviours allow quite a broad range of responses (I donโ€™t expect anything from a SIGSEGV Behaviour, even a socket error would be counted as OK), as they are issued to measure their effect on other requests (maybe some WSGI Servers will insulate other requests from a SIGSEGVโ€˜s). More than 10% of failed responses in a test will consider the whole test as failed.

Do note that the data in the table above should not be used to infer anything about the servers listed. First, it was created using only 1,000 requests per test (hey, Iโ€™m on vacation and all I got is a crummy lilโ€™ Netbook). Second, so far Labour does nothing to try and tune the various servers with similar parameters. So, for example, maybe some of these servers have multiprocessing support which I didnโ€™t enable, while others forked 16 kids. Third and last, I didnโ€™t think much about the tests Iโ€™ve created so far, and am mostly focused with developing Labour itself rather than producing quality comparisons (yet).

Thatโ€™s it, for now. Youโ€™re welcome to try Labour, and by all means Iโ€™d be happy to hear comments about this benchmarking methodology, the kind of test profiles youโ€™d like to see constructed (try looking into labour.tester.factories and labour.behaviours, the syntax of test-construction is self-teaching), etc. I wonโ€™t wreak havoc on the sources on purpose, but no API is stable until declared otherwise (โ€ฆ).


One response to โ€œLabour Updatedโ€

  1. [โ€ฆ] Labour Updated ยซ NIL: .to write(1) ~ help:about says: April 15, 2010 at 11:14 pm [โ€ฆ]