User-343630552 posted
I have a c# personal finance WinForms app that I have been trying to convert to Blazor Wasm. A financial forecast is calculated each time the user changes a variable in their plan. The calculations entail looping through a series of years and
invoking in each iteration a number of methods in a set of 25-35 objects (depending on the user's forecast specs) that calculate the individual variables of the forecast. Once started, the exact same calculation code runs in the WinForms and Blazor apps.
I am seeing a ~20 fold degradation in performance under Blazor (e.g. a complex forecast takes 350ms in WinForms and 7000ms in Blazor). Does that level of degradation make sense? Is a big part of it inherent to running within a browser?
Is Blazor Wasm a big part of it? Are there any ways to significantly reduce it?
I am using VS Community 2019 v 16.8.2 to run AspNetCore 5.0 with Chrome
86.0.4240.198.