https://pulumi.com logo
#general
Title
# general
o

orange-airport-64592

11/09/2022, 8:14 AM
why reading output from other stacks is so slow? When I use
pulumi.StackReference
My backend used aws s3
e

echoing-dinner-19531

11/09/2022, 9:34 AM
It has to grab all the state of that stack to read the outputs, so if the state is large and your bandwidth to S3 limited it will be slow.
c

cuddly-magician-97620

11/09/2022, 2:52 PM
@echoing-dinner-19531 Is there any other/better way to read a single stack output from S3 back end?
e

echoing-dinner-19531

11/09/2022, 2:54 PM
Not at the moment. State is just one large .json file so you have to read and parse the whole file to get any bit out. I've been thinking of ways we could re-organize the way we store data on S3 to help with cases like this and some other state issues we have, but no concrete ideas yet.
c

cuddly-magician-97620

11/09/2022, 2:57 PM
State is just text, so it is not clear to me how the "limited bandwidth to S3" would make these updates so painfully slow...
e

echoing-dinner-19531

11/09/2022, 4:25 PM
Well its just text, but that's still data and for statefiles it's often megabytes of data. We've seen some users with slow uplinks to their S3 storage such that that is a noticeable delay to read. There might be other factors at play here and we're looking at adding more performance tracing to the engine to help answer questions like this, once that's all in we'd be happy to get tracefiles from users to show where real world performance issues are coming from.
17 Views