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.
Mysqld 1662MB RAM
Mysqld 1662MB RAM
Hi
Just wanted to check, it does not feel normal for one website with a 13MB database to need over 1,5GB of ram for mysqld. What do you guys think? In my mind it must be something seriously wrong with my server or vestacp installation?
Yours // Niklas
Just wanted to check, it does not feel normal for one website with a 13MB database to need over 1,5GB of ram for mysqld. What do you guys think? In my mind it must be something seriously wrong with my server or vestacp installation?
Yours // Niklas
-
- Support team
- Posts: 1096
- Joined: Sat Sep 06, 2014 9:58 pm
- Contact:
- Os: Debian 8x
- Web: apache + nginx
Re: Mysqld 1662MB RAM
Well it'd not be proper to say that outright... depends on your site's payload and coding abilities and architecture.
What is usual visit count per day for your site ?
What CMS/Framework you use ?
What MySQL version you are using ? Are there any "Slow Queries" ? What does "show processlist;" command show up ?
Is SWAP enabled ?
dmesg | grep mysql ?
# optimise and Repair all your DB's
mysqlcheck --all-databases -o
mysqlcheck --all-databases --auto-repair
mysqlcheck --all-databases --analyze
# Clean logs
> /var/log/auth.log
> /var/log/mysql/error.log
> /var/log/mysql.log
> /var/log/mysql.err
# Then tail them for fresh error.
tail -f /var/log/mysql/error.log
Also consider upgrading to MariaDB 10.1 or PerconaDB. but if your app's queries are not optimized... you may consider re-developing the application
What is usual visit count per day for your site ?
What CMS/Framework you use ?
What MySQL version you are using ? Are there any "Slow Queries" ? What does "show processlist;" command show up ?
Is SWAP enabled ?
dmesg | grep mysql ?
# optimise and Repair all your DB's
mysqlcheck --all-databases -o
mysqlcheck --all-databases --auto-repair
mysqlcheck --all-databases --analyze
# Clean logs
> /var/log/auth.log
> /var/log/mysql/error.log
> /var/log/mysql.log
> /var/log/mysql.err
# Then tail them for fresh error.
tail -f /var/log/mysql/error.log
Also consider upgrading to MariaDB 10.1 or PerconaDB. but if your app's queries are not optimized... you may consider re-developing the application