actix
Flagship · Rust · standard configuration · completeness 4/4
Actix-web 4 with rustls for TLS and mimalloc as the allocator. Default worker count, TCP_NODELAY enabled. actix-files serves static content from disk per request via try_compressed(), which selects a pre-compressed .br/.gz sibling by Accept-Encoding through the framework API (no hand-rolled suffix lookup). JSON is serialized per request with serde_json; on json-comp gzip (level 1) is driven in the handler, because actix-web's encoder sends every body over 1 KiB through the blocking pool, and the Compress middleware on that route serves any other encoding. async-db through a deadpool-postgres pool per worker (DATABASE_MAX_CONN split between the workers). fortunes rendered through an Askama template. json-tls and static-tls are served over HTTP/1.1-with-TLS on :8081; baseline-h2/static-h2 over h2 on :8443. Compiled with -O3 and thin LTO.
Achievements
🥇 3 Gold · 🥈 1 Silver · 🥉 3 Bronze. Top three of a field, taken in this entry's own league: the family composite, the same composite among entries written in the same language, and each test profile it is scored on. Every field is the one the badges publish, so a medal and a badge always say the same thing. How medals are awarded.
| Medal | Award | Field | Rank |
|---|---|---|---|
| 🥇 Gold | Test profile | Efficiency · Latency-10K | 1 of 85 |
| 🥇 Gold | Test profile | Efficiency · Latency-1M | 1 of 85 |
| 🥇 Gold | Test profile | Workload · JSON TLS | 1 of 82 |
| 🥈 Silver | Within its language | Rust · HTTP/2 | 2 of 7 |
| 🥉 Bronze | Within its language | Rust · HTTP/1.1 | 3 of 9 |
| 🥉 Bronze | Within its language | Rust · WebSocket | 3 of 7 |
| 🥉 Bronze | Test profile | WebSocket · Echo Pipelined | 3 of 27 |
Composite rank
Each profile of a family is worth 1,000 to the entry that leads it, and the composite is the sum over the family, less 2.5% for each of routing, middleware, request and response the entry does not do for you - its completeness factor, which the WebSocket and gRPC families do not carry. The field is this entry's own league: engines and reverse proxies are scored apart from frameworks. How it works.
Protocol compliance
The conformance suites this entry subscribes to, run against it on the benchmark machine: Http11Probe on HTTP/1.1, h2spec on HTTP/2, h3spec on HTTP/3 and Autobahn on WebSocket. A score, not part of the composite. How it works.
| Suite | Tool | Passed | Failed |
|---|---|---|---|
| HTTP/1.1 | http11probe d50d818 | 120 of 159 (75.5%) | 39 - the server crashed during the suite |
| HTTP/2 (actix-h2c) | h2spec 2.6.0 | 144 of 145 (99.3%) | 1 |
| WebSocket (actix-websocket) | autobahn-testsuite 25.10.1 | 105 of 244 (43.0%) | 139 |
HTTP/1.1: what failed
| Test | Expected | Got |
|---|---|---|
COMP-HOST-WITH-USERINFO Host header with userinfo (user@host) must be rejected (RFC 9112 §3.2, MUST) | 400 or close | 200, connection left open |
COMP-HOST-WITH-PATH Host header with path component must be rejected (RFC 9112 §3.2, MUST) | 400 or close | 200, connection left open |
COMP-ASTERISK-WITH-GET Asterisk-form (*) request-target with GET must be rejected (RFC 9112 §3.2.4, MUST) | 400, close, or timeout = warn | 404, connection left open |
COMP-OPTIONS-STAR OPTIONS * is the only valid asterisk-form request (RFC 9112 §3.2.4, MUST) | 2xx or 405; close/timeout = warn | 404, connection left open |
COMP-METHOD-CONNECT CONNECT to an origin server must be rejected (RFC 9110 §9.3.6, SHOULD) | 400/405/501 or close | 404, connection closed |
COMP-HOST-EMPTY-VALUE Empty Host header value must be rejected (RFC 9112 §3.2, MUST) | 400 or close | 200, connection left open |
SMUG-CHUNK-BARE-SEMICOLON Chunk size with bare semicolon and no extension name must be rejected (RFC 9112 §7.1.1, MUST) | 400 or close | 200, connection left open |
SMUG-CHUNK-EXT-INVALID-TOKEN Chunk extension with invalid token character must be rejected (RFC 9112 §7.1.1, MUST) | 400 or close | 200, connection left open |
SMUG-CHUNK-SIZE-TRAILING-OWS Chunk size with trailing whitespace before CRLF must be rejected (RFC 9112 §7.1, MUST) | 400 or close | 200, connection left open |
SMUG-CHUNK-LF-TRAILER Bare LF in chunked trailer termination — server MAY accept bare LF per RFC 9112 §2.2 (RFC 9112 §7.1, MAY) | 400 or 2xx | no response, timed out |
SMUG-MULTIPLE-HOST-COMMA Host header with comma-separated values must be rejected (RFC 9110 §7.2, MUST) | 400 or close | 200, connection left open |
MAL-LONG-HEADER-VALUE 100KB header value should be rejected with 431 (SHOULD) | 400/431 or close | 200, connection left open |
MAL-INCOMPLETE-REQUEST Partial HTTP request — request-line and headers but no final CRLF (NOTAPPLICABLE) | 400/close/timeout | 408, timed out |
MAL-EMPTY-REQUEST Zero bytes — TCP connection established without sending any data (NOTAPPLICABLE) | 400/close/timeout | 408, timed out |
MAL-LONG-METHOD 100KB method name should be rejected (SHOULD) | 400, 501 or close | no response, connection error (Failed to connect: Error) |
MAL-NON-ASCII-HEADER-NAME Non-ASCII bytes (UTF-8 ë) in header name must be rejected (MUST) | 400 or close | no response, connection error (Failed to connect: Error) |
MAL-NON-ASCII-URL Non-ASCII bytes (UTF-8 é) in URL must be rejected (MUST) | 400 or close | no response, connection error (Failed to connect: Error) |
MAL-CL-OVERFLOW Content-Length with integer overflow value must be rejected (MUST) | 400 or close | no response, connection error (Failed to connect: Error) |
MAL-WHITESPACE-ONLY-LINE Whitespace-only request line should be rejected or timeout (NOTAPPLICABLE) | 400/close/timeout | no response, connection error (Failed to connect: Error) |
MAL-NUL-IN-HEADER-VALUE NUL byte in header value should be rejected (MUST) | 400 or close | no response, connection error (Failed to connect: Error) |
MAL-CHUNK-SIZE-OVERFLOW Chunk size with integer overflow must be rejected (MUST) | 400 or close | no response, connection error (Failed to connect: Error) |
MAL-H2-PREFACE HTTP/2 connection preface sent to HTTP/1.1 server must be rejected (NOTAPPLICABLE) | 400/505/close/timeout | no response, connection error (Failed to connect: Error) |
MAL-CL-EMPTY Empty Content-Length value must be rejected (RFC 9110 §8.6, MUST) | 400 or close | no response, connection error (Failed to connect: Error) |
MAL-CL-TAB-BEFORE-VALUE Content-Length with tab as OWS — valid per RFC but unusual (RFC 9110 §5.5, MAY) | 400 or 2xx | no response, connection error (Failed to connect: Error) |
MAL-URL-BACKSLASH Backslash in URL path — not valid URI character, some servers normalize to / (SHOULD) | 400 or 2xx/404 | no response, connection error (Failed to connect: Error) |
MAL-URL-OVERLONG-UTF8 Overlong UTF-8 encoding of / (0xC0 0xAF) in URL must be rejected (MUST) | 400 or close | no response, connection error (Failed to connect: Error) |
MAL-URL-PERCENT-NULL Percent-encoded NUL byte (%00) in URL — security risk from null byte injection (NOTAPPLICABLE) | 400 or 2xx/404 | no response, connection error (Failed to connect: Error) |
MAL-URL-PERCENT-CRLF Percent-encoded CRLF (%0d%0a) in URL — header injection if server decodes during parsing (NOTAPPLICABLE) | 400 or 2xx/404 | no response, connection error (Failed to connect: Error) |
MAL-CHUNK-EXT-64K 64KB chunk extension — tests extension length limits (CVE-2023-39326 class) (NOTAPPLICABLE) | 400 or 2xx | no response, connection error (Failed to connect: Error) |
MAL-POST-CL-HUGE-NO-BODY POST with Content-Length: 999999999 but no body — tests timeout vs memory allocation (MUST) | 400/413/close/timeout | no response, connection error (Failed to connect: Error) |
NORM-UNDERSCORE-CL Underscore in Content-Length name — checks if server normalizes Content_Length to Content-Length (NOTAPPLICABLE) | Reject/drop (pass), normalize (fail), preserve (warn) | no response, connection error (Failed to connect: Error) |
NORM-SP-BEFORE-COLON-CL Space before colon in Content-Length — checks if server strips whitespace before colon (RFC 9112 §5, MUST) | Reject/drop (pass), normalize (fail), preserve (warn) | no response, connection error (Failed to connect: Error) |
NORM-TAB-IN-NAME Tab character in header name — checks if server normalizes Content\tLength to Content-Length (MUST) | Reject/drop (pass), normalize (fail), preserve (warn) | no response, connection error (Failed to connect: Error) |
NORM-UNDERSCORE-TE Underscore in Transfer-Encoding name — checks if server normalizes Transfer_Encoding to Transfer-Encoding (NOTAPPLICABLE) | Reject/drop (pass), normalize (fail), preserve (warn) | no response, connection error (Failed to connect: Error) |
WS-UPGRADE-POST WebSocket upgrade via POST must not be accepted (RFC 6455 §4.1, MUST) | !101 | no response, connection error (Failed to connect: Error) |
WS-UPGRADE-MISSING-CONN Upgrade header without Connection: Upgrade must not trigger protocol switch (RFC 9110 §7.8, MUST) | !101 | no response, connection error (Failed to connect: Error) |
WS-UPGRADE-UNKNOWN Upgrade to unknown protocol must not return 101 (RFC 9110 §7.8, MUST) | !101 | no response, connection error (Failed to connect: Error) |
WS-UPGRADE-INVALID-VER WebSocket upgrade with unsupported version — should return 426 (RFC 6455 §4.4, MUST) | non-101 (426 preferred) | no response, connection error (Failed to connect: Error) |
WS-UPGRADE-HTTP10 Upgrade header in HTTP/1.0 request must be ignored (RFC 9110 §7.8, MUST) | !101 | no response, connection error (Failed to connect: Error) |
HTTP/2: what failed
| Test | Expected | Got |
|---|---|---|
http2/3.5/2 Sends invalid connection preface | GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed | Error: unexpected EOF |
WebSocket: what failed
| Test | Expected | Got |
|---|---|---|
3.1 Send small text message with <b>RSV = 1</b>. | The connection is failed immediately (1002/protocol error), since RSV must be 0, when no extension defining RSV meaning has been negotiated. | Actual events match at least one expected. / close: The close code should have been 1002 or empty |
3.2 Send small text message, then send again with <b>RSV = 2</b>, then send Ping. | Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negotiated. The Pong is not received. | Actual events match at least one expected. / close: The close code should have been 1002 or empty |
3.3 Send small text message, then send again with <b>RSV = 3</b>, then send Ping. Octets are sent in frame-wise chops. Octets are sent in octet-wise chops. | Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negotiated. The Pong is not received. | Actual events match at least one expected. / close: The close code should have been 1002 or empty |
3.4 Send small text message, then send again with <b>RSV = 4</b>, then send Ping. Octets are sent in octet-wise chops. | Echo for first message is received, but then connection is failed immediately, since RSV must be 0, when no extension defining RSV meaning has been negotiated. The Pong is not received. | Actual events match at least one expected. / close: The close code should have been 1002 or empty |
3.5 Send small binary message with <b>RSV = 5</b>. | The connection is failed immediately, since RSV must be 0. | Actual events match at least one expected. / close: The close code should have been 1002 or empty |
3.6 Send Ping with <b>RSV = 6</b>. | The connection is failed immediately, since RSV must be 0. | Actual events match at least one expected. / close: The close code should have been 1002 or empty |
3.7 Send Close with <b>RSV = 7</b>. | The connection is failed immediately, since RSV must be 0. | Actual events match at least one expected. / close: The close code should have been 1002 or empty |
6.5.1 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0x68656c6c6f24776f726c64 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.5.2 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0x68656c6c6fc2a2776f726c64 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.5.3 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0x68656c6c6fe282ac776f726c64 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.5.4 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0x68656c6c6ff0a4ada2776f726c64 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.5.5 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1bdb9cf83cebcceb5 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xce | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.2 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xceba | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.4 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1bd | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.5 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1bdb9 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.6 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1bdb9cf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.7 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1bdb9cf83 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.8 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1bdb9cf83ce | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.9 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1bdb9cf83cebc | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.10 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1bdb9cf83cebcce | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.6.11 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xcebae1bdb9cf83cebcceb5 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.7.1 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0x00 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.7.2 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xc280 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.7.3 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xe0a080 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.7.4 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf0908080 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.8.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf888808080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.8.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfc8480808080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.9.1 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0x7f | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.9.2 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xdfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.9.3 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.9.4 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf48fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.10.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf7bfbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.10.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfbbfbfbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.10.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfdbfbfbfbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.11.1 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xed9fbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.11.2 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xee8080 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.11.3 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfbd | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.11.4 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf48fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.11.5 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf4908080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.12.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0x80 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.12.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.12.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0x80bf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.12.4 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0x80bf80 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.12.5 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0x80bf80bf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.12.6 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0x80bf80bf80 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.12.7 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0x80bf80bf80bf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.12.8 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0x808182838485868788898a8b8c8d8e8f909192939495969798999a9b9c9d9e9f... | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.13.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xc020c120c220c320c420c520c620c720c820c920ca20cb20cc20cd20ce20cf20... | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.13.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xe020e120e220e320e420e520e620e720e820e920ea20eb20ec20ed20ee20 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.13.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf020f120f220f320f420f520f620 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.13.4 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf820f920fa20 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.13.5 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfc20 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xc0 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xe080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf08080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.4 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf8808080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.5 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfc80808080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.6 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xdf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.7 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xefbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.8 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf7bfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.9 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfbbfbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.14.10 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfdbfbfbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.15.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xc0e080f08080f8808080fc80808080dfefbff7bfbffbbfbfbffdbfbfbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.16.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfe | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.16.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xff | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.16.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfefeffff | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.17.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xc0af | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.17.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xe080af | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.17.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf08080af | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.17.4 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf8808080af | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.17.5 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfc80808080af | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.18.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xc1bf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.18.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xe09fbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.18.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf08fbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.18.4 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf887bfbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.18.5 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfc83bfbfbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.19.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xc080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.19.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xe08080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.19.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf0808080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.19.4 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xf880808080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.19.5 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xfc8080808080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.20.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xeda080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.20.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedadbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.20.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedae80 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.20.4 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedafbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.20.5 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedb080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.20.6 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedbe80 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.20.7 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.21.1 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xeda080edb080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.21.2 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xeda080edbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.21.3 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedadbfedb080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.21.4 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedadbfedbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.21.5 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedae80edb080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.21.6 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedae80edbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.21.7 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedafbfedb080 | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.21.8 Send a text message with payload which is not valid UTF-8 in one fragment.<br><br>Payload: 0xedafbfedbfbf | The connection is failed immediately, since the payload is not valid UTF-8. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.1 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.2 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.3 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf09fbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.4 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf09fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.5 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf0afbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.6 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf0afbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.7 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf0bfbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.8 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf0bfbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.9 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf18fbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.10 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf18fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.11 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf19fbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.12 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf19fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.13 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf1afbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.14 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf1afbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.15 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf1bfbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.16 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf1bfbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.17 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf28fbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.18 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf28fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.19 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf29fbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.20 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf29fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.21 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf2afbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.22 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf2afbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.23 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf2bfbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.24 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf2bfbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.25 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf38fbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.26 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf38fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.27 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf39fbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.28 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf39fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.29 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf3afbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.30 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf3afbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.31 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf3bfbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.32 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf3bfbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.33 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf48fbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.22.34 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xf48fbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.23.1 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfb9 | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.23.2 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfba | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.23.3 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfbb | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.23.4 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfbc | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.23.5 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfbd | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.23.6 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfbe | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
6.23.7 Send a text message with payload which is valid UTF-8 in one fragment.<br><br>Payload: 0xefbfbf | The message is echo'ed back to us. | Actual events match at least one expected. / close: It is preferred that the server close the TCP connection |
Every result
Alpha Round, 31 runs. Requests per second is the best of three; latency, CPU and memory come from that run.
| Category | Profile | Conns | Req/sec | Avg | p99 | CPU | Memory |
|---|---|---|---|---|---|---|---|
| Connection | Baseline | 4,096 | 2,955,902 | 1.20ms | 2.39ms | 6311.4% | 371MiB |
| Connection | Pipelined | 4,096 | 18,907,788 | 3.08ms | 3.55ms | 6756.4% | 428MiB |
| Connection | Short-lived | 4,096 | 1,139,262 | 1.15ms | 9.27ms | 4400.5% | 278MiB |
| Concurrency | Async Delay | 32,000 | 1,998,958 | 14.42ms | 17.00ms | 4807.0% | 1.3GiB |
| Efficiency | Latency-10K | 1,024 | 9,983 | 69.5us | 105.0us | 25.4% | 360MiB |
| Efficiency | Latency-1M | 1,024 | 998,533 | 100.9us | 185.0us | 2731.9% | 294MiB |
| Efficiency | Latency-500K/8 | 1,024 | 445,089 | 1075424.1us | 2126848.0us | 793.9% | 83MiB |
| Workload | JSON Comp | 4,096 | 613,630 | 5.84ms | 24.60ms | 6341.9% | 609MiB |
| Workload | JSON Comp | 16,384 | 594,198 | 17.56ms | 35.10ms | 6562.2% | 910MiB |
| Workload | JSON TLS | 4,096 | 1,401,777 | 2.87ms | 58.23ms | 6274.9% | 429MiB |
| Workload | 8Gbit | 512 | 49,392 | 94.8us | 125.0us | 218.8% | 336MiB |
| Workload | Static TLS | 1,024 | 414,570 | 2.51ms | 31.64ms | 6303.9% | 2.6GiB |
| Database | Async DB | 1,024 | 320,231 | 2.73ms | 19.30ms | 3602.7% | 418MiB |
| Database | Fortunes | 1,024 | 267,328 | 2.31ms | 7.00ms | 5072.5% | 430MiB |
| HTTP/2 | Baseline | 256 | 6,427,519 | 3.82ms | 25.31ms | 6262.7% | 513MiB |
| HTTP/2 | Baseline | 1,024 | 4,836,173 | 19.84ms | 87.47ms | 6233.4% | 829MiB |
| HTTP/2 | Static | 256 | 419,801 | 19.31ms | 61.96ms | 6239.4% | 2.3GiB |
| HTTP/2 | Static | 1,024 | 404,445 | 77.57ms | 228.28ms | 6246.2% | 2.8GiB |
| HTTP/2 | Baseline (h2c) | 256 | 6,671,590 | 3.67ms | 16.15ms | 6418.6% | 578MiB |
| HTTP/2 | Baseline (h2c) | 1,024 | 4,961,422 | 20.15ms | 77.59ms | 6340.3% | 829MiB |
| HTTP/2 | Baseline (h2c) | 4,096 | 4,500,687 | 83.98ms | 210.21ms | 6176.9% | 2.6GiB |
| HTTP/2 | JSON (h2c) | 1,024 | 1,764,965 | 17.79ms | 48.72ms | 6566.7% | 584MiB |
| HTTP/2 | JSON (h2c) | 4,096 | 1,616,163 | 69.10ms | 320.17ms | 6244.4% | 1.3GiB |
| WebSocket | Echo | 512 | 3,646,407 | 139us | 249us | 6495.2% | 179MiB |
| WebSocket | Echo | 4,096 | 3,660,925 | 957us | 1.78ms | 6188.0% | 275MiB |
| WebSocket | Echo | 16,384 | 3,473,363 | 1.94ms | 6.13ms | 5920.3% | 449MiB |
| WebSocket | Echo Pipelined | 512 | 47,190,006 | 172us | 278us | 6715.6% | 184MiB |
| WebSocket | Echo Pipelined | 4,096 | 46,405,884 | 1.19ms | 4.05ms | 6235.8% | 283MiB |
| WebSocket | Echo Pipelined | 16,384 | 44,938,672 | 1.73ms | 4.65ms | 6151.7% | 341MiB |
| WebSocket | Echo Short-lived | 512 | 1,170,845 | 64us | 177us | 4419.1% | 173MiB |
| WebSocket | Echo Short-lived | 4,096 | 1,145,177 | 68us | 214us | 4314.1% | 178MiB |
Compared with
The Rust web frameworks around actix on the HTTP/1.1 composite, and the one leading them. Entries of other leagues are left out: a composite does not carry from one league to another. The last column shows every profile side by side.
| Entry | Composite | vs actix | |
|---|---|---|---|
| cpeak | 7187 | +14% | head to head |
| ntex | 6613 | +5% | head to head |
| tako | 6474 | +2% | head to head |
| trillium-tuned | 5820 | -8% | head to head |
| mq-bridge | 4109 | -35% | head to head |
Compare actix with any Rust entry · Compare actix with any entry, in any language · Every Rust entry, ranked
Results updated · How the benchmark is run · The machine · Add or fix an entry