Here is the steps on how to run benchmark if you really need some numbers.

I start weed servers in one console for simplicity. Better run servers on different consoles.

By default, the benchmark command would start writing 1 million files, each having 1KB size, uncompressed.For each file, one request is sent to assign a file key, and a second request is sent to post the file to the volume server.The written file keys are stored in a temp file.

Then the benchmark command would read the list of file keys, randomly read 1 million files.For each volume, the volume id is cached, so there is several request to lookup the volume id,and all the rest requests are to get the file content.

The default "weed benchmark" uses 1 million 1KB file. This is to stress the number of files per second.Increasing the file size to 100KB or more can show much larger number of IO throughput in KB/second.

My Own Results on Mac Book with Solid State Disk, CPU: 1 Intel Core i7 at 2.2GHz.

How can the replication 001 writes faster than no replication?I could not tell. Very likely, the computer was in turbo mode.I can not reproduce it consistently either. Posted the number here just to illustrate that number lies.Don't quote on the exact number, just get an idea of the performance would be good enough.