STOR-5552: Preserve in-flight WebSocket auto-responses - #7065
STOR-5552: Preserve in-flight WebSocket auto-responses#7065apeacock1991 wants to merge 1 commit into
Conversation
|
LGTM |
1ea082e to
73922e6
Compare
Merging this PR will improve performance by 9.11%
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ⚡ | request[RegExpBenchmark] |
4.5 ms | 4.1 ms | +9.58% |
| ⚡ | simpleStringBody[Response] |
24.3 µs | 22.4 µs | +8.65% |
Tip
Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.
Comparing apeacock/STOR-5552 (6454b32) with main (5ef8a1f)2
Footnotes
-
129 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
-
No successful run was found on
main(7739c5e) during the generation of this report, so 5ef8a1f was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩
Track auto-response sends in the hibernation manager so revived WebSockets wait before writing. Queue completion alongside pending responses and retain the message buffer independently of the legacy adapter. Cover direct, queued, packaged, cancellation, and repeated-revival paths.
73922e6 to
6454b32
Compare
Track auto-response sends in the hibernation manager so revived WebSockets wait before writing.
Queue completion alongside pending responses and retain the message buffer independently of the legacy adapter. Cover direct, queued, packaged, cancellation, and repeated-revival paths.