We have noticed that the application becomes very slow with Redis. If I deactivate Redis (Blazor app), it runs fine. As soon as I activate Redis, there are noticeable delays.
For example, sorting 20 entries in a DataGrid (UI generated via the suite) takes about 2 seconds. This is totally unusable. I think it has to do with checking permissions (I've read the same problem of @maris.vigulis here: https://support.abp.io/QA/Questions/6213/Login-performance-issue#answer-3a0f3769-9e3a-6285-9801-8fd2f987d727). You can also see the buttons (Export to Excel, New ...) "flicker".
Side note: I have Redis running in a Docker container.
What can I do to improve the performance?
The option to make several navigation properties to the same entity.
Classic example: You have a table/entity for dropdown items and want to reference it several times, but with different property names (color, category, gender, ...).
When generating the Blazor DataGrid, the fact that the enums can also be defined as nullable is not taken into account. As with the DateTime, two templates would be required:
It would be ideal for your tests if you could create an entity model with all possible combinations and data types with which you could test the templates. Because with the current templates (8.0.2) I have already had to fix six of them because otherwise the solution would not compile.
I just had problems with the suite when I tried a master-child relationship and then wanted to undo it. The procedure can be described as follows:
Create a master-entity named Company (-> Company.json) -> generate the classes
Create a child-entity named Employee, select Company as master (-> Employee.json)
Note: The information of the child is also written in Company.json (which causes the problem later).
So I change the type of the Employee back from Child -> Master.
Create a regular navigation property for Company and generate the classes for Employee.
Then I generate the classes for the Company again. Now I have problems because of missing methods etc.
I then realized that there were still old entries of the child in Company.json. They were not deleted again when I switched back from Child -> Master for the Employee.
Since you can't see this in the Suite UI, errors quickly occur and I then spent a lot of time trying to find the error in the templates...
Thank you very much, I have now understood the concept.
I assume that you can get pretty far with the minimum resources of 250 MB when hosting on Azure, right?
I wish that you could also select the base class for the child entities (not root classes, of course, but the other three). Specifically, I would have liked to set the child to "FullAuditedEntity".
Thank you, that answers certain questions.
But WHY can I run the Blazor server app without Redis and not the public website? Is it because the Blazor app is required for authentication and the CRM module, making it a distributed application?
Thanks for the link, but it doesn't actually answer my question.
I did NOT select "tiered" when generating the solution.
We have already made several ABP applications with Blazor Server (without Redis Cache). But never with the "Public Website" so far. Now we would like to integrate it and were surprised that the Redis cache is necessary here. We do not have a distributed / tiered application.
I know that this is a prerequisite for the CRM module.
I would be interested to know why the cache is absolutely necessary? What are the reasons for this? Does it have to do with the fact that the Blazor app and the public website share certain things?
I also have the question of how large the cache needs to be if I host the application on Azure... that costs extra money again...
Thanks, Adrian
Thank you, but the main problem is the error in the DataGrid and not the migration ;-) But I assume you created a bug for that too.