I would be very interested to hear any feedback on this issue my self!
I find it very strange that nobody can comment on them other than “its jus Blazor and abp is bringing lot to the table” so this is just normal.
There is nothing normal about this load time at all!
Btw I would think about using static web application and CDN to distribute your app! We got our loading time from 50-60 sek (!!) to 10-15 sek after compression finally worked.
Compression did only work in version 6.0…1.5 years after Blazor WASM was released…
Tks, Sturla. Will also try your suggestions.
Did you encounter those errors what I mentioned above in your implementation?
It seems, as far as I could decipher, that all the idle times are coming from the errors bellow. After each error there is an ~ 10 sec of idle time, then resumes, then another error, another 10 seconds, then finally website loads.
More exactly when it tries to do this:
I don't understand what is happening. API is working perfectly fine.
I have the same error on local dev machine, minus the idle time between them.
What is ABP trying to do? I am using standard Blazor wasm template.
https://github.com/abpframework/abp/issues/13114
See also this, the last week comment. We have the sane situation.
Already did that.
Has nothing to do with idle times. There are literally seconds where nothing happens and it's related to the internals of ABP as I couldn't reproduce this with any other Blazor app.
Please provide some guidance as I can't use the app like this in prod.
Hello!
The application loads very slow. But what's perplexing are these idle times:
There's no such thing with a standard MS Blazor WASM template.
We have 21 seconds of idle time by using the ABP Blazor wasm template.
Our app is in production and its unusable with that kind of performance, which has nothing to do with Blazor as a framework.
Did you guys made some deployments in different environment to test the performance?
How can we solve this?
Thank you very much.
Hi @ccernat, We are sorry for the late response.
First of all, please delete this github repository. Your nuget api key is exposed there https://github.com/RelevanceRo/TestChatModule/blob/master/NuGet.Config
This is not allowed.Why the public website is an MVC Razor pages app if the template is Blazor wasm? Is it planned to update the ABP Suite to generate the public website with the same tech stack as the back-end app?
Blazor wasm is for single-page backend applications and not suitable for public websites.
ABP Suite should have an options to disable SaaS / Tenancy from the UI. The SaaS / Tenancy is really a small niche of application developed with ABP Framework.
We may consider disabling multi-tenancy on project creation. I'll create an issue about that.
Why after I disable multitenancy I still get in the Administration menu SaaS / Tenant sections? How can I actually remove completely those sections from the administration menu?
You have to remove the Saas module from the solution (csproj & module.cs files).
We'll reply the question related with Chat module in a short time.
My bad. Repo deleted.
Tks for noticing.
Hello!
Unfortunately no tutorial or documentation really helped to actually implement the chat module in a Blazor wasm app, so please don't send me to documentation or the latest tutorial in APB Community.
Can the Support Team provide a sample Blazor wasm app template with a Blazor public website in which the chat module is actually working in a non-multitenant environment?
The chat module should be enabled by default. There's no need to actually enable chat for a tenant if I am not using multitenancy. Nor SaaS editions, etc.
Steps I did:
Create a Blazor WASM app from ABP Suite, LeptonX theme, ver. 6.0.1, non-tiered.
Went into *.Domain.Shared and disable multitenancy.
From ABP Suite added Chat module as package.
Opened the solution and tried to run and got errors to AbpBundlingOptions. You can see them if you reproduce the steps.
Solved errors, created an user. As its a non multi-tenant environment, I can't assign chat permissions.
Opened the blazor website, opened the public website: no chat icon.
This is the solution as it was generated by ABP Suite and after added the chat module as packaged:
https://github.com/RelevanceRo/TestChatModule.git
Please help me understand how to implement the Chat Module in a full blazor environment with no SaaS / multitenancy.
PS:
A few suggestions and questions:
Why the public website is an MVC Razor pages app if the template is Blazor wasm? Is it planned to update the ABP Suite to generate the public website with the same tech stack as the back-end app?
ABP Suite should have an options to disable SaaS / Tenancy from the UI. The SaaS / Tenancy is really a small niche of application developed with ABP Framework.
Why after I disable multitenancy I still get in the Administration menu SaaS / Tenant sections? How can I actually remove completely those sections from the administration menu?
Works perfectly!
Tks alot.
PS. The problem was indeed the placement of the survey.jquery.min.js!
Hello again!
Someone help, please? :)
Tks.
Hello!
I have a public blazor wasm app ( which is basically a copy of the default blazor project generated by the Suite ) and the default blazor backoffice app generated by the ABP Suite.
The environment is non-multitenant, so multitenancy is set to false.
In the chat module documentation there's no mention of how you can operate in a non-multitenant environment.
I have some questions / help requests related to the Chat Module:
Tks alot and thank you for all the hard work! Amazing product!
Catalin
