VPS (connection per database)

invo · 08-19-2007, 01:32 PM

Hello,
hello i have been managing 2 portals on a VPS .. the company that provided me the VPS have a good uptime but my VPs is getting mounted everyday
i have about 5,000 visitor everyday on both portals, and the load average range between 0,99 to 4.50 is this problem coming from the high number of people connecting to the databases or its the lack of sufficient RAM to handle that type of traffic ?
my VPS have 256 RAM operating on
CPU GenuineIntel, Intel(R) Xeon(TM) CPU 3.20GHz
Version os_FedoraCore 4
OS Linux 2.6.9

tHANKS FOR YOUR SUPPORT AND IDEAS

Dotster · 08-20-2007, 01:47 AM

Maybe 256MB RAM isn't enough? There are plans with bigger RAM from myriadnetwork.com with 512 MB.

damien_ls · 08-20-2007, 09:15 AM

What VPS platform is it? If you have burstable memory then 256MB may be fine, but any other platform (e.g. except Virtuozzo) then you're less likely to be able to cope with the peaks.

Your provider should be able to tell you what (if any) resource limits you're hitting in order to give you the best (technical) advice on upgrades etc.

However, it's possible that tweaking may help... talk to your provider and they should be able to give you some pointers.

I should also point out that the underlying physical hardware of your VPS is irrelevant - a big fat CPU just means that the provider can put more VPS's onto it before the node becomes overloaded...

gannik · 08-21-2007, 02:41 AM

Quote:

Originally Posted by Dotster

Maybe 256MB RAM isn't enough? There are plans with bigger RAM from myriadnetwork.com with 512 MB.

Why do you think it'll not be enough? What platform does Myriadnetwork.com provide?

iHubNet-Matt · 08-24-2007, 10:41 PM

Have a check with the host about the resource usage limit the VPS is having.

alemcherry · 09-20-2007, 01:59 AM

More ram should help, 256 is too low for a VPS. The OS, Plesk etc. takes a major chink and you are left with very little for your site.

You may also consider optimizing the script and DB. Are you using a custom script?

damien_ls · 09-20-2007, 03:33 AM

256 is quite low, but with a decent provider that is sensible about bursting (on the assumption that the virtualisation platform in question supports it, and the provider enables it) then it works fine.

It can make a big difference what control panel software you run - cPanel is a bit tight on 256, whilst DirectAdmin and Plesk will run fine on 128 (guarantee).

However, as I think I mentioned earlier - your provider should be able to tell you exactly which resources are hitting limits and causing your problems. Just throwing memory (or anything else) at the problem is a bit silly unless you know for sure that it's the problem...

Script (and/or SQL query) optimisation is one potential way to help; that's coming at the problem from the other end. I.e. you can either use less resources, or increase the amount of resources available - in both cases you end up with enough resources for your needs (hopefully!).

It could just be that the provider is overloading the node and you're not getting a good slice of CPU time etc. so your processes are left queuing hence things build up and so on..