DO Ideas 2

Offer different hardware configurations based on the use case (DB, Storage, Decrypt etc.)

This is a repost of a previous idea (granular, slider-based hardware selection) as suggested by Moisey:

"..However, we do believe that there are different workloads that require different servers and hardware. For example caching services need a lot of RAM but not much else, DBs need very fast harddrives and CPU, and then there are cases when you just want a bunch of storage and not much else.

This is an area that we are exploring to see if we can begin provisioning different hardware types sometime in 2014 and testing to see if customers like the ability to select a different type of VM with different combinations of underlying specs based on their workload.

If anyone wants to startup a separate uservoice request for that we then upvote from there we can provide regular updates on those projects..."

This would be useful when building out a heterogenous system, and especially in cases (like hardware-accelerated decryption) where it might involve specialized hardware. This would also lay the groundwork for other specialized cases such as HPC (with GPUs) and mining.

I'll start it off with my +3 votes...

  • JP Barringer
  • Sep 11 2018
  • Attach files
  • Kounavi commented
    September 11, 2018 17:36

    Yes! I'm into this a lot since we perform DevOps deployments for research purposes and beyond the size of ram (which we need plenty for expirements) and 3-4 CPUs everything is not needed. However, I assume other would like 64 GB RAM without the need for 20 CPUs!!! :) :) :)

  • DRJ commented
    September 11, 2018 17:36

    Alright, we've enjoyed and praised your great service. Now, we need flexible droplets. High CPU/Memory options are driving most of our projects to Google Cloud and AWS. As cloud services get cheaper, the IT departments can afford to hire some badass guys who draw the most unbelivable architectures *with clear CPU/RAM requirements*

    We would also need to have a VPC that allows our machines to be "safe" without requiring firewalls/blocking ports. We don't need the complex stuff immediately, like tunnels, etc.

    You guys are in a good space right now, but the other guys are making you look like the place to host test projects and one-page websites. Think about this.

  • Rob Frawley 2nd commented
    September 11, 2018 17:36

    I cannot stress enough how amazing this feature would be. For instance, right now I needed to run a test against our live DB, which has an innodb buffer pool size of 80GB, so I need +80GB of ram. I don't need extra hard drive space; I don't need extra bandwidth, and I don't need extra CPU cores. I just need a standard droplet with the ability to set a custom amount of RAM so I can load the same MySQL config that is used in production for the purpose of playing with charset and collation modifications.

    This feature would be great. I can only give it three votes, but I'd give it all of my votes if I could!

  • Andrew Maizels commented
    September 11, 2018 17:36

    I can see the difficulties in implementing custom droplet sizes or network storage, but this looks like it would be easy to implement and provide a good solution for most users.

    I could deploy a storage droplet for my files, a CPU droplet for my database, and a bunch of regular $10 droplets for my application.

  • Anonymous commented
    September 11, 2018 17:36

    this is an awesome idea. hope its implemented soon