Nice work guys.
Slightly off topic but I notice that in this release the azure picture service is using async calls however the calling function uses ".Result" which will in effect block and cause the call to be synchronous. All database access is also still synchronous.
So this release will speed things up by reducing the time spent in the http request cycle but I don't see it helping much with concurrent user load if you are using sql azure or if you store pictures in azure blob. Switching everything to async in my mind will provide much better performance and scalability benefits than just switching to .net core, you could also start using async viewcomponents as I imagine adding widgets is a big factor in slowing a site down.
https://news.ycombinator.com/item?id=13383016
Slightly off topic but I notice that in this release the azure picture service is using async calls however the calling function uses ".Result" which will in effect block and cause the call to be synchronous. All database access is also still synchronous.
So this release will speed things up by reducing the time spent in the http request cycle but I don't see it helping much with concurrent user load if you are using sql azure or if you store pictures in azure blob. Switching everything to async in my mind will provide much better performance and scalability benefits than just switching to .net core, you could also start using async viewcomponents as I imagine adding widgets is a big factor in slowing a site down.
https://news.ycombinator.com/item?id=13383016
Thanks a lot! Sure, we know about it. There's a separate work item for this task