All in all it takes about 5-6 minutes just for a p...
# pulumi-deploymentsa
ambitious-air-92938
11/01/2023, 10:33 AMAll in all it takes about 5-6 minutes just for a preview to complete, whereas the same op started locally takes about 30s in total
l
lemon-agent-27707
11/01/2023, 5:57 PMWhat language are you using, and do you have policy as code configured?
a
ambitious-air-92938
11/01/2023, 5:57 PMUsing Go, and no policy as code
ambitious-air-92938
11/01/2023, 5:58 PMI've tried in different stacks in the same project and the same happens with all I've tried
ambitious-air-92938
11/01/2023, 6:00 PMThe "View Live" link that's provided at the start of the preview just shows a spinner in the preview pane for about 3.5 to 4 minutes on average before the preview run begins proper
l
lemon-agent-27707
11/01/2023, 6:02 PMI would guess that this is due to a recent regression in memory consumption in the compile step which we're working on fixing: https://github.com/pulumi/pulumi/issues/14344
When you run a preview, the first thing that happens is
go run main.goa
ambitious-air-92938
11/01/2023, 6:04 PMInteresting. Yeah, the behaviour I'm seeing is only when triggering via a Deployment. Triggering from a local run or via GHA starts up much faster.
ambitious-air-92938
11/01/2023, 6:06 PMI ran a trace profile when triggering a preview from a local CLI call and, end-to-end, the preview returns consistently in around 30s
l
lemon-agent-27707
11/01/2023, 10:49 PMAre you using default GitHub Actions runners (8GB RAM)? Is it the exact same repo/project you are comparing? An older project that hadn't updated to more recent provider SDKs would not see these problems. But in theory, the same code on GHA and Deployments with the same memory and same version of dependencies should have the same performance characteristics.
a
ambitious-air-92938
11/02/2023, 12:21 PMYes, default GHA runners, exact same repo/project (and even the exact same changes).
e
enough-garden-22763
11/02/2023, 3:57 PMThis is a really curious difference, I'm sorry you're experiencing that. There might be a few factors in play but I am wondering if GHA's support for build caching is making a big difference here.
enough-garden-22763
11/02/2023, 3:59 PMIf you're using something like actions/setup-go as we do [internally](https://github.com/pulumi/pulumi-aws/actions/runs/6712451436/job/18242044336#step:5:47) one of the benefits is that it preserves go compilation cache across build runs. This can make a substantial difference for Pulumi Go programs as we have a significant dependency set, and recompiling it from scratch does add up.
a
ambitious-air-92938
11/02/2023, 4:12 PMWe are indeed using
actions/setup-goambitious-air-92938
11/02/2023, 4:14 PMWell, a bit longer than 30s, but not enough to account for the difference, unless maybe if Deployments is pulling every package, then compiles, it might add up.
e
enough-garden-22763
11/02/2023, 4:18 PMI've cleaned up
enough-garden-22763
11/02/2023, 4:18 PMWhich commands do you use to clean up?
enough-garden-22763
11/02/2023, 4:18 PM Copy code
go clean -modcache && go clean -cache # perhapsenough-garden-22763
11/02/2023, 4:19 PMIt's quite possible that my guess is off and something else is in play though, as you point out. Very interesting to understand this so we can improve deployments.
l
lemon-agent-27707
11/02/2023, 8:59 PMI would guess that the specs on your local environment are beefier than the VM running the deployment/GHA. Running a build in a docker container constrained to a single cpu and 8gb of RAM allocated would likely produce closer results.