echoing-vase-56822
09/05/2021, 8:05 PMpulumi up --yes
without any changes takes around 2-5min, which is not acceptable. Im trying to debug the performance with pulumi up --tracing=file:./trace --yes
. The resulting file is 170mb in size. When using PULUMI_DEBUG_COMMANDS=1 pulumi view-trace trace
the UI is very bugy displaying all the traces. Then I tried docker run -d --name jaeger -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 -p 16686:16686 -p 9411:9411 jaegertracing/all-in-one:1.22
and pulumi up --yes --tracing=<http://localhost:9411/api/v1/spans>
but according to sudo tcpdump -i any port 9411
pulumi is not sending any traffic to port 9411 (curl localhost:9411
shows traffic).
1.) Whats wrong with http tracing?
2.) Is this performance expected?billowy-army-68599
09/05/2021, 9:30 PMechoing-vase-56822
09/05/2021, 11:39 PMhosts
file, which seem to have caused the tracing issues......
/pulumirpc.ResourceMonitor/RegisterResource
seems to be the performance issue in the gcp bucket backend.
There are some funky operations, but at least I have a starting point. Will also look into the hosted service😛-rocket:.high-answer-18213
09/06/2021, 9:17 AMcolossal-car-2729
09/06/2021, 11:19 AMImagePullBackOff
waiting issue. How about making timeouts for error configurable?
What are “feature-branch preview environment”?high-answer-18213
09/06/2021, 11:39 AMcolossal-car-2729
09/06/2021, 12:34 PMpulumi up
with no changes?
BTW Its also possible to split a stack up by e.g. pulumi.StackReference("someStack").getOutput("kubeconfig");
high-answer-18213
09/06/2021, 1:42 PMbillowy-army-68599
09/06/2021, 5:42 PMbusy-branch-95201
09/07/2021, 11:31 AMechoing-vase-56822
09/07/2021, 4:58 PMRegisterResource
calls on the bucket? AFAIK the open source backend deletes the stack.json during pulumi up
anyways and is not capable of parallel pulumi up
sbillowy-army-68599
09/07/2021, 6:28 PM