Document minimum system requirements

[EvanBoyle]

We don't currently document the minimum system requirements (RAM, etc) required to run Pulumi. Our Go SDK is a particularly hungry resource hog due to the number of types we generate for providers (a simple AWS program binary can be 100mb). We had a user run into an OOM error when trying to use the Go SDK. The issue turned out to be at the go run step, before any pulumi user code even executed. The user was using a 1GB VM to run pulumi. They saw inconsistent success with a 2GB VM, and consistent success with a 4GB VM. We should explore these limits and have a page with minimum system requirements. This may vary by language, and we should decide if we want to publish a single set of limits or break it down by runtime.

See thread for more details: https://pulumi-community.slack.com/archives/CCWP5TJ5U/p1592928208198100

[toriancrane]

Unable to see messages in Slack prior to 90 days and so I may be missing a bit of context. From what I can tell, there are currently some pages that document minimum system requirements such as the following:

• Self Hosting API Requirements
• Self Hosting Console Requirements
• Self Hosting Network Requirements

These documents seem to be focused on users that are self hosting their Pulumi Cloud environment (or at least that is the impression that I am getting). I wonder if it would be prudent to add a "minimum system requirements" on the Download & Install Pulumi page to address this?

[cnunciato]

Yep, we should totally write this and make it accessible from the installation guide.

[GeoffMillerAZ]

are the requirements known?

Or is part of this issue setting up a benchmarking test and then executing across each? Then just make a table or something that presents the recommendations?

If so, does this need to be integrated into some periodic process to re-evaluate benchmarks as the product evolves?

A blanket requirement was mentioned above, I could execute that as the simplest path and then address the runtime specific concern in the future. Please let me know what would be best and I'll take care of this.

[thoward]

Requirements are not known (by me). I would reach out to engineering and see if they have some numbers/stats to share. Otherwise, benchmarking/doing that research is part of the project.

[thoward]

Fixed in #13662