Skip to content

Commit 5dc729f

Browse files
authored
Update 200 Cloud IPs.md (#1300)
Clarify the number of IPs needed per instance and fix formatting
1 parent 25052b9 commit 5dc729f

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

src/data/markdown/docs/03 cloud/07 Cloud reference/200 Cloud IPs.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -55,13 +55,17 @@ If your tests have specific requirements, contact k6 support for a custom soluti
5555
k6 has 3 tiers of hardware for load generation.
5656
The tier k6 chooses depends on the number of VUs allocated to a load zone.
5757

58+
First step is to determine the number of VUs per load zone.
59+
5860
- Tier 1 when the load zone has 1-999 VUs
5961
- Tier 2 when the load zone has 1000-4001 VUs
6062
- Tier 3 when the load zone has 4001-5000 VUs
6163

62-
Tier 1 instances can host up to 300 VUs
63-
Tier 2 instances can host up to 1200 VUs
64-
Tier 3 instances can host up to 5000 VUs
64+
Second step is to determine the number of VUs per instance.
65+
66+
- Tier 1 instances can host up to 300 VUs
67+
- Tier 2 instances can host up to 1200 VUs
68+
- Tier 3 instances can host up to 5000 VUs
6569

6670
Regardless of the tier, the amount of resources (CPU, Memory, Network) per VU is the same.
6771
For example, if you start a test with 400VUs, k6 uses 1 Tier 1 server,

0 commit comments

Comments
 (0)