From 160b798aad17c48e2bf93811dd06de168244a4e1 Mon Sep 17 00:00:00 2001
From: Rahul C S <rahulcs@redhat.com>
Date: Fri, 17 Feb 2012 17:44:37 +0530
Subject: Scalability using iozone

Change-Id: I111eb271116ce36dafd121fa7cee176539623eea
Signed-off-by: Rahul C S <rahulcs@redhat.com>
---
 scalability/README     | 40 ++++++++++++++++++++++++++++++++++++++++
 scalability/iconf      |  5 +++++
 scalability/run_iozone | 11 +++++++++++
 3 files changed, 56 insertions(+)
 create mode 100644 scalability/README
 create mode 100644 scalability/iconf
 create mode 100755 scalability/run_iozone

diff --git a/scalability/README b/scalability/README
new file mode 100644
index 0000000..2828682
--- /dev/null
+++ b/scalability/README
@@ -0,0 +1,40 @@
+Clustered mode iozone setup:
+----------------------------
+Before continuing reading, please make sure the iozone version is greater
+than 3.394 to run iozone in clustered mode.
+
+Iozone needs either passwordless rsh or passwordless ssh to be setup to run in
+clustered mode.
+By default, iozone uses rsh. To force iozone to use ssh, the shell variable RSH
+needs to be set to 'ssh'. The command line listed earlier uses this feature.
+
+Contents of the iconf file used [ iozone cluster mode configuration file]:
+fusion1 /mnt/fioperf /usr/bin/iozone
+fusion1 /mnt/fioperf /usr/bin/iozone
+fusion2 /mnt/fioperf /usr/bin/iozone
+fusion2 /mnt/fioperf /usr/bin/iozone
+fusion3 /mnt/fioperf /usr/bin/iozone
+fusion3 /mnt/fioperf /usr/bin/iozone
+fusion4 /mnt/fioperf /usr/bin/iozone
+fusion4 /mnt/fioperf /usr/bin/iozone
+fusion5 /mnt/fioperf /usr/bin/iozone
+fusion5 /mnt/fioperf /usr/bin/iozone
+
+[Note that each entry is repeated twice so that two child processes
+could be run on each system.]
+
+Pitfalls:
+
+1.When the config file uses IP addresses instead of hostnames,
+iozone fails to proceed. For a successful iozone run in clustered mode,
+one needs to populate the config file with hostnames.
+For name resolution, one could use /etc/hosts.
+
+2.Even after successfully configuring passwordless rsh/ssh,
+if you are unable to run iozone, make sure you flush firewall rules
+
+To look at the configured firewall rules, one could use:
+# iptables -L
+
+To flush the rules, once could use:
+# iptables -F
\ No newline at end of file
diff --git a/scalability/iconf b/scalability/iconf
new file mode 100644
index 0000000..6d4a66c
--- /dev/null
+++ b/scalability/iconf
@@ -0,0 +1,5 @@
+#Example config file
+Engg.client1  /data/perfmount /data/iozone
+Engg.client14 /data/perfmount /data/iozone
+Engg.client15 /data/perfmount /data/iozone
+Engg.client16 /data/perfmount /data/iozone
\ No newline at end of file
diff --git a/scalability/run_iozone b/scalability/run_iozone
new file mode 100755
index 0000000..5d0457c
--- /dev/null
+++ b/scalability/run_iozone
@@ -0,0 +1,11 @@
+#!/bin/bash
+
+for size in 500m 1g 10g
+do
+    for bs in 16k 32k 64k 128k 256k 512k
+    do
+        echo "Filesize - $size, blksize - $bs"
+        RSH="ssh" iozone -t 4 -i 0 -i 1 -r $bs -s $size  -+m iconf -b iozone.$bs-$size.xls
+        sleep 10
+    done
+done
-- 
cgit