Vesta Control Panel - Forum

hello guys,

I am running a default vesta installation on a fresh debian 7 64 bit

I host 21 wordpress websites, which get 50 to 100 hits per site-per day

I am running this configuration on a 1 GB single core vps plan...

Mysql stops from time to time (at least once every 48 hours) and doesn't start with service start mysql command.

I have to restart the server to make it work.

Do you think 1 gb is not enough for 21 wordpress websites? Do you think that is why mysql keeps crashing?

On what amount of ram and websites do you run vesta ? Please share

I run it on 32gb. :)

Anyway, its due to other services consuming too much memory.

Check the graphs and services in Vesta CP and you will see how much each service consumes memory.

You can fine tune some settings to use less RAM but most likely it will just slow everything down.

A good indication that you have enough ram is when used swap size is 0. :)

karlis.kisis wrote:I run it on 32gb. :)

Anyway, its due to other services consuming too much memory.

Check the graphs and services in Vesta CP and you will see how much each service consumes memory.

You can fine tune some settings to use less RAM but most likely it will just slow everything down.

A good indication that you have enough ram is when used swap size is 0. :)

How many websites do you host in 32 gb?

Actually I am waiting for the Nginx only vesta version to upgrade things. Maybe (if the price is affordable) I can give paid version of Vesta a try.

If you are running wordpress only and not a mailserver then you can stop mail services:
dovecot
clamd
spamassassin (or spamd)
exim

bind (named) also consumes a lot of ram (if you are not using it, stop it as well)

eventually just run nginx, httpd and mysqld :)

karlis.kisis wrote:If you are running wordpress only and not a mailserver then you can stop mail services:
dovecot
clamd
spamassassin (or spamd)
exim

bind (named) also consumes a lot of ram (if you are not using it, stop it as well)

eventually just run nginx, httpd and mysqld :)

actually, if vesta installation asked us which services we wanted during setup, it would be great.

now, disabling those won't remove dependencies.

if the service is not running then it doesn't consume any RAM :)

but, yes, I agree on the Vesta CP setup part.. or disabling it later from the panel.

karlis.kisis wrote:if the service is not running then it doesn't consume any RAM :)

but, yes, I agree on the Vesta CP setup part.. or disabling it later from the panel.

vesta is not mature at the time. plus they dont stick to "roadmap dates"

community expects frequent updates, now it gives the impression "vesta can be abandoned anytime" + "this is a 1 man project"

if they make the community bigger, release frequent updates and make believe everyone that they stand behind their product, they ve got more chance to sell paid version.

if vesta installation asked us which services we wanted during setup, it would be great.

This function is planned
https://bugs.vestacp.com/responses/adva ... components