public static void UpdateRecord(Record record)
{
var form = record.GetForm();
using (var recordStorage = new RecordStorage())
{
recordStorage.DeleteRecord(record, form);
recordStorage.InsertRecord(record, form);
}
}
Checkout this link, as there might be many reason for CPU spikes :-
The main issue there was DFS replicating the giant licensing log file. However, once that was resolved, and after the HQ team provided some updated DLL's, submissions were still taking 12 or so seconds.
I am not sure if that's what you're seeing now, but should give you some historical perspective that similar issues have long been a problem. Sometimes, you can improve the situation.
You'd first want to track down the exact cause of the issue if you want to make any headway in resolving it.
Umbraco Form UpdateRecord Slow and spikes CPU
Using the above example to update a record field but it results in high CPU/memory spikes and timeouts. Is there any known issues with this?
Hello,
try, delete and insert like this :-
Checkout this link, as there might be many reason for CPU spikes :-
https://moriyama.co.uk/about-us/news/blog-fixing-umbraco-100-cpu-spikes-and-crashes/#:~:text=The three common reasons for, necessary and can be refactored.
Last time I checked (which, granted, was apparently 6 years ago), it was a known issue that, as far as I know, never got resolved (Contour is the old name for Umbraco Forms): https://our.umbraco.com/forum/umbraco-pro/contour/72902-contour-submissions-extremely-slow
The main issue there was DFS replicating the giant licensing log file. However, once that was resolved, and after the HQ team provided some updated DLL's, submissions were still taking 12 or so seconds.
I am not sure if that's what you're seeing now, but should give you some historical perspective that similar issues have long been a problem. Sometimes, you can improve the situation.
You'd first want to track down the exact cause of the issue if you want to make any headway in resolving it.
thanks for the response. I removed it as felt it was unreliable.
is working on a reply...