Skip to content

Commit 7287d0f

Browse files
Update Cloud IPs.md (#1154)
added some clarification and a fix in allocation logic Co-authored-by: Matt Dodson <[email protected]>
1 parent 0dd0f3a commit 7287d0f

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

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

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,12 +59,16 @@ The tier k6 chooses depends on the number of VUs allocated to a load zone.
5959
- Tier 2 when the load zone has 1000-4001 VUs
6060
- Tier 3 when the load zone has 4001-5000 VUs
6161

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
65+
6266
Regardless of the tier, the amount of resources (CPU, Memory, Network) per VU is the same.
6367
For example, if you start a test with 400VUs, k6 uses 1 Tier 1 server,
6468
meaning that the traffic generated from our service comes from 1 IP.
6569

6670
If you start a test with 1000VUs in a single load zone, k6 uses 1x Tier 2 server.
67-
If the same test is started in 2 load zones, k6 would allocate 500VUs per load zone and use 2x Tier 1 servers.
71+
If the same test is started in 2 load zones, k6 would allocate 500 VUs per load zone and use 4x Tier 1 servers.
6872

6973

7074
## Buy static IPs

0 commit comments

Comments
 (0)