Long delay in Blazor after saving model and the page updating. #2472
Unanswered
adrianwright109
asked this question in
Questions
Replies: 1 comment 1 reply
-
Seems to be spending a lot of time (1200 times - gave up counting after that!!) in the below method on the Blazor component for (IsDirty, IsSavable etc) after the save has completed and before Saved event is invoked:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a
BusinessBase
editable object which has 16 properties on it that are updated from the Blazor UI.When I save the object using
Clsa.Blazor.ViewModel.SaveAsync()
method it saves as expected in a timing manner.The
SaveAsync()
implementation inCsla.Blazor.ViewModel
has these 2 lines:In my example it takes over 4.5 minutes from the
DoSaveAsync()
call for theSaved
action to be invoked. I'm not sure why this is happening?I have a theory that it might be data related...
So I lied... my business editable object has 2 additional properties to maintain a 2 different lists of string. Only holds database field names and the other holds a list of unique record keys.
The reason for this is that we have a legacy stored procedure to call just after updating the repository with the updated editable object. This SP takes in a comma separated list of database field names and a comma separated list of unique record IDs.
I'm my scenario I have a list of 16 database field names and a list of 714 record IDs.
These 2 properties have been implemented using a
BusinessListBase
parent list withBusinessBase
children. This allows for us to add items to the list in the UI prior to saving.It seems to me that the 4.5 minutes is spent checking the model include these 2 properties to see what model values have changed.
Should I be using a more lightweight approach as these lists don't have any business rules; they are purely there to store the values so we can send them as a comma separated list to the stored procedure?
The parent list class:
The parent list child item class:
Beta Was this translation helpful? Give feedback.
All reactions