search

lthibault / quic-mangos

A QUIC transport for mangos (scalability protocols) written in pure Go
Apache License 2.0
24 stars 2 forks source link

benchmark ? #1

Open ghost opened 6 years ago

ghost commented 6 years ago

I read an in-depth review of QUIC versus tcp and they found in general its only quicker for edge cases. I cant remember the URL unfortunately.

For simple gets it was slower because tcp runs in the kernel an QUIC does not and so in kernel stuff gets scheduled earlier.

SO it would be really interesting if you even get to the point of benchmarking this against tcp. Also webrtc. I think there is a decent webrtc. https://github.com/keroserene/go-webrtc This one is VERY up to date, so should work.

lthibault commented 6 years ago

Did you ever find that URL?

I believe the edge-cases in question are related to reconnects and network-changes (e.g. changing from wifi to 4g on a phone). Nevertheless, the advantages to QUIC are not limited to performance. Native stream multiplexing is a huge convenience in many cases.

More to your point, a benchmark would be most welcome. Is that something you'd be willing to tackle?

ghost commented 6 years ago

i am hard pressed on time right now. Deadlnes and no sleep.

Will try to remember to get it when i am awake....

Benchmarks. Same again. No freaking time right now...

egorsmkv commented 5 years ago

Link #7