@@ -117,7 +117,7 @@ under ten instances, and opt for vertical scale over horizontal scale after
117
117
meeting availability requirements.
118
118
119
119
Coder's
120
- [validated architectures](../../admin/infrastructure/validated-architectures.md)
120
+ [validated architectures](../../admin/infrastructure/validated-architectures/index .md)
121
121
give specific sizing recommendations for various user scales. These are a useful
122
122
starting point, but very few deployments will remain stable at a predetermined
123
123
user level over the long term, so monitoring and adjusting of resources is
@@ -197,7 +197,7 @@ a virtual machine (VM), you can deploy multiple provisioner daemons, ensuring
197
197
each has a unique `CODER_CACHE_DIRECTORY` value.
198
198
199
199
Coder's
200
- [validated architectures](../../admin/infrastructure/validated-architectures.md)
200
+ [validated architectures](../../admin/infrastructure/validated-architectures/index .md)
201
201
give specific sizing recommendations for various user scales. Since the
202
202
complexity of builds varies significantly depending on the workspace template,
203
203
consider this a starting point. Monitor queue times and build times to adjust
@@ -219,7 +219,7 @@ must also be low-latency with respect to one another.
219
219
220
220
Prefer scaling PostgreSQL vertically rather than horizontally for best
221
221
performance. Coder's
222
- [validated architectures](../../admin/infrastructure/validated-architectures.md)
222
+ [validated architectures](../../admin/infrastructure/validated-architectures/index .md)
223
223
give specific sizing recommendations for various user scales.
224
224
225
225
# # Workspace proxies
0 commit comments