You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/content/docs/add-framework/test-profiles/_index.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,4 +35,5 @@ Data files are **mounted automatically** by the benchmark runner — your Docker
35
35
{{< card link="h2" title="HTTP/2" subtitle="Baseline and static file benchmarks over encrypted TLS connections with stream multiplexing." icon="globe-alt" >}}
36
36
{{< card link="h3" title="HTTP/3" subtitle="Baseline and static file benchmarks over QUIC for frameworks with native HTTP/3 support." icon="globe-alt" >}}
37
37
{{< card link="grpc" title="gRPC" subtitle="Unary RPC throughput over cleartext HTTP/2 using Protocol Buffers serialization." icon="globe-alt" >}}
WebSocket test profiles measure framework performance for real-time bidirectional communication. The server listens on **port 8080** and accepts WebSocket upgrade requests.
Measures WebSocket echo throughput. Each connection upgrades via HTTP/1.1, then sends text messages and receives echoes. Each echo counts as one completed response.
6
+
7
+
**Connections:** 512, 4,096, 16,384
8
+
**Pipeline:** 16 (messages in flight per connection)
9
+
10
+
## Workload
11
+
12
+
1. Open TCP connection to port 8080
13
+
2. Send HTTP/1.1 upgrade request to `/ws`
14
+
3. After receiving `101 Switching Protocols`, switch to WebSocket framing
15
+
4. Send text frames containing `"hello"`, receive echo frames
16
+
5. Measure messages per second
17
+
18
+
## What it measures
19
+
20
+
- WebSocket upgrade handshake performance
21
+
- WebSocket frame parsing and construction efficiency
0 commit comments