3 ms·
So far, testing Digital Ocean, the ability to spin up a new VM in 55-70 seconds, clone over one of my own "snapshots" created on a lower cost VM and configured
by decentrality 13y ago
So far, testing Digital Ocean, the ability to spin up a new VM in 55-70 seconds, clone over one of my own "snapshots" created on a lower cost VM and configured to perfection, test it for 5 minutes to an hour and then destroy it with the comparible reverence of used toilet paper, has been extremely invigorating and ridiculously useful.
Messing with VM configuration for half the time rather than directly testing during that time and destroying well before the metered hour seems like a practice from century ago in terms of advancement, after what I just experienced when testing Digital Ocean.
And they detected in my 4-7 sentence questions that I was unsure of their platform and gave me incentives to spend the time to try them out, and it made all the difference. I did spend a few hours trying, and I am impressed. Now, all that's needed is the long term testing process with extremely respectable numbers to start with, even before jRuby/Java warmed up completely.
- decentrality 13y agoReally feeling the CPU caps ( per package ) even at Digital Ocean now, even though the actual packages can scale cores. Would be nice to add/remove resources a la carte. Looks like it'll be at least another 6-18mo before the industry shifts to more concurrent friendly virtual machines. At Digital Ocean: No ability to add IP addresses, change the RAM, cores ( as I said ) or any other resource without moving up to the next virtual machine. Seems like Linode and DO are not so different after all, but two of a kind.