Sounds like a great idea to me. That way we can see how others are configuring their systems and what works well.
As far as benchmarking for Ceph, you want to use the RADOS testing tool. This is included in ceph-common and thus already installed on Proxmox.
I recommend first creating a test pool on ceph with appropriate PG size. (See the
Customize Ceph section I wrote for appropriate PG sizing)
sudo ceph osd pool create 2xtest 4096
**See attached excel spreadsheet for the block sizes I have been testing with. Make sure to update the disks in the top left to reflect how many disks are in your cluster. After the test enter your average throughput in the "Throughput MBps" column and it will generate your IOPS.
**You must do a write of a particular block size before you can do a read (seq), also if you wait too long you may need to do another write before you can do a read.
This is the format for the testing command:
rados -p test bench -b *blockSize* *secondsToRun* *seq/write* -t *numberOfThreads* -c ceph.conf -k ceph.client.admin.keyring --no-cleanup
"blockSize" is in bytes and you can use the sizes listed in my spreadsheet for a good spread between bandwidth and IO. "secondsToRun" I usually set to 30-60 seconds. "seq" is read and "write" is... write. The number of threads should match the number of cores on the box you are testing from (that gives best results from what I have seen). You must also copy your ceph.conf and keyring from ceph into the working directory of the server you are testing from. I test directly from a proxmox host because my VMs seem to be limited in throughput as I explained earlier.
Example tests:
rados -p test bench -b 4194304 60 write -t 32 -c ceph.conf -k ceph.client.admin.keyring --no-cleanup
rados -p test bench -b 4194304 60 seq -t 32 -c ceph.conf -k ceph.client.admin.keyring --no-cleanup
It might also be a good idea to purge your cache before doing the read for best accuracy, although it didn't make much of a difference in my case.
echo 3 > /proc/sys/vm/drop_caches
