DO Ideas 2

Allow us to power down a droplet, and not continue to be charged.

Allowing us to create say 50-100 droplets, and by powering up and down, you would start charging or stop charging depending on what is currently running, The issue with having to destroy a droplet and rebuild it later to turn it back on is not ideal by any means. It takes too long to rebuild the droplet. The time it takes to power on or reboot is fine, but the fact that you continue to charge full rates as if the server is being used is not a good deal. You could have a price plan even for on/off states charged by the hour or up to X amount.

  • Brian
  • Sep 11 2018
  • Will not implement
  • Attach files
  • Martin Buhr commented
    September 11, 2018 18:52

    I wasn't aware that this was the case an was charged for a full months use of a droplet I created as a test.

  • Moisey Uretsky commented
    September 11, 2018 18:52

    The issue with that is that a powered on droplet or a powered off droplet really consumes the same resources. A powered off droplet still reserves the IP, CPU, RAM and diskspace so essentially its the same thing.

    Certainly understand that it would be easier to restore by a simple power on / power off - but if everything is still reserved for it, then its technically still utilizing that portion of the resources because they are otherwise unavailable.