Crank up dbench, now that everything seems to be quite stable under load.

We now do 1, 10, 50, and 100 client runs each night.
Make sure the path back to the scripts directory is available in the
environment for scripts to get at if need be.

run.dbench

@@ -1,27 +1,8 @@
 #!/bin/sh
 # 
-# Does a dbench run (10 clients if $DBENCH_CLIENTS is not set),
-# then massages the output into CSV format.
+# Does a single-client dbench run
 # 
-DBENCH_CLIENTS=${DBENCH_CLIENTS:=10}
+DBENCH_CLIENTS=1
+export DBENCH_CLIENTS
 
-run_dbench()
-{
-	mkdir ./dbench || exit 1
-	cd dbench
-	dbench $DBENCH_CLIENTS
-	status=$?
-	cd ..
-	rm -fr ./dbench
-	[ $status -ne 0 ] && exit 1
-}
-
-# 
-# Sample dbench output:
-# "Throughput 40.6701 MB/sec (NB=50.8376 MB/sec  406.701 MBit/sec)"
-# 
-if [ $# -gt 0 ]; then
-	echo "clients,MB/sec"
-	exit 0
-fi
-run_dbench | awk 'END { printf "%u,%s\n", '$DBENCH_CLIENTS', $2 }'
+exec $here/common.dbench