Server stress testing and VPS versus dedicated servers
We used to have a dedicated server (1 & 1) and it was very rare to have a problem with a server having problems.
Recently we have moved to a VPS (Wiredtree.com) with similar characteristics to our old dedicated server, but have noticed frequent out of memory issues, mysql that needs to be restarted, etc ... as when deliberately running intensive scripts. and just by accident during normal use.
Because of this, we are considering switching to another VPS - this time to Slicehost to make sure it performs better.
My question is twofold ...
Are their easy ways so that we can test the VPS on Slicehost to see if the same issues occur without actually migrating everything?
Also, is it possible that the problems we are facing are not just with the provider (Wiredtree), but with the difference between the dedicated field and the VPS (despite similar characteristics)?
a source to share
The best way to stress an environment test is to load it under load. If this VPS hosts a web application, use one of the many available web server tools: ab , httperf , Siege, or http_load . You don't always care so much about the statistics from the tool itself, but more than that, it puts a predictable load on the server so you can tune Apache to handle it, or at least not crash and write.
The only problem you run into testing on Slicehost is that you are at the mercy of the internet and your bandwidth for Slicehost. You may not be able to load enough server load to reach meaningful output.
Instead, you may find it just as valuable to launch one of the many virtualization products on the market and build a virtual machine with comparable specifications in the VPS plan you are considering. Local testing through your local network will allow you to put a higher and more predictable server load.
You don't need to port everything anyway, but you will need to set up the environment to run your application with representative data in your database.
A VPS with similar specifications for a dedicated server should do roughly the same thing, but you still need to configure Apache, MySQL, and any other long-lived server processes to achieve good performance. In my experience, the out-of-the-box Apache configuration in many Linux distributions is not ideal and will allow too many child processes, excessive memory, and sending the server into a death spiral.
a source to share