- Notifications
You must be signed in to change notification settings - Fork1k
docs: create WIP 10k scale doc#20213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Some nitpicks and typos.
The biggest feedback I have is the lack of intro to the testing methodology/assumptions at the top of the document.
| > utilization and adjust. | ||
| The 10,000 users architecture targets large-scale enterprises with globally-distributed development | ||
| teams in multiple geographic regions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
| teams in multiple geographic regions. | |
| teams. |
eitherglobally-distributedor multiple geaographic regions has to go.
| **Geographic Distribution**: For these tests we deploy on 3 Cloud-managed Kubernetes clusters in | ||
| different regions. | ||
| 1. USA - Primary (also contains the PostgreSQL database deployment). | ||
| 2. Europe - Workspace Proxies | ||
| 3. Asia - Workspace Proxies |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
| **Geographic Distribution**: For these tests we deploy on 3Cloud-managed Kubernetes clusters in | |
| differentregions. | |
| 1. USA - Primary(also containsthe PostgreSQL database deployment). | |
| 2. Europe - Workspace Proxies | |
| 3. Asia - Workspace Proxies | |
| **Geographic Distribution**: For these tests we deploy on 3cloud-managed Kubernetes clusters in | |
| the followingregions:" | |
| 1. USA - Primary- Coderd collocated withthe PostgreSQL database deployment. | |
| 2. Europe - Workspace Proxies | |
| 3. Asia - Workspace Proxies |
| **Footnotes**: | ||
| - Each provisioner handles a single concurrent build, so this configuration imples 200 concurrent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
| - Each provisioner handles a single concurrent build, so this configurationimples 200 concurrent | |
| - Each provisioner handles a single concurrent build, so this configurationimplies 200 concurrent |
| ### Workspaces | ||
| Thse numbers are for each of the 3 regions. We recommend that you use a separate node pool for user Workspaces. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
| Thse numbers are for each of the 3 regions. We recommend that you use a separate node pool for user Workspaces. | |
| These numbers are for each of the 3 regions. We recommend that you use a separate node pool for user Workspaces. |
| > recommendations. Use these recommendations as a starting point, but monitor your cluster resource | ||
| > utilization and adjust. | ||
| The 10,000 users architecture targets large-scale enterprises with globally-distributed development |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
I think it'd be nice to detail out the numbers we are expecting when we say 10k users - 600 concurrent builds, 6000 concurrent workspaces, etc.
| **Footnotes**: | ||
| - Assumed that a workspace user needs 2 GB memory to perform |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
How realistic is that 2 GB? That's the request for the workspace pod or both request and limit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Some nitpicks and typos.
The biggest feedback I have is the lack of intro to the testing methodology/assumptions at the top of the document.
Uh oh!
There was an error while loading.Please reload this page.
Adds a new document for our ongoing efforts achieving 10k user scale. The content is caveated as work in progress, but represents what we have tested so far.
closes:coder/internal#1025