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
WebSockets in Vert.X have high latency overhead compared to other backends:
One fix that can be applied is similar to #3393
This requires:
allowing a fast_path
handling standard_path with more efficient stream merging. Use fs2.Channel to perform the merge (more efficient than Stream#mergeHaltL / Stream#parJoin), just as in the mentioned PR.
This should be applied to the sttp.tapir.server.vertx.cats.streams.fs2.webSocketPipe function.
WebSockets in Vert.X have high latency overhead compared to other backends:
One fix that can be applied is similar to #3393
This requires:
Stream#mergeHaltL
/Stream#parJoin
), just as in the mentioned PR.This should be applied to the
sttp.tapir.server.vertx.cats.streams.fs2.webSocketPipe
function.Verification:
vertxServer3/Test/testOnly *VertxServerTest*
WebSocketSimulation
(See https://github.com/softwaremill/tapir/blob/master/perf-tests/README.md#testing-websockets)The text was updated successfully, but these errors were encountered: