coder

mirror of https://github.com/coder/coder.git synced 2026-09-24 15:04:27 +08:00

Files

T

Spike Curtis 73253df6bf fix: use separate HTTP clients in scale test load generators (#21288 )

While scale testing, I noticed that our load generators send basically
all requests to a single Coderd instance.

e.g. 


![image.png](https://app.graphite.com/user-attachments/assets/e259862a-adf1-47e7-a37b-fd14e420058e.png)


This is because our scale test commands create all `Runner`s using the
same codersdk Client, which means they share an underlying HTTP client.
With HTTP/2 a single TCP session can multiplex many different HTTP
requests (including websockets). So, it creates a single TCP connection
to a single coderd, and then sends all the requests down the one TCP
connections.

This PR modifies the `exp scaletest` load generator commands to create
an independent HTTP client per `Runner`. This means that each runner
will create its own TCP connection. This should help spread the load and
make a more realistic test, because in a real deployment, scaled out
load will be coming over different TCP connections.

2025-12-19 12:22:49 +04:00

agentconn

chore: distinct operations for provisioner's 'parse', 'init', 'plan', 'apply', 'graph' (#21064 )

2025-12-15 11:26:41 -06:00

autostart

chore: distinct operations for provisioner's 'parse', 'init', 'plan', 'apply', 'graph' (#21064 )

2025-12-15 11:26:41 -06:00

createusers

refactor(scaletest): add runner for creating users (#19811 )

2025-09-22 17:35:36 +10:00

createworkspaces

chore: distinct operations for provisioner's 'parse', 'init', 'plan', 'apply', 'graph' (#21064 )