OpenApp tuning
From Openpanel Documentation Wiki
OpenApp-tuning tries to set some nice values for the processes that your appliance uses. This includes disabling functions that your appliance doesn't use (like InnoDB for Wordpress/Joomla).
Tuned services
The following services can be tuned with OpenApp-tuning:
- Apache2
- Mysql
- Lighttpd
Supported OpenApp Appliances
The following OpenApp Appliances use OpenApp-tuning to tune the mentioned services:
- OpenApp-wordpress, OpenApp-joomla
- Tunes Apache2 in such a way that it should not use too much memory by setting a reasonable amount of maxclients. It also disables InnoDB in Mysql, since Joomla and Wordpress do not use it. It does set some better values for caches in Mysql.
- OpenApp-mysql
- Tunes Lighttpd in such a way that only the minimal amount of php-cgi processes are started to use phpmyadmin. The rest of the memory is allocated to Mysql. Also, InnoDB is configured and tuned.
- OpenApp-ruby
- Tunes Apache2 in such a way that it should not use too much memory by setting a reasonable amount of maxclients. It keeps InnoDB enabled but uses the default values for it. It does set some better values for caches in Mysql.
Disabling OpenApp-tuning
OpenApp-tuning watches /etc/OpenApp-tuning/config to see if it should configure specific services. If you do not want OpenApp-tuning to tune a service, set the value of TUNE_$SERVICE to anything but 'true'. Please note that if you disable tuning for Mysql, it might have changed the iblogfile-size and you might need to change that manually to the value you want/need.