Hi All. First of all, I want to appreciate your gr...
# general
a
Hi All. First of all, I want to appreciate your great effort at Pulumi. I'm using it in my project. It's great :). I have a question about the correlation between component resources and parallel execution.
pulumi up
has flat
--parallel
available. Does it make sense to use component resources with this flag set to 3-4 to speed up the deployment of the resources? Currently, we are not using the Component Resources, but I'm wondering if this could help optimize deployment time. At the moment, it's around 8 minutes. I wish to cut it by at least a few minutes because, soon, we would like to set gitops pipelines.
Apologies if it's wrong channel ๐Ÿ™‚
l
Hello @adamant-football-558, thanks for the kind words on Pulumi! Regarding the
--parallel
flag, the default value is
unlimited
which means we try to perform as much as possible concurrently. If you set a value yourself, you are actually reducing the number of resources our engine will provision concurrently. When resources do not have any dependencies on each other, Pulumi will provision these concurrently. When you pass the output of one resource as an input to another resource, you create a dependency and Pulumi will provision the first resource before the other resource. The
dependsOn
resource option makes a similar dependency.
As long as you limit mentioned dependencies then the introduction of components wonโ€™t change much on what Pulumi can provision concurrently.
a
Hey @limited-rainbow-51650, thanks for the response.
Regarding the --parallel flag, the default value is unlimited  which means we try to perform as much as possible concurrently. If you set a value yourself, you are actually reducing the number of resources our engine will provision concurrently.
-> so no change here ๐Ÿ™‚
When resources do not have any dependencies on each other, Pulumi will provision these concurrently. When you pass the output of one resource as an input to another resource, you create a dependency and Pulumi will provision the first resource before the other resource. The dependsOn resource option makes a similar dependency.
-> here I might work on the diagram then ๐Ÿ™‚ thanks again