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
I have a hunch that a such thing happens because Http2::accept needs to wait for a stream buffer provided by the user instead of creating one as soon a header frame is received. Or maybe not, there needs to be more investigation/profiling.
https://github.com/LesnyRumcajs/grpc_bench showed that
wtx
generally performs well but some requests, specially in the 99% area, end up having higher latencies.I have a hunch that a such thing happens because
Http2::accept
needs to wait for a stream buffer provided by the user instead of creating one as soon a header frame is received. Or maybe not, there needs to be more investigation/profiling.wtx
project LesnyRumcajs/grpc_bench#473 (comment)The text was updated successfully, but these errors were encountered: