gitlab-com-seaweedfs/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2024-01-19 02:48:24 +00:00
Code Issues Projects Releases Wiki Activity

help content textual changes

Browse source
This commit is contained in:
Chris Lu 2014-03-13 12:11:26 -07:00
parent 7a8bc2e19e
commit 7621b9b8a9
1 changed files with 9 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
go/weed/benchmark.go
View file

@ -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
`,
}