- ABP Framework version: v4.2.2
- UI type: Razor
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): yes
I am upgrading my application from Asp.Net ZERO with aspnetboilerplate to abp vNext, now some features have been migrated to abp vNext, but I found the razor page load slowly, the api also take more time than the Asp.Net ZERO done.
Generally, If any data needs to be bound to a razor page on the OnGetAsync method, the razor page will needs to more than 1 second to 5 seconds to render page (if more select controls data needs to be bound to the control), if no data needs to be bound to the select control on the OnGetAsync method or no enmuerated types to be bound, the razor page could be render and load to client less than 200 ms.
Also, compare to the Asp.Net ZERO, on the same server the Asp.Net ZERO application could load an API call with less than 200 ms per request, but the application with vNext an API request needs more the 900ms or 1 second to load data to the client.
Neither a razor page or an API request, if needs more than 1 second, the user will feel the application is slowly and cannot wait it anymore.
Is there a performance issue on the razor page load with tag helper and the HttpApi Controller with API application service?
Some screenshots compare Asp.Net ZERO application and the vNext application:
MVC page with lots of select control data load on the page, the request waiting time as below:
The remote API request, waiting time as below:
The vNext razor page with some select control data load on the page, the request waiting time as below:
The remote API request, waiting time as below:
It seems the HttpApi project spent some time cost to auto define the API controllers.
4 Answer(s)
-
0
Hi Could you share a simple project to reproduce the problem? thanks
-
0
Hi Could you share a simple project to reproduce the problem? thanks
Yes, Can I contact with you via QQ? Then I can send you my production application information
-
0
We need you to use a template project to reproduce this problem and provide full steps. thanks.
-
0
We are using Blazor WASM and it is much slower to load (many 10's of seconds)... Once the application is running it is OK.
This is our first SPA as we are migrating products from Aspnetzero Core/MVC... Apart from getting it up to the same level of functionality, we hope the framework loading gets faster.
