Details
-
Question/Request
-
Resolution: Won't Fix
-
Minor
-
None
-
None
-
None
-
16150
Description
After LAD this year the suggestion about our performance issues with single client single steam data was to try out the 2.6 Client. We are aiming for 900MB/s single stream single client performance.
Could I ask if we were to use this in production would this be covered by our support contract?
I am seeing on average a 66% increase in performance from the 2.5 to the 2.6 client. This is giving us approximately 650MiB/s from a single client running IOR.
Run as below
/dls_sw/apps/openmpi/1.4.3/64/bin/mpirun -mca btl self,tcp,sm -np 1 /home/bnh65367/code/ior/src/ior -o /mnt/lustre03/testdir/dave/ior_dat -w -r -k -t4m -S -b 10G -i 1 -e -a POSIX
This agrees with dd used as a crude way to measure single stream performance, and real world testing. Though iozone achieves much higher figures being approximately 900MB/s the relationship is still an proximate 60% improvement.
I believe the IOR figures to be more like what we would see with one of our detectors and I do not fully understand yet why iozone achieves so much better results.
iozone.x86_64 -i 0 -r 4M -s 10G -t 1
But I would like to know if you feel we can get IOR to run at 900MB/s. The testing I have done so far with real world tests and benchmarking is consistently showing the 600MB/s performance. Andreas was of the opinion I should be able to achieve 900MB/s with the 2.6 client.
Is there any tuning that you can think of that might benefit us. We can already see the file striped across all OST's