https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
i
@white-balloon-205 @tall-librarian-49374 do you need anything else? or should I post update in that issue
t
I haven’t looked at the trace but a significant part of this could be executing the whole 
azure_nextgen
module when you do a blank import. Is there a chance for you to try the same but with targeted imports like https://github.com/pulumi/examples/blob/master/azure-nextgen-ts-aci/index.ts#L5-L6 ?
i
removed all non-namespaced imports, waiting for trace
still very slow
w
Is this trace on a run that was doing verbose logging? What language is this? Anything notable about the structure of your program? Did this just start being slow on a stack that has been fast? Or has this always been slow for this stack?
FWIW - I see an ~1 min gap where nothing obvious is happening, but it's after a lot of logging has happened. This gap is between logging that all resource providers are configured (from the azure-nextgen provider I assume) and a call to GetRootResource (from the language host you are using I presume).
i
@white-balloon-205 that’s typescript, I’ve rewritten everything to not use non-namespaced import from azure-nextgen
it was always slow, it takes around ~30sec just to start showing some pulumi output in preview. “cold” start is very flow
I am not using verbose logging 🙂
btw, I’ve tested a lot today and it looks like it’s bumped to 30secs from 68secs just on preview, thanks @tall-librarian-49374. probably that’s namespacing
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by