Chore: Publish modules benchmarking results from job scheduler refactor

[radeksimko]

Think about how we can automate the monitoring of a team SLA for performance.

CodeLens command good first test case.

Performance

• Line in the sand
  • Where are we now?
  • Where would we like to be?
• What is a normal config?
• What is a top end config?
• Create a public affirmation of performance guidelines SLA
• We have existing benchmarks via test suite.
• Cold vs Hot load
• Existing framework tests against stable, in development how do we test against latest.

Proposal

• assemble a hand-crafted list of modules from the Registry
  • hashicorp/terraform-aws-consul
  • hashicorp/terraform-aws-terraform-enterprise
  • https://registry.terraform.io/modules/terraform-aws-modules/vpc/aws/latest
• run initialize / initialized to trigger the directory hierarchy walk & parsing & discovery as per https://gist.github.com/radeksimko/aae53d1bb93e96dd524793113718da3f
• report total memory allocated (e.g. in bytes)
• report total CPU time spent (in seconds)
• set a benchmark for both memory usage and CPU time and document it in /docs publicly and/or link from Readme.md
• run nightly in GHA (input can be branch name)
• report violations of benchmark for either CPU or memory nightly into Slack
• (nice to have) render & store graphs of CPU / memory usage

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.