Expecting a spike in traffic on my website. Not sure what to do.

I moved this question to the Web Dev forum where you are most likely to get responses ... you posted in the Geeks' Lounge which is just for off-topic hanging out and not any serious questions.

I can tell you from my own experience that if you aren't capable of handling all of your visitors, your servers COULD crash and not just slow down.

Firstly, I assume your site uses a database since you mentioned phpBB ... is the database server on the same physical box as your web server??

It's been my own experience that Apache could crash if it is trying to use more memory than the physical server has available. So, for example, if each instance of executing the script takes up 8 megs of ram (just making stuff up), then if it's hosted on a server with 2 gigs of ram, there's clearly an upper limit on how many scripts are capable of executing simultaneously before something won't be happy because it's trying to allocate more ram than physically available.

The good news is that it usually takes only a second for a script to execute, and once it finishes executing, it frees up the memory for another instance of the script to execute. Therefore, it's pretty unlikely that soooooooooooo many people would be trying to load a page at the exact same second as to use up all of your ram. What would simply happen is that, based on how many cpu cores you allocate to Apache (or whatever httpd server you happen to be using), the load average of your server will increase, as load average is a representation of how many processes are waiting in line to be processed.

phpBB is database-driven, however. This is where my question relating to your database comes in, though. The heavier the load on the database server, the longer it takes to execute an individual MySQL query.

Lots of MySQL queries get executed from within a single phpBB page, and each time a database request is issued, phpBB sits there and twiddles its thumbs until it receives a response back.

Therefore, if MySQL slows down too much, it could cause those 1-second long web scripts to take 20 or 30 seconds instead, because they remain active even if they're not using up cpu time and simply waiting for the database to return something. Now, with scripts taking 30X as long to process, it's much more of a reality that we won't have enough RAM to accomodate all of the concurrently running scripts at once. That can kill the server.

In conclusion, talk to your host about offloading your database to the cloud.

I wish I would not have missed this thread, otherwise my recommendation would have been to bring up the new VPS in parallel, then simply cutover when the new VPS system was stable and validated, especially since you indicated that additional costs were not of concern.

For anyone else reading this thread, see more..
http://www.daniweb.com/web-development/threads/470774/moved-my-phpbb-forum-from-shared-to-vps-now-i-have-serious-issue