4 ms·

I've used Scaleway for several projects across many years, personal experience for those interested: Pros: - often free/unmetered bandwidth - very useful for

by ve55 6y ago

I've used Scaleway for several projects across many years, personal experience for those interested: Pros: - often free/unmetered bandwidth - very useful for some projects - relatively cheap prices - low downtime in general - decent support ticket response times Cons: - CPU is generally rather slow, very noticeable compared to mainstream providers like AWS, GC, etc - little selection of some parameters such as location (only Paris, Amsertdam, Warsaw) - have had some issues with stopping/starting instances being absurdly slow due to how they move the entire disk around in the past I think they're a decent choice for side projects that are intended to run at a low cost scale, since the unmetered bandwidth can add up to a lot of savings compared to some competitors (they don't lie about unmetered either - I used to have a $4/month instance that sometimes used >10TB/month, and they never complained), but I likely wouldn't use them for a serious or high-growth startup.

dspillett 6y ago
> 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.
- ve55 6y ago
  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.

by ve55 6y ago

dspillett 6y ago

> 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.

ve55 6y ago
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.