I've done some cursory profiling, it seems like improvements are centered on collections + strings manipulation (and I suspect the transport layer but it's harder to estimate because IIS relies on the native http.sys)
Prikaži ovu nit
We're in the middle of migrating one of our biggest apps (5000+ servers) to .net core. In yellow is CPU usage for .net framework + http://asp.net . In green is .net core 3.1 + aspnetcore. We've migrated other apps but it's the first time we see such a dramatic improvementpic.twitter.com/Ka6zg4Zjds
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
5000+ servers ? Wow that's a web app or batch processing or else ? I'm curious how you manage this
-
Web app. Currently Windows + .net framework + IIS. Planning to migrate to Linux (Mesos) + .net core by the end of the year.
- Još 9 drugih odgovora
Novi razgovor -
-
-
When you say migrate, what code was changed? Was it just enough to work with the core libraries or were other changes made beyond that? I’m trying to get a good picture of what conversion means in this case.
-
It's hard to tell. Migrating our SDK to netcore took us more than a year but that's because we started with netcore 1.0 (compatibility wasn't even remotely as good as today). Plus, we have a custom toolchain for build, which made the conversion much harder
- Još 1 odgovor
Novi razgovor -
-
-
looks like a multi million savings on the next hw renewal, impressive! Is it also same QPS and memory usage?
-
Interestingly we couldn't increase the QPS at first (the app would start behaving erratically at >40% CPU), but we identified and fixed the bottleneck. It's now CPU-bound and performs well up to 80% of charge. I haven't checked the memory usage.
- Još 2 druga odgovora
Novi razgovor -
-
-
5000 servers?! What is this? How many CPU cores?
-
32 logical cores per server (16 hyperthreaded)
- Još 6 drugih odgovora
Novi razgovor -
-
-
at constant latency?
-
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.