Best droplet for webshop using Prestashop

June 17, 2014 5.2k views
oliwer.helsen
By:
oliwer.helsen
Hello, I'll kick off two webshops. The first will only have about 100-200 visits a day and the other will have up to 500-1000 visitors a day. Which droplet size should I choose for each? I will use Prestashop.
Log In to Comment
1 Answer
asb MOD June 17, 2014
I'd suggest going with a 1 GB droplet. You might be able to get away with the 512 MB, but the larger one will ensure that you can deal with any traffic spikes. If you use the 512 MB droplet, I'd recommend add a swap file: https://www.digitalocean.com/community/tutorials/how-to-add-swap-on-ubuntu-14-04 It will give you a bit of a buffer if MySQL starts using a lot of memory.
How To Add Swap on Ubuntu 14.04
by Justin Ellingwood
Swap space can be used as an "overflow" area for your system when you run out of RAM. The operating system can store data that would normally be kept in RAM on the hard drive in a specially formatted file. In this guide, we'll demonstrate how to create and use one of these files in Ubuntu 14.04.
Reply
  • oliwer.helsen June 17, 2014
    Thanks man! I Will try the swap. IF the shop gles well and we get around 8-10k of visitors. Which one do you think is the best?
  • asb MOD June 17, 2014
    The real issue is with concurrent visitors, not total. So you need to this about how many might hit the site all at once. As you start to grow, you should look into doing some load testing. You can use something like ApacheBench for that. There are also external services. You might also think about doing something like breaking the database out onto its own server: https://www.digitalocean.com/community/tutorials/how-to-set-up-a-remote-database-to-optimize-site-performance-with-mysql Setting up some kind of cache would also be a good idea.
    How To Set Up a Remote Database to Optimize Site Performance with MySQL
    by Justin Ellingwood
    When your site begins to get more visitors, you may have to think about how to handle the additional traffic. One easy way of doing this is to separate your database operations from your web server so that each can handle its own load. In this guide, we'll demonstrate how to do this for a WordPress site built on Nginx by configuring a remote MySQL database.
Have another answer? Share your knowledge.