This message was deleted.
# generals
sparse-intern-71089
05/12/2023, 4:11 AMThis message was deleted.
👀 1
w
worried-rain-74420
05/12/2023, 7:02 PMThat's not expected; the behavior should match your expectation. The number of parallel resource creation operations is controlled with the
--parallelworried-rain-74420
05/12/2023, 7:02 PMFor my own curiousity, what CLI version are you using and what language?
m
mammoth-camera-90962
05/18/2023, 2:14 AMSorry Robbie, been off sick and didn't get back to you quickly. Currently using Python and Pulumi
v3.66.0pulumi-aws5.36.0mammoth-camera-90962
05/18/2023, 2:16 AMWithout having looked too far into it, some of the team suspect that it might be related to how the python libraries communicate with the engine, and wait for resources to create. I unfortunately don't have code to point to at the moment though.
w
worried-rain-74420
05/18/2023, 11:28 AMHope you're feeling better!
It's also possible that somewhere along the way the Python runtime added a blocking future to the code, which would also cause the outcome you're describing (I think).
If your code is written such that the 20 resources are e.g. in a component resource, and the next 20 depend on that component, then you'd also get this same behavior.
m
mammoth-camera-90962
05/19/2023, 7:15 AMI don't believe that in this case it'll be the component resources. I'll try and make a reproduction just with dynamic resources that sleep to eliminate any dependencies.
I don't have a wealth of experience with asynchio let alone the deeper internals of the AWS Pulumi Python libraries - what could possibly cause some resources to be blocking futures and not others?
w
worried-rain-74420
05/19/2023, 12:07 PMwhat could possibly cause some resources to be blocking futures and not others?Programmer error on the Pulumi-side of things! Sorry if that was unclear. I'm saying it's possible it's a bug.