We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Tuning MySQL 5.6 on Vesta
Tuning MySQL 5.6 on Vesta
I tried my old percona-tuned my.cnf, but it doesnt work on Vesta (strange errors and no start)
So, here are my specs:
Intel Core i7 3770 @ 3.4GHz
16GB DDR3 1333MHz RAM
2 x 3.0TB S-ATA storage.
Running debian 7 (Wheezy) with VestaCP and MySQL 5.6.
1 large database (3GB) running InnoDB and the other 5 databases are MyISAM @ around 100MB/each (more or less)
The config (Vesta included?) is now:
Any tuning tips are welcome.
So, here are my specs:
Intel Core i7 3770 @ 3.4GHz
16GB DDR3 1333MHz RAM
2 x 3.0TB S-ATA storage.
Running debian 7 (Wheezy) with VestaCP and MySQL 5.6.
1 large database (3GB) running InnoDB and the other 5 databases are MyISAM @ around 100MB/each (more or less)
The config (Vesta included?) is now:
Code: Select all
[client]
port = 3306
socket = /var/run/mysqld/mysqld.sock
[mysqld_safe]
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
nice = 0
[mysqld]
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
basedir = /usr
datadir = /var/lib/mysql
tmpdir = /tmp
lc-messages-dir = /usr/share/mysql
explicit_defaults_for_timestamp
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1
log-error = /var/log/mysql/error.log
# Recommended in standard MySQL setup
sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
# * IMPORTANT: Additional settings that can override those from this file!
# The files must end with '.cnf', otherwise they'll be ignored.
#
!includedir /etc/mysql/conf.d/