Below is a guide on how to install a database for the latest version of Rogō (6.5.0 onwards).
If you have a MySQL expert or database administrator you are recommended to contact them for advice first. |
MySQL is currently the only supported database. However, in theory MariaDB should also be compatible. Please let us know if you do successfully run Rogō on a non MySQL database.
Minimum required version of MySQL 5.1 we recommend you use the latest MySQL 5.6.X version available on your operating system.
Currently MySQL 5.7 is not supported. |
The following non default settings may need to be applied to your my.cnf in order to run Rogō .
The basic default installation config should work in small settings. The my-large.cnf should be suitable for most configurations. It is best to increase the key_buffer (the settings do depend upon your exact conditions) then make sure that the query cache is increased. You would be recommended to have a read of the MySQL documentation. |
mysqld settings:
ft_min_word_len | 3 |
key_buffer = 384M | 384M |
max_allowed_packet | 256K |
thread_cache_size | 8 |
max_connections | 500 |
query-cache-type | 1 |
query_cache_limit | 5M |
query_cache_size | 500M |
max_heap_table_size | 536870912 |
tmp_table_size | 536870912 |
table_open_cache | 2500 |
log-bin | mysql-bin |
binlog_format | mixed |
innodb settings:
innodb_buffer_pool_size = 2000M | 2000M |
innodb_additional_mem_pool_size | 200M |
innodb_log_buffer_size | 5M |
innodb_flush_log_at_trx_commit | 1 |
innodb_lock_wait_timeout | 50 |
On systems with networked file storage (SANS) with slow disk IO times considerer usinginnodb_flush_log_at_trx_commit = 2. See 'adaptive flushing' for a description of the consequence.
mysqldump settings:
quick | |
max_allowed_packet | 24M |