There are three main types of latency metrics for your Coder deployment:

- Dashboard-to-server latency:

The Coder UI measures round-trip time to the Coder server usingthe browser's Performance API.

The Coder UI measures round-trip time to the Coder serveror workspace proxyusingbuilt-in browser timing capabilities.

This appears in the user interface next to your username, showing how responsive the dashboard is.

- Workspace connection latency:

When users connect to workspaces, Coder measures and displays the latency between the user and:

- Workspace (direct P2P connection when possible)

- DERP relay servers (when P2P isn't possible)

This latency is visible in workspace cards and resource pages. It shows the round-trip time in milliseconds.

The latency shown on the workspace dashboard measures the round-trip time between the workspace agent and its DERP relay server.

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 would be a combination of dashboard-to-server latency plus this agent-to-relay latency.

- Database latency:

For administrators, Coder monitors and reports database query performance in the health dashboard.

To improve latency and user experience:

-**Deploy workspace proxies**: Place[proxies](./workspace-proxies.md) in regions closer to users.

-**Deploy workspace proxies**: Place[proxies](./workspace-proxies.md) in regions closer to users, connecting back to your single Coder server deployment.

-**Use P2P connections**: Ensure network configurations permit direct connections.

-**Regional deployments**:PlaceCoderservers inregions where most users work.

-**Strategic placement**:Deploy your singleCoderserver ina region where most users work.

-**Network configuration**: Optimize routing between users and workspaces.

-**Check firewall rules**: Ensure they don't block necessary Coder connections.