Balancing your Linux Server infrastructure  Design with TurboStorage to deliver the right mix of Session Speed and Number of Sessions per Data Server requires the CIO to profile the mix of customer experience and application workloads read/write IOPs traffic. 

A good place to start is to study the application performance monitoring tool reporting provided by vendors like Cisco(AppDynamics), New Relic and Dynatrace. CIOs can use the information these tools produce to identify a workload’s time of day/week pattern and to also identify the exact payload size distribution and frequency  as well as balance of reads and writes per each workload profile. 

This information will help the CIO more optimally group ‘shared block size’ workloads making use of shared Flash storage drive arrays (Direct attached or in SAN) so as to configure TurboStorage LVM2 volume to correctly create and share like formatted block volumes with each workload group type, where the direct attach drives of each Linux server or the Linux  server connected SAN Appliance’s drives are sized appropriately to balance overall speed and durability required for all the workload groups created. 

The network bandwidth for each different type of block size and workload group pairing can also be  TurboStorage configured, where direct attached storage bandwidth on PCIE buses or storage area network bandwidth is both physically sized per slot or throttled per VXLAN or MPLS path on 40/56 or 100/200 Gigabit Ethernet to optimally handle the like block sized volume grouped peak loads of all  the workload types ‘in aggregate’  by using the TurboStorage Browser UI or cli to assign volume groups  storage tier IOPs speed group during the initial setup and  physical and logical configuration of the flash storage array, be it direct or SAN attached.