This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Does anyone understand pulumi memory/CPU usage? I am trying to figure out how to scale my API that creates pulumi stacks on different cloud providers. I see that for each stack the memory and cpu usage is different. Curious how pulumi cloud handles the load from many clients. I had sequential execution of stacks via API but it's too slow for my needs. So I added logic to handle multiple requests in parallel, but now cpu/memory explodes and I need to think about server capacity or some limits on how many to allow in parallel. So, another approach I am considering is to have a queue for pulumi stack requests and maybe create a job per request where each job will have some standard cpu/memory profile.