#Fasthttp alt that supports h2

17 messages · Page 1 of 1 (latest)

iron walrus
#

why do u need it "as fast"?

near wharf
#

H2 muxing adds some overhead

#

it also read head blocking issues

#

you just can't get H2 as good as extremely optimised H1

#

decoding the request could be better since it's more format binary but the body most likely not

twilit tendon
twilit tendon
near wharf
# twilit tendon Will keep that in mind thanks for the tip

I think I oversold the thing, you could get H2 extremely close to H1, it's just that if you want ultra high performance http either you have H3 which does not have many problems H2 have, or you have H1 which is compatible with everything, easier to optimise (since you can make it a small shim over TCP)

#

so becasicaly the incentives are for H1 or H3, that why less very optimised H2 implementations exists

twilit tendon
#

What about echo though? is it worth trying? A friend recommended it to me but i don't really find anything useful about it online for some reason

short onyx
#

if you want performance, there's no substitute for actually measuring the thing you're trying to do

#

people focus too much on the abstract choice of frameworks

and not enough on the fundamentals of "am I programming in a basically efficient way"

twilit tendon
#

And it's also not how i handle the http connection and requests because i already analyzed that too, its just that net/http isnt enough

iron walrus
#

i'm curious, i've never seen a net/http bottleneck, could you show your analysis?

twilit tendon