Droplet resize: CPU/RAM-only vs disk-inclusive path for a low-traffic workload
Goal I want to reduce monthly cost for a low-traffic workload running on an over-provisioned DigitalOcean Droplet by resizing it to a smaller plan. The Droplet is billed hourly with a monthly cap, so moving to a smaller plan should lower the rate, but I need to pick the right resize path before powering off. Uncertainty DigitalOcean documents two resize opti
digitalocean