Blazor Webassembly Speed issue

Question

Blazor Webassembly Speed issue

Kuldeep Y 41

Hello,
I Developed A Blazor web assembly application and deployed it on my local server machine using IIS Server. But only 30-50 Users login to application for do work, it goes its knees all pages stopped working. Processes stuck in mid and user logout automatically sometimes.
I want to speed up this application and make enough able to handle 100-200 user can use it at a time.

AgaveJoe 30,406 Reputation points

2023-06-22T10:55:14.4833333+00:00

By definition, Blazor WASM runs in the browser. Therefore Blazor WASM cannot be causing the "goes its knees" symptom. There must be some other issue like a memory leak in Web API.

Is there any way you can show us your code and explain the general design?
Anonymous

2023-06-23T01:46:20.48+00:00

Agree with AgaveJoe. Besides, whether your Blazor web assembly application is an Asp.net Hosted application (it contains Client, Server and a Shared project) or not? And try to debug the application use F12 developer tools or add logging, are there any exceptions and errors？
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
alicja 0 Reputation points

2023-06-26T11:35:03.7666667+00:00

thanks thisinformation

4 answers

Your answer

AgaveJoe 30,406 Reputation points

2023-06-22T10:55:14.4833333+00:00

By definition, Blazor WASM runs in the browser. Therefore Blazor WASM cannot be causing the "goes its knees" symptom. There must be some other issue like a memory leak in Web API.

Is there any way you can show us your code and explain the general design?
Anonymous

2023-06-23T01:46:20.48+00:00

Agree with AgaveJoe. Besides, whether your Blazor web assembly application is an Asp.net Hosted application (it contains Client, Server and a Shared project) or not? And try to debug the application use F12 developer tools or add logging, are there any exceptions and errors？
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
alicja 0 Reputation points

2023-06-26T11:35:03.7666667+00:00

thanks thisinformation

Answer 1

Kuldeep Y 41

Thanks for your response information are below : -

User's image

Here is my Blazor WASM project structure.

User's image

and i am including repository method Snapshot her
User's image

AgaveJoe 30,406 Reputation points

2023-06-26T15:18:11.8433333+00:00

The coding pattern does not look correct. There is a dependent MyDataSourceFactory member and what looks like a DbContext injected in the constructor then passed to the base class. Why are there two different data access objects in the same repository?

Does the repository have a finalizer? How are the base classes designed? Do the base classes manage lifetime as well?

Is there a compelling reason to manually manage the repository's lifetime? A typical ASP.NET Core approach is designing a service. The service lifetime is controlled by configuration.

There are other head scratchers like the use of DataSet. Maybe you are trying to integrate an existing data access layer?

In my opinion, there is enough code to question the general design approach. I assume the "it goes its knees" affect is due not properly managing object lifetime.

Answer 2

Kuldeep Y 41

User's image

In my application i have used Azure Active directory , Radzen UI etc.
and i am wondering at first run time it loading almost 230-250 dll at browser

Answer 3

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 4

Bruce (SqlWork.com) 81,971 Volunteer Moderator

that is the cost of blazor WASM, all the libraries must be loaded. but it generally only effect startup. if your blazor wasm app bogs down with user load, then its the server. use the browsers network support to see how long fetch/xhr requests are taking and if they are timing out or failing.

Kuldeep Y 41 Reputation points

2023-06-27T07:24:06.79+00:00

How i can improve it and make it faster.
Bruce (SqlWork.com) 81,971 Reputation points Volunteer Moderator

2023-06-27T15:36:46.8466667+00:00

first determine the slow requests (anything over 100ms). then profile the slow request to determine what makes them slow. maybe you have slow database calls, maybe you have blocking.

if database calls are slow (over 50 - 100ms), use the database performance tools.

if you are not capturing performance metrics, start there first.

Share via

Blazor Webassembly Speed issue

4 answers

Your answer