zfs_arc_max foi aparentemente reprovado. Consulte o link :
ZFS Memory Management Parameters
This section describes parameters related to ZFS memory management.
user_reserve_hint_pct
Description
Informs the system about how much memory is reserved for application use, and therefore limits how much memory can be used by the ZFS ARC cache as the cache increases over time.
By means of this parameter, administrators can maintain a large reserve of available free memory for future application demands. The user_reserve_hint_pct parameter is intended to be used in place of the zfs_arc_max parameter to restrict the growth of the ZFS ARC cache.
Note - Review Document 1663862.1, Memory Management Between ZFS and Applications in Oracle Solaris 11.2, in My Oracle Support (MOS) for guidance in tuning this parameter. Data Type
Unsigned Integer (64-bit)
Default
0
If a dedicated system is used to run a set of applications with a known memory footprint, set the parameter to the value of that footprint, such as the sum of the SGA of Oracle database.
To assign a value to the parameter, run the script that is provided in Document 1663862.1 in My Oracle Support (MOS). To make the tuning persistent across reboots, refer to script output for instructions about using –p option.
Range
0-99
Units
Percent
Dynamic
Yes
You can adjust the setting of this parameter dynamically on a running system.
When to Change
For upward adjustments, increase the value if the initial value is determined to be insufficient over time for application requirements, or if application demand increases on the system. Perform this adjustment only within a scheduled system maintenance window. After you have changed the value, reboot the system.
For downward adjustments, decrease the value if allowed by application requirements. Make sure to use decrease the value only by small amounts, no greater than 5% at a time.
Commitment Level
Unstable
...
zfs_arc_max
Description
Determines the maximum size of the ZFS Adaptive Replacement Cache (ARC). However, see
user_reserve_hint_pct.
Na minha opinião, este é um grande passo para trás. Um limite rígido é substituído por uma mera "dica". Pode haver muito, muito, muito boas razões para um limite hard .
(Eu estou querendo saber se realmente existe um limite rígido de ARC não documentado. A Sun / Oracle tem um histórico de fazer coisas como essa com o ZFS. "O ZFS é sempre consistente no disco! Você não precisa de fsck ou qualquer ferramentas de depuração. Não, você não sabe, nós dissemos que não. POR QUE, POR QUE VOCÊ NÃO ACREDITARIA NÓS?!?! Ah, humm, ahhh, sim, aqui está zdb . Nós temos usado internamente há anos, então é bem maduro ... ")