> have had some issues with stopping/starting instances being absurdly slow due to how they move the entire disk around in the past
That is not unusual on other cloud providers too. It is a opimisation they must choose: keep the vdisks close to the CPU(s) that will be running the VM but have the expense of moving it around to put it in the right place on startup, or let the vdisk be hosted anywhere in the network so startup is almost instant but IO performance suffers while running. Most, though presumably not all, choose to optimise for better performace in active use.
Yeah, that seems about right, thank you. But also when I meant 'slow', some times I would wait hours for a disk that was ~200GB, which seemed far beyond what is reasonably expected. It may have been an isolated instance and not the general case there, since my new ones are all much more reasonable now.
That is not unusual on other cloud providers too. It is a opimisation they must choose: keep the vdisks close to the CPU(s) that will be running the VM but have the expense of moving it around to put it in the right place on startup, or let the vdisk be hosted anywhere in the network so startup is almost instant but IO performance suffers while running. Most, though presumably not all, choose to optimise for better performace in active use.