Skip to content
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

Update max browser runtime #1201

Merged
merged 3 commits into from
Feb 26, 2025
Merged

Update max browser runtime #1201

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
adbec31
update max browser runtime
Dnhem Jan 29, 2025
b81f4e1
update browser max runtime
Dnhem Jan 29, 2025
ede616a
Merge branch 'main' into update-max-browser-runtime
Dnhem Feb 26, 2025
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
4 changes: 2 additions & 2 deletions site/content/docs/private-locations/scaling-and-redundancy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,8 +51,8 @@ the location and their frequency. API checks can be scheduled as frequently as e
frequently as every 1 minute.

Based on your configuration, you should be able to estimate how many checks will run per minute in your Private Location.
API checks have a maximum running time of 30 seconds, Browser checks 2 minutes. This means that in the worst case scenario,
a checkly agent with a `JOB_CONCURRENCY` of 1 can run two API checks per minute, or 1 Browser checks per 2 minutes.
API checks have a maximum running time of 30 seconds, Browser checks 4 minutes. This means that in the worst case scenario,
a checkly agent with a `JOB_CONCURRENCY` of 1 can run two API checks per minute, or 1 Browser check per 4 minutes.
In an average configuration this will be higher and API checks are generally faster than Browser checks.

Once you have an idea of how many checks will be running and you know the per-agent `JOB_CONCURRENCY` limit based on the
Expand Down
Loading