Configuring the MySQL x64 server for working with Kaspersky Security Center Linux

If you use the MySQL server for Kaspersky Security Center, enable support of InnoDB and MEMORY storage and of UTF-8 and UCS-2 encodings.

Recommended settings for the my.cnf file

For more details about DBMS configuring, refer also to the account configuring procedure. For information about DBMS installation, refer to the DBMS installation procedure.

To configure the my.cnf file:

  1. Open the my.cnf file in a text editor.
  2. Add the following lines into the [mysqld] section of the my.ini file:

    sort_buffer_size=10M

    join_buffer_size=20M

    tmp_table_size=600M

    max_heap_table_size=600M

    key_buffer_size=200M

    innodb_buffer_pool_size=the real value must be no less than 80% of the expected KAV database size

    innodb_thread_concurrency=20

    innodb_flush_log_at_trx_commit=0 (in most cases, the server uses small transactions)

    innodb_lock_wait_timeout=300

    max_allowed_packet=32M

    max_connections=151

    max_prepared_stmt_count=12800

    table_open_cache=60000

    table_open_cache_instances=4

    table_definition_cache=60000

    Note that the memory specified in the innodb_buffer_pool_size value is allocated at server startup. If the database size is smaller than the specified buffer size, only the required memory is allocated. The actual size of allocated memory is approximately 10 percent greater than the specified buffer size. Refer to the MySQL documentation for details.

    It is recommended to use the parameter value innodb_flush_log_at_trx_commit = 0, because the values "1" or "2" negatively affect the operating speed of MySQL. Ensure that the innodb_file_per_table parameter is set to 1.

Page top