Skip to content

Commit b6b55a2

Browse files
authored
[CI] Minor updates to premerge/cluster-management.md (#437)
Typos, and update the current autoscaling limit for the cluster.
1 parent 86c0411 commit b6b55a2

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

premerge/cluster-management.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Yes, it's called `prototype`, but that's the production cluster.
4040
We should rename it at some point.
4141

4242
To add a VM to the cluster, the VM has to come from a `pool`. A `pool` is
43-
a group of nodes withing a cluster that all have the same configuration.
43+
a group of nodes within a cluster that all have the same configuration.
4444

4545
For example:
4646
A pool can say it contains at most 10 nodes, each using the `c2d-highcpu-32`
@@ -53,7 +53,7 @@ will see 3 node pools:
5353
- llvm-premerge-linux-service
5454
- llvm-premerge-windows
5555

56-
Definitions for each pool is in [Architecture overview](architecture.md).
56+
Definitions for each pool are in [Architecture overview](architecture.md).
5757

5858
If you click on a pool, example `llvm-premerge-linux`, you will see one
5959
instance group, and maybe several nodes.
@@ -64,8 +64,8 @@ a basic cluster, we have a single instance group per pool.
6464

6565
Then, we have the nodes. If you are looking at the panel during off hours,
6666
you might see no nodes at all: when no presubmit is running, no VM is on.
67-
If you are looking at the panel at peak time, you should see 4 instances.
68-
(Today, autoscale is capped at 4 instances).
67+
If you are looking at the panel at peak time, you should see 8 instances.
68+
(Today, autoscale is capped at 8 instances).
6969

7070
If you click on a node, you'll see the CPU usage, memory usage, and can access
7171
the logs for each instance.

0 commit comments

Comments
 (0)