You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some of the items on the list will certainly be useful in Oqtane - others not so much because they only support static application scenarios. One of the items I did want to call out because it is more significant than people may realize:
"Performance Improvements - For .NET 5, we made significant improvements to Blazor WebAssembly runtime performance with a specific focus on complex UI rendering and JSON serialization. In our performance tests, Blazor WebAssembly in .NET 5 is two to three times faster for most scenarios."
Note that Microsoft has identified this as a Blazor WebAssembly specific improvement, but it is not. Oqtane is architected in a client/server manner - so whether you are running on Blazor WebAssembly or Blazor Server, the framework is interacting over HTTP services between the Client application and the Server application. In earlier versions of Blazor there was some criticism expressed about application performance. This was not actually due to Blazor itself, but rather due to the new .NET Core System.Text.Json library which is used for serializing/deserializing objects when interacting over HTTP. In .NET 5 Microsoft optimized this library - resulting in a 2-3X improvement in speed. So essentially this means that Oqtane should be 200-300% faster whether you are running on Blazor WebAssembly or Blazor Server on .NET 5.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am sure many of you have already read the Blazor release notes for .NET 5:
https://docs.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-5.0?view=aspnetcore-5.0#blazor
Some of the items on the list will certainly be useful in Oqtane - others not so much because they only support static application scenarios. One of the items I did want to call out because it is more significant than people may realize:
"Performance Improvements - For .NET 5, we made significant improvements to Blazor WebAssembly runtime performance with a specific focus on complex UI rendering and JSON serialization. In our performance tests, Blazor WebAssembly in .NET 5 is two to three times faster for most scenarios."
Note that Microsoft has identified this as a Blazor WebAssembly specific improvement, but it is not. Oqtane is architected in a client/server manner - so whether you are running on Blazor WebAssembly or Blazor Server, the framework is interacting over HTTP services between the Client application and the Server application. In earlier versions of Blazor there was some criticism expressed about application performance. This was not actually due to Blazor itself, but rather due to the new .NET Core System.Text.Json library which is used for serializing/deserializing objects when interacting over HTTP. In .NET 5 Microsoft optimized this library - resulting in a 2-3X improvement in speed. So essentially this means that Oqtane should be 200-300% faster whether you are running on Blazor WebAssembly or Blazor Server on .NET 5.
Beta Was this translation helpful? Give feedback.
All reactions