Fastest provider #260
-
I started using CodeBuild as the provider as it seemed like the simplest solution given that its serverless. But it seems like provisioning times are at least 1 minute, presumably to pull the docker image. Is there a way to speed that up? So I tried EC2 spot, figuring that'd be cheap and always available, but it seems as though it doesn't leave the instances running and spins up a new instance for every job. Is there a way to leave All this is to say: what's the fastest provider? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Lambda is the fastest provider but it is very limited by having a read-only file system, short time limit, and only 10GB of space. CodeBuild can be sped up by using bigger instances. EC2 might be faster still. None of the options leave the runners behind because we aim to spin up ephemeral runners. Persistent runners can cause weird build issues as anything installed in one build will be available in the next. It sounds like you're looking for #191. |
Beta Was this translation helpful? Give feedback.
0.9.1 now has support for
EcsRunnerProvider
and you can use something like:Even with the default
minInstances: 0
, the instances stay behind for 15 minutes. You have access to the ASG withnew EcsRunnerProvider(this, 'ECS').capacityProvider.autoScalingGroup
so you should be able to even add scheduled scaling or anything else you might need. And if you want even more control, you can override the capacity provider completely.