aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Lu <chris.lu@gmail.com>2014-03-13 12:11:26 -0700
committerChris Lu <chris.lu@gmail.com>2014-03-13 12:11:26 -0700
commit7621b9b8a9848e03f547be44007c8921a0d54406 (patch)
tree6de6d160dd2f459e9538bd150b9b0af6aebc35b5
parent7a8bc2e19ea7d79a3c80e954dadf8847a0851773 (diff)
downloadseaweedfs-7621b9b8a9848e03f547be44007c8921a0d54406.tar.xz
seaweedfs-7621b9b8a9848e03f547be44007c8921a0d54406.zip
help content textual changes
-rw-r--r--go/weed/benchmark.go15
1 files changed, 9 insertions, 6 deletions
diff --git a/go/weed/benchmark.go b/go/weed/benchmark.go
index ad99f42d8..733435c73 100644
--- a/go/weed/benchmark.go
+++ b/go/weed/benchmark.go
@@ -62,18 +62,21 @@ var cmdBenchmark = &Command{
2) read the files out
The file content is mostly zero, but no compression is done.
-
- By default, write 1 million files of 1KB each with 7 concurrent threads,
- and randomly read them out with 7 concurrent threads.
-
+
You can choose to only benchmark read or write.
During write, the list of uploaded file ids is stored in "-list" specified file.
You can also use your own list of file ids to run read test.
Write speed and read speed will be collected.
The numbers are used to get a sense of the system.
- But usually your network or the hard drive is
- the real bottleneck.
+ Usually your network or the hard drive is the real bottleneck.
+
+ Another thing to watch is whether the volumes are evenly distributed
+ to each volume server. Because the 7 more benchmark volumes are randomly distributed
+ to servers with free slots, it's highly possible some servers have uneven amount of
+ benchmark volumes. To remedy this, you can use this to grow the benchmark volumes
+ before starting the benchmark command:
+ http://localhost:9333/vol/grow?collection=benchmark&count=5
`,
}