StorNext Storage Manager uses a MySQL database for storing managed StorNext file system information.
StorNext Storage Manager can run on Linux MDCs and requires a Storage Manager license. Tuning the MySQL database can improve the performance of Storage Manager and other parts StorNext.
The InnoDB buffer pool is used to cache the data and indexes of MySQL InnoDB database tables.
Increasing the size of the InnoDB buffer pool will allow MySQL to keep more of the working database set memory resident, thereby reducing the amount of disk access required to read datasets from the file system. The InnoDB buffer pool size is determined by the parameter
innodb_buffer_pool_size in the
Increasing this value can improve the performance of Storage Manager operations that require large queries. However, setting this value too high can inefficiently remove memory from the free pool that could otherwise be used by the StorNext file system or other applications, and could lead to memory starvation issues on the system. The default value value of
innodb_buffer_pool_size is 8 G. The following are the default values for the StorNext Appliances:
Quantum recommends setting this value to at least 8 GB (except on the M330 where 5 GB is recommended). This value may need to be decreased if memory starvation is observed or if the Linux Out-of-Memory (OOM) Killer is triggered.
To change this value, modify the
/usr/adic/mysql/my.cnf file and change the
innodb_buffer_pool_size setting in the
innodb_buffer_pool_size = 8G
Both Storage Manager and MySQL will need to be restarted for the change to
/usr/adic/mysql/my.cnf to take effect by executing the following commands:
# adic_control stop
# adic_control start