Skip to content

Commit 55e6c73

Browse files
committed
update latency info
1 parent 47f5d86 commit 55e6c73

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

docs/admin/networking/index.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -84,21 +84,21 @@ Coder measures and reports several types of latency, providing insights into the
8484
There are three main types of latency metrics for your Coder deployment:
8585

8686
- Dashboard-to-server latency:
87-
88-
The Coder UI measures round-trip time to the Coder server using the browser's Performance API.
89-
87+
88+
The Coder UI measures round-trip time to the Coder server or workspace proxy using built-in browser timing capabilities.
89+
9090
This appears in the user interface next to your username, showing how responsive the dashboard is.
9191

9292
- Workspace connection latency:
93-
94-
When users connect to workspaces, Coder measures and displays the latency between the user and:
95-
- Workspace (direct P2P connection when possible)
96-
- DERP relay servers (when P2P isn't possible)
9793

98-
This latency is visible in workspace cards and resource pages. It shows the round-trip time in milliseconds.
94+
The latency shown on the workspace dashboard measures the round-trip time between the workspace agent and its DERP relay server.
95+
96+
This metric is displayed in milliseconds on the workspace dashboard and specifically shows the agent-to-relay latency, not direct P2P connections.
97+
98+
Total end-to-end latency experienced by a user would be a combination of dashboard-to-server latency plus this agent-to-relay latency.
9999

100100
- Database latency:
101-
101+
102102
For administrators, Coder monitors and reports database query performance in the health dashboard.
103103

104104
### How latency is classified
@@ -127,9 +127,9 @@ Latency measurements are color-coded in the dashboard:
127127

128128
To improve latency and user experience:
129129

130-
- **Deploy workspace proxies**: Place [proxies](./workspace-proxies.md) in regions closer to users.
130+
- **Deploy workspace proxies**: Place [proxies](./workspace-proxies.md) in regions closer to users, connecting back to your single Coder server deployment.
131131
- **Use P2P connections**: Ensure network configurations permit direct connections.
132-
- **Regional deployments**: Place Coder servers in regions where most users work.
132+
- **Strategic placement**: Deploy your single Coder server in a region where most users work.
133133
- **Network configuration**: Optimize routing between users and workspaces.
134134
- **Check firewall rules**: Ensure they don't block necessary Coder connections.
135135

0 commit comments

Comments
 (0)