New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
What can an 128MB RAM VPS (OpenVZ, SSD HDD) serve?
MichaelBui
Member
in General
I'm going to run some websites (SF2-based) on my VPS from @ramnode:
- 128MB RAM (128MB swap)
- SSD HDD
How many concurrent users you think that VPS can serve?
(I know the answer will depends on the complexity of the code but I just want a rough estimation). Thanks a lot!
Comments
concurrent users?
8-10 maybe
It all depends on which web server your using.. If your using Nginx you can serve more requests....
If possible use mem cache it will improve site performance
http://lowendbox.com/blog/yes-you-can-run-18-static-sites-on-a-64mb-link-1-vps/
http://lowendbox.com/blog/xenvz-99-pence-openvz-vps-quick-review/
depends how you will configure and set it up
@MichaelBuiA - 128MB VPS from different providers can provide very different results. Good news is Ramnode runs some extremely good low ram VPS nodes. The results you get will depends on what you run on it. If you going to be steaming (SF2) then concurrent connections was the correct question to ask. To test it just set up your site and open browser tabs and stream to each. Then see how much RAM that each concurrent connection uses in the VPS.
Disclaimer: I have a RamNode 256MB VPS in Seattle that gets about 100,000 hits a day on an apache web server, no mysql, and never runs out of RAM.
I have setup an website using Apache2, CakePHP and used ab to benchmark it:
How do you guys think about the above result?
I have a test rig setup there with varnish serving directly from memory. At best, AB concurrency on a page is 80 without the server starting to drag on requests (into the 100ms). So assuming firefox's 6 requests/server... 13 concurrent real users by that definition at least.
The biggest problem you'll face is the single CPU. If you have php fpm, and rely on that exclusively to serve content, you're probably going to lock yourself out far far lower.
Use Nginx, you will be able to server to hundreds of users static content. Dynamic content depends on complexity of code and the server/client programming split. If you offload most of the interactive stuff to JS, and only run the bare minimum of commits on the server, then you can also serve hundreds of users.
You'll probably struggle running the standard LAMP, mainly because MySQL and Apache are RAM hungry in my experience.
How about MongoDB instead of MySQL