What plan of DigitalOcean is the best for me?

Hello, there

Choosing the right Droplet plan depends on your workload. An oversized Droplet would underuse its resources and cost more, but an undersized Droplet running at full CPU or memory would suffer from degraded performance or errors.

In your case, you can start with a smaller droplet and then upgrade in the future if this is needed. I’ll recommend having at least 2GB of RAM.

You can also resize a Droplet to a larger plan after creation, including resizing to a larger Droplet plan of a different kind. For example, you can resize from a Basic Droplet plan to a larger CPU-Optimized Droplet plan. See the Droplet pricing page for a full list of plans and prices.

You can always check our tutorial on Choosing the Right Droplet Plan

https://docs.digitalocean.com/products/droplets/resources/choose-plan/

Hope that this helps! Regards, Alex

Totally agree w/@Kamal; so what follows are more educational recommendations as opposed to suggestions on what to do w/your specific site. Check out: <br> <br>1.) <a href=“https://www.digitalocean.com/community/articles/how-to-set-up-nginx-load-balancing”>How To Set Up Nginx Load Balancing</a>; <br> <br>2.) <a href=“https://www.digitalocean.com/community/articles/how-to-install-wordpress-nginx-php-and-varnish-on-ubuntu-12-04”>How To Install Wordpress, Nginx, PHP, and Varnish on Ubuntu 12.04</a>; <br> <br>3.) <a href=“http://ewan.im/900/10-million-hits-a-day-with-wordpress-using-a-15-server”>10 Million hits a day with WordPress using a $15 server</a>; <br> <br>4.) <a href=“http://kbeezie.com/caching-wordpress/”>The Importance of Caching WordPress</a>; <br> <br>5.) <a href=“http://aws.amazon.com/cloudfront/”>Amazon CloudFront</a>. <br> <br>If you’re thinking about splitting up your site across various droplets, however, I would definitely recommend a configuration-management tool. <i>See</i> <a href=“https://www.digitalocean.com/community/articles/how-to-install-puppet-on-a-digitalocean-vps”>How To Install Puppet on a DigitalOcean VPS</a>.

No body can answer this question as no body knows how your app is written, what the average memory usage per request is, etc… <br> <br>It depends on <strong>a lot</strong> of factors. I suggest you start with a 1GB droplet and see how your app performs and then scale up as needed.

Thanks so much wwalker!! Your answer brought me some light! <br> <br>Pablo, i still don’t know how much static vs dynamic content it willl serve =( My site is www.pergunteaumamulher.com <br> <br>My visitors are 90% from Brazil. <br> <br>I can’t tell you abou hiogh availability also, i still don’t know what it could mean, but i’m seriosly thinking about splitting, one droplet to my site, and another only for hosting podcasts (.mp3) files <br> <br>What you guys think?? <br> <br>Thanks so much!!

To provide you w/solid recommendations, you need to provide more details: <br> <br>How much static vs dynamic content will the droplet serve? <br> <br>Are your site visitors disbursed all over the globe or are they concentrated to a specific geographic area? <br> <br>Are you willing to pay for a high availability (HA) configuration (in the form of additional droplets)?

http://www.slideshare.net/modoc/apache-performance-12508773 <br> <br>Gives some indication of the abilities of modern web servers. Look around page 10 of the presentation. <br>

This is according to how heavy your pages are. First you calculate your page rate. 30K/ day is roughly 1 page every 3 seconds, BUT you may well have times of day with 10 times more visitors than the average. Therefore multiply by 10 and assume you have a peak load of 3 pages per second. <br> <br>Some people’s pages have 4 or 5 elements, others can have 100 or more elements per page. So, going with a worst case type measure, you may have 100 static elements per page, and 3 pieces of dynamic dynamic content per page. <br> <br>That gets you to 30 static elements per second and 1 dynamic content piece per second. <br> <br>Apache on a single CPU should be able to handle that. however the db and or apache may consume more than 512 MB. I’d go with the 1 GB plan myself. <br> <br>Then I would install atop to monitor the system performance over time. <br>