WARN MySQL variable tmp_table_size variable is set to 128MB

If you see this warning in the panel, it indicates that your tmp_table_size is set to 128MB. Upon installation the Media Control Panel automatically deploys a profile based on the system specs, if your server is hitting our minimum specificatons (specifically 2GB of memory) then the tmp_table_size will be set to 128MB. This is supported and should work when working within the limitations of the minimum specifications. You will only see this warning when more than 10 services are active on the panel which is above the recommended maximum for servers hitting minimum requirements.

This is still a warning and can be ignored if you are unable to upgrade to a higher memory capacity. If you are able to upgrade your server to have more memory increasing the tmp_table_size will increase the speed and performance of database operations. This may be especially important if you're having high concurrent connections (10,000 concurrent connections) and thus far more data in reporting. The higher table size will assist with the performance of reporting/historics and in reducing load on the hard disk If you do upgrade to more system memory, we recommend you increase the tmp_table_size to match our presets:

  • For more than 4 GB we recommend setting the tmp_table_size to 256M 
  • For more than 16 GB we recommend setting the tmp_table_size to 512M 
WARN MySQL variable tmp_table_size variable is set to 128MB.
INFO tmp_table_size is set automatically during install based on available memory.
INFO 
INFO We recommend increasing system memory to > 4 GB and updating
INFO /usr/local/mediacp/mysql/my.cnf increasing tmp_table_size to 256M
 
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Liquidsoap reinstall

Liquidsoap has a large quantity of dependencies and can easily fail installation or upgrade...

Remove database table prefix

A database table prefix was originally used in the MediaCP software many years ago and has since...

Removing database table prefix to improve stability on older installations

The database table prefix has not been a default for some years now and can often cause issues...

Why do I see 'An error occurred' message in the MedicaCP?

This is a generic error and can be the result of several problems listed below.- Underperforming...

Fast DNS resolution and connection to license server failed test

The System Health check has failed the following test: Fast DNS resolution and connection to...