billions-xylophone-85957
08/02/2021, 6:36 PMup
? We're using an s3 backend and every change to a rather simple stack (3 stack references, 92 resources) takes 7-8 minutes on 5mbps upload/160ms latency to S3pulumi up
as far as I can tell is limited by the upload/download speed (nothing could be done about the e.g. cloud providers APIs perf) and local IO to some extent.billowy-army-68599
08/02/2021, 6:51 PMbillions-xylophone-85957
08/02/2021, 6:52 PMstack size * number of resources
? Even if the API call is a read?Duration: 4m9s
$ fgrep -c 'Appended new state snapshot to be written' log.txt
92
$ fgrep -c 'Saved stack' log.txt
13
$ fgrep 'SnapshotManager: mustWrite' log.txt | awk '{print $NF}' | uniq
false
same
mustWrite
checks return false, but there were at least 13 stack writes nonethelessI0802 20:03:43.882189 389878 snapshot.go:130] SnapshotManager: Beginning mutation for step `same` on resource `urn:foobar`
I0802 20:03:43.882207 389878 step_executor.go:327] StepExecutor worker(0): applying step same on urn:foobar
(preview false)
I0802 20:03:43.882224 389878 snapshot.go:266] SnapshotManager: sameSnapshotMutation.End(..., true)
I0802 20:03:43.882244 389878 snapshot.go:513] Marked old state snapshot as done: urn:foobar
I0802 20:03:43.882253 389878 snapshot.go:522] Appended new state snapshot to be written: urn:foobar
I0802 20:03:43.882270 389878 snapshot.go:258] SnapshotManager: mustWrite() false
I0802 20:03:43.882280 389878 snapshot.go:288] SnapshotManager: sameSnapshotMutation.End() eliding write
I0802 20:03:43.882290 389878 step_executor.go:327] StepExecutor worker(0): step same on urn:foobar retired
billowy-army-68599
08/02/2021, 8:52 PM