Hello Jorge,
first I did not want to answer because there is so much information that would still be important to make an appropriate statement.
But then a certain interest arose and I am curious what others write about it.
Information that would be important among others:
* How is the storage system equipped and installed?
* What media is used and how many, what raid size? SCMs, SSDs, FCMs; 9+2P+S...
* Expansions?
* How much memory? 64, 256, 512GB - Write Cache is always 12GB
* Which firmware?
* If different media, is EasyTier used.....
* Which pools? Standard or DataReduction?
* How full is the storage system?
* How many physical connections from storage to switch and from switch to server? Max 1.75 gigabytes per second per physical connection.
* How many servers are connected to the storage
* How many volumes are presented to the server?
* What is the multipath configuration? multipath -ll
* How is the LVM configured?
* What does the zoning look like and how is the switch configured?
* Switch information like congestions or port errors
* What does the workload look like? What you are showing us is a single thread throughput test and probably does not reflect what Informix is doing on the storage system. Better use fio or DB specific tool
* Is it monitored? Maybe Spectrum Control
, Storage Insight Pro, Stor2rrd? Is there any data from the Informix workload like IO Size, Read/Write Ratio, Write Cache problems?
There is a sizer from IBM that always assumes an optimal environment and you can fill it with many parameters.
Simply said 100% write IO without caching, and streaming effects at 12 FCMs and 16Gb/s, I think 3GB/s should be the best you can expect.
According to the data sheet, IBM specifies 21GB/s in a fully expanded cluster, which is a quarter for a single system. Therefore 5.25GB/s
https://www.ibm.com/downloads/cas/VXDNQQELBest practices are relatively simple:
* Standard pools
* As many media in storage as possible (12)
* Many volumes to the server (number of cores of the storage system) >= 16
* Max 80% fill level for flash storage
* Automatic distribution of volumes to nodes
* Min 4 physical paths to SAN and min 2 paths from server to SAN
* Fixed speeds in SAN - no autonegotiation
* For LVM - check multipath and connect volumes from storage via LVM, pay attention to striping, single stripe size and round robin
* Same applies if database internal functions can be used
* For experienced users adjust the queue depth (max queue depth / volumes) (consider server and storage)
It was fun to write this together and as mentioned above, I'm curious what others contribute.
Greetings Patrik
------------------------------
Patrik Groß
------------------------------