Skip to content

Update Cloud IPs.md #1154

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 2, 2023
Merged

Update Cloud IPs.md #1154

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e06453f
Update 200 Cloud IPs.md
Vmihajlovic Apr 28, 2023
2e98bc4
delete doubled word
MattDodsonEnglish Apr 28, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion src/data/markdown/docs/03 cloud/07 Cloud reference/200 Cloud IPs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,12 +59,16 @@ The tier k6 chooses depends on the number of VUs allocated to a load zone.
- Tier 2 when the load zone has 1000-4001 VUs
- Tier 3 when the load zone has 4001-5000 VUs

Tier 1 instances can host up to 300 VUs
Tier 2 instances can host up to 1200 VUs
Tier 3 instances can host up to 5000 VUs

Regardless of the tier, the amount of resources (CPU, Memory, Network) per VU is the same.
For example, if you start a test with 400VUs, k6 uses 1 Tier 1 server,
meaning that the traffic generated from our service comes from 1 IP.

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


## Buy static IPs
Expand Down