The only test written is a connect-disconnect test and the harness makes runs roughly:
each benchmark to run 120 seconds for each driver: (PostgreSQL, MySQL) for each benchmark: (dbconnectdisconnect) run the setup for each concurrency: (1,25,100,250,500) run that benchmark summarize that benchmark run the teardown
When it starts hammering 500 sessions I think either the 2.4.20 Linux scheduler or Python threading starts to choke. I don't have enough hardware to run the benchmarker against a different machine where I would expect some different numbers. Now I'm getting to a point where it's time to write some more interesting tests. The framework also tracks successful iterations which I just tested by setting the max-connections for MySQL down fairly low. I'm going to stop hacking on it tonight and go back and do some reading.