I migrated my project from angularjs to angular.
Into angular application I saw bad performances for partial update data.
I have a pivot grid with 400.000 records, when I set the report I must wait some seconds after that I can see all report, but after a partial update data of 40.000 record I must wait for some minutes until pivot is ready.
In my old angularjs project the same operation took only a few seconds.
Thank you for writing to us.
So far, it is not exactly clear to us why there is such a big difference in performance between AngularJS & Angular.
Do you think you could do some profiling on your side to check whether the issue actually revolves around Flexmonster?
Alternatively, it would also be really helpful if you could provide us with a sample project together with a dummy data set with which the issue is reproducible.
Please let us know what you think.
attached you can find the example.
The file is structured in this way:
<HTML> : Pivot Markup with two buttons, “SetData” to fill the pivot and “UpdateData” to do partial update
<TS> : Pivot management
<Controller c#>: For the backend with two calls “Get” for button “SetData” and “Update” for the button “UpdateData”.
Let me know if you need more details, the limited upload size prevented me from uploading all solution.
Thank you for providing us with code snippets of your project – it allowed us to take a deeper look at this situation.
updateData() we’ve noticed there is virtually no difference in execution time, even though in both cases it did take a lot of time for the API calls to execute when testing on large data sets.
With that in mind, currently, we are not able to see how exactly Angular could be connected to the performance differences you’ve mentioned. Therefore, we wanted to ask whether you are certain about AngularJS working faster with the same data set & overall Flexmonster configurations. Understanding this will help us to move further with this question.
Thank you in advance and looking forward to hearing from you.
Hope you’re doing well.
We were wondering if you have any updates on this question since last week. Have you managed to get to the core of the issue, or does it persist?
We would be happy to hear your thoughts.
How are you?
Just checking in to ask whether this question is still relevant for you. Please let us know if there is anything else you would like to discuss related to this matter.