DO Ideas 2

offer more CPUs

when I compare the offerings between Linode and DigitalOcean,
one thing stands out: all Linodes start with 4 cores!

DigitalOcean could really improve their offerings in respect to CPU cores!

It would be good if your plans would be as follows:

- 1GB / 2 CPUs / 30GB
- 2GB / 4 CPUs / 40GB
- 4 GB / 4 CPUs / 60GB
- 8GB / 8 CPUs / 80GB
- 16GB / 8 CPUs / 160GB

or at least offer the option to add more CPU cores to an instance

  • Tilo
  • Sep 11 2018
  • Will not implement
  • Attach files
  • Welcome 365 commented
    September 11, 2018 19:01

    I agreed.

    I have the same deployment. the app server need more cpu power than db server.

    High cpu cores, less SSD high network bandwidth would be great combo for app server. (maybe a little bit higher price =>)

  • Moisey Uretsky commented
    September 11, 2018 19:01

    Hi Tilo,

    You are right in your writeup and here are our take aways:

    1. We are discussing adding more CPU cores to the lower plans now that we've had a chance to collect a lot of usage information.

    2. While you are right that there are many different use cases the item that is missing is average cost. Sure you may be better off having a 96GB RAM machine and 1CPU core, however if you average out the cost of the resources from other providers that provide a mixture of different resources and compare that to our plans you will see that usually we are a cheaper alternative.

    So while you may not like having 16CPU cores when you only need 1 because you just have a high RAM instance, if the overall cost of our virtual server is still smaller than what you would be paying somewhere else why worry about it?

    Unfortunately we can't segment out resources because that means we have to stock different types of servers, with different configurations, and part of us being able to offer our pricing as it is, is by standardizing. Sure it won't fit every application and need but I think the overall cost is still in your favor even if you end up with some resources that aren't used.

    Think of it like a sushi restaurant you can either order the combo which is cheaper than ordering the individual pieces that come in it. So if you wanted to pick your own CPU and RAM you could, but you would pay more, so why do it when you can have those resources bundled together for less?

  • Tilo commented
    September 11, 2018 19:01

    Hi Moisey,

    thank you for looking at this!

    I want to add one more important angle here...

    If you think about how customers will use your instances (customer use cases),
    do they really get the instances they need?

    e.g. all your plans scale up somewhat linearly in SSD, RAM and in CPU cores.

    While this seems straightforward at first to scale the payment plans up linearly,
    the typical customer use cases do not really match the resulting product offerings.

    I'm currently running a large application deployment in the cloud with front-ends, back-ends and db-servers -- and all three need high-end instances with very different resources.

    e.g. let's look at high-end instances for a moment:

    - high-RAM, high-SSD instances often used as database servers of some sort, and these typically do not need more than 4 CPU cores.

    - instances with large CPU-core number are often used for application servers like web-servers, and they typically do not need lots and lots of RAM, sometimes not even lots of SSD.

    On the other hand, looking at the lower-end spectrum for a moment:

    when you are just about to deploy a proof of concept, a staging server, or a small deployment, you may want to put many things on one small instance and don't want to pay for lots of resources you don't need.

    that's where my earlier suggestion with more CPU-cores comes in.

    Your product offerings are missing lower-end offerings with 4 cores, as well as high-end offerings with different resource allocations, like few CPUs.

    If you look at competitors instance offerings, you can easily see that I'm not just making this up -- they actually cater to these different types of customer use cases.

    I think it would be a good idea for Digital Ocean to do the same -- after all this should be only a matter of a configuration file in your backend infrastructure..

  • Moisey Uretsky commented
    September 11, 2018 19:01

    Unfortunately it's not possible to arbitrarily select RAM and CPU, we could allow that but it would actually cost more than using one of the predefined plans.

    It's the same thing like going to a sushi restaurant and ordering one of their packages vs buying each piece a la carte. You may get a couple of pieces you don't need but it will be overall cheaper than ordering everything a la carte.

  • Kevin McCaughey commented
    September 11, 2018 19:01

    I agree.

    What about allowing people to pick their number of CPU's and amount of RAM, within reason (i.e. within how you can implement it).

    For example, I would like to be able to add a CPU to a smaller memory plan if it turns out it is CPU intensive but not RAM hungry.

    Even the higher plans seem weak on CPU.

    I don't mind paying extra for this. I really like DigitalOcean and would move all my stuff here, but the 1 CPU vs 4 CPU on Linode is still holding me back with some apps.

  • Moisey Uretsky commented
    September 11, 2018 19:01

    Hi Tilo,

    Thanks for the suggestion we'll definitely review it =]