Check in new benchmark results

[bluesky.git] / microbench / run-spec.sh

diff --git a/microbench/run-spec.sh b/microbench/run-spec.sh
index 93cb191..bd2ab63 100755 (executable)
--- a/microbench/run-spec.sh
+++ b/microbench/run-spec.sh
@@ -7,8 +7,8 @@ run_spec() {
     BLUESKY_RUN_NAME=$(date +%Y%m%d)-$1
     SPEC_CONF=$2
 
-    $HOME/bin/s3-cleanup.py mvrable-bluesky
-    $HOME/bin/s3-cleanup.py mvrable-bluesky-west
+    #$HOME/bin/s3-cleanup.py mvrable-bluesky
+    #$HOME/bin/s3-cleanup.py mvrable-bluesky-west
     run_cmd $PROXY cleanup-proxy
     run_cmd $PROXY run-proxy >$BLUESKY_RUN_NAME.proxy 2>&1 &
     proxy_pid=$!
@@ -21,6 +21,16 @@ run_spec() {
     wait $proxy_pid
 }
 
-BLUESKY_TARGET=s3:mvrable-bluesky-west
-BLUESKY_OPT_FULL_SEGMENTS=1
-run_spec s3-west-fullseg sfs_bluesky
+# Test of using full segment fetches instead of range requests
+#BLUESKY_TARGET=s3:mvrable-bluesky-west
+#BLUESKY_OPT_FULL_SEGMENTS=1
+#run_spec s3-west-fullseg sfs_bluesky
+
+# Run a simulation of not using a log-structured system at all
+#BLUESKY_TARGET=s3:mvrable-bluesky-west
+#BLUESKY_EXTRA_OPTS="BLUESKY_OPT_FULL_SEGMENTS=1 BLUESKY_OPT_NO_AGGREGATION=1"
+#run_spec s3-west-noseg sfs_bluesky
+
+# Standard test with Azure instead of Amazon S3 for storage
+BLUESKY_TARGET=azure
+run_spec azure sfs_bluesky