Memory Amount Needed

What amount of memory on a VPS is needed for Dolphin to run without bumping up against out of memory problems; such as killing the MySQL server?

 Depends on the amount of traffic. But i think 1 GB to even start with.

OK.  We started with 1 GB; of course that was total VPS memory for everything running on the server including the server itself outside of Apache and MySQL; for all processes running on the server.  We had a flood of sign-ups hitting us all at once and hit the memory limit which shutdown MySQL server.  I have put in a request for a memory upgrade to 2 GB.  I should have explored this before taking the site live.

Memory at 1GB is good I think.

Setting site timeouts are also important.

I have found this site very useful for "loading" you server http://www.blitz.io showing errors and timeout problems.

You get info like..

This rush generated 3,609 successful hits in 1.0 min and we transferred 1.85 MB of data in and out of your app.

The average hit rate of 57/second translates to about 4,986,280hits/day.

I used loadimpact.com

I just tested my VPS and looks like installing nginx and all optimization stuff did paid off

http://loadimpact.com/load-test/www.boonexdolphin.com-8d22f77249da0ada77332bd5c65ad23d

4 gigs of ram should be good. with 4 gigs you will have about 1 gig of extra ram if traffic starts to get heavy.  

1 gig is just barely enough to run the OS, MySQL and Apache.  Then you add in a control panel like plesk or cpanel and it goes up from there.

Site seems slow to me; we now have 2 gigs of ram (VPS) but I am wondering if we need more CPUs for Dolphin.  What does others recommend as an optimum VPS configuration for Dolphin?

i like to run 4 cores with 4 gigs of ram... 

What we are running into is the MySQL server shutting down and thus taking the site down.

I had our VPS provider take a look and this is what they told me:

Your VPS solution is not really made for an intense load.  Most server setups trying to run this kind of traffic have at least 8GB of ram and possibly 2 CPU's .

If you wanted to stay with the less expensive VPS approach as opposed to a dedicated server,  What I can suggest is limiting the amount of allowed MYSQL connections.  This will cause an error to appear on the users screen stating that they could not establish a database connection and to try again later.  This is definitely better than having to restart mysqld.  Is this something you would like done? Currently you have 65 connections active to mysql.  I would recommend cutting that in half to try and establish a baseline of what works well for your flow of traffic.  Thanks.