Skip to content

docs: add a section about latency and how it's measured #16734

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 3 commits into from
Apr 4, 2025
Merged

docs: add a section about latency and how it's measured #16734

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c09cedf
just latency section
EdwardAngert Apr 2, 2025
9e7dc7b
add multiple workspace proxies latency
EdwardAngert Apr 2, 2025
0497c0a
Update docs/admin/networking/index.md
EdwardAngert Apr 3, 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
Prev Previous commit
Update docs/admin/networking/index.md
  • Loading branch information
@EdwardAngert
EdwardAngert authored Apr 3, 2025
commit 0497c0afca5d80b053a4860d14b12f7107bf85c0
2 changes: 1 addition & 1 deletion docs/admin/networking/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,7 +215,7 @@ There are three main types of latency metrics for your Coder deployment:

This metric is displayed in milliseconds on the workspace dashboard and specifically shows the agent-to-relay latency, not direct P2P connections.

Total end-to-end latency experienced by a user is a combination of dashboard-to-server latency plus this agent-to-relay latency.
To estimate the total end-to-end latency experienced by a user, add the dashboard-to-server latency to this agent-to-relay latency.

- Database latency:

Expand Down