Enter the number of SSDs in the array. Include parity drives, but not hot spares in this count.

Enter the number of available SSD bays. The "best fit" function will populate SSDs, up to this number of SSDs..

Enter the RAID level for maxRAID to use. maxRAID does not recommend RAID-1/10 as these mirroring options do not provide benefits beyond RAID-5/6.

Enter the size of the SSDs. The list includes most datacenter 1 DWPD SSDs. maxRAID does not recommend 3 DWPD SSDs as their additional over-provisioning does not provide any benefit to maxRAID. Consumer drives are supported, but not included in this estimator.

Enter the target AWPD (Array Writes per Day) for the array you are creating. This is the number of times you can completely over-write your data, per day, every day, for five years.

Most active hosting applications need at least 1 AWPD.

Enter the general maximum fill level that you use operationally. In general, most installations don't fill their storage completely. This defaults to 90%. Above 90%, many file systems slow anyway.

Enter the compressibility of your data blocks.

General hosting of file systems, containers, and virtual instances usually see between 20% and 30% compressibility.

Many databases are highly compressible, both because they tend to store ascii text, and they tend to have signifigant padding inside of their blocks. 50% minimum compressibility is common for databases like Postgres and MariaDB.