DRAFT: I'd like feedback on this approach for 1k before I give the others the same treatment and add a 10k document.

• Bumps database requirements to 8 vCPU, 30 GB memory. In our testing database was nearly always the bottleneck. (This could come back down again with improvements to how we use it.)

• Removes specific machine type recommendations.

  • This only applies to VM-based deployments and many of our customers use Kubernetes.
  • The major clouds upgrade their machine teirs, so our recommendations go out of date
  • In its place we just give CPU and memory requirements

• Removes API requests per second

  • It's not a metric that many operators will know until they are already operating
  • Our API requests vary wildly in cost depending on what they are
  • Replaces them with Users | Running Workspaces | Concurrent Builds - which represents our scale testing scenarios, and are easier for operators to reason about.

• Removes specific advice about workspace sizing, instead gives the minimum specs for the agent

• Gives Kubernetes resource request/limits in notes

• Adds advice about not needing high performance disks for Coderd, but that provisioners will benefit.