Publishing Space
To ensure that PhixFlow can publish data changes, its database must have enough space to hold a copy of the largest table. For MariaDB, this space is in the file system.
Tuning
Tuning MariaDB for optimum performance is a potentially complex task. However, in general, because PhixFlow uses simple statements to perform its operations, you can rely in most cases on a few settings to make use of available resources on the database server.
Memory
MariaDB installations used for PhixFlow use InnoDB as the storage engine.
Rule of thumb settings
As a very broad rule of thumb, we recommend that you allow at least 20% head room on top of the assigned buffer pool size (innodb_buffer_pool_size) for running the database. To work out how much to assign to the database, take into account account any other software that needs to run on the sever and an allowance for the operating system itself.
...
Tomcat, if you are running Tomcat and the database on the same server (see https://phixflow.atlassian.net/wiki/pages/resumedraft.action?draftId=8643674113 for Tomcat’s memory requirements)
A reverse proxy, if you are also running this on the same server; although in general these will have a minor footprint across all resources (CPU, memory, storage) for most PhixFlow instances
Anti-virus, and other security and monitoring software; see note on https:/wiki/spaces/INTRANETphixflow.atlassian.net/wiki/pages/1326383177createpage.action?spaceKey=INTRANET&title=MariaDB%20Linux%20install to make sure that any anti-virus software does not interfere with MariaDB
...
| Code Block |
|---|
sudo systemctl stop mysql sudo systemctl start mysql |
Using mysqltuner
You can get an insight into the overall memory requirements of your database by using database management tools like mysqltuner (https://github.com/major/MySQLTuner-perl). Note that mysqltuner can be installed from the standard repositories on many linux distributions.
...