Kestrelhttpserver: Switch back to libuv as the default transport
@muratg
halter73
All 5 comments
馃槥
davidfowl
on 14 Dec 2017
why?
tmds
on 14 Dec 2017
cc @DamianEdwards
muratg
on 14 Dec 2017
We're concerned about the performance of the socket transport relative to the libuv transport.
halter73
on 14 Dec 2017
The goal is still to make the socket transport the default once we reach our performance goals (~parity or greater with the libuv transport in all measured scenarios). If we don't meet the goals for 2.1, we'll still release the sockets transport in 2.1 as an option for customers to use.
DamianEdwards
on 19 Jan 2018
👍5
Was this page helpful?
0 / 5 - 0 ratings
Related issues
felschr
路
6Comments
Tazer
路
4Comments
M-Curtis
路
3Comments
txdv
路
7Comments
pathcore-tasos
路
5Comments
Most helpful comment
The goal is still to make the socket transport the default once we reach our performance goals (~parity or greater with the libuv transport in all measured scenarios). If we don't meet the goals for 2.1, we'll still release the sockets transport in 2.1 as an option for customers to use.