@[email protected] on X: "@m0sa Took me a minute, but here are performance numbers clients can feel: response times. Here's the median, 95th, and 99th percentile render times (full in to out time on a web server) for the API. Blue highlight is .NET Core:"
Took me a minute, but here are performance numbers clients can feel: response times. Here's the median, 95th, and 99th percentile render times (full in to out time on a web server) for the API. Blue highlight is .NET Core:
If you look really close, you can tell when @m0sa deployed the Stack Exchange API port to .NET Core earlier today. We're in final test phase (it's been in canary for a bit), and the plan is to merge tomorrow:
To clarify: that's memory usage. The earlier dips are rolling builds (see how quickly they ate way more memory) - this is consistently much better.
CPU was also already low...but now it's even lower. Same time period. We're now around 0.1% CPU on the box for the API.
Took me a minute, but here are performance numbers clients can feel: response times. Here's the median, 95th, and 99th percentile render times (full in to out time on a web server) for the API. Blue highlight is .NET Core:
That's across *all* API routes (some people hit us with brutal queries, so it varies), but you don't need to dig to see a very noticeable drop in response times across the board.
Anyway, yay - perf is a total side win. The maintenance and testing is where it's at here.
