You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deleting a match with a scorecard timed out consistently, but removing the scores and then deleting the remaining match didn't. Removing the scores was slow but worked (as it usually is), and removing the match was fast.
This suggests that smaller, faster operations might be the answer to SQL timeouts and slow performance. Slow scorecard saves are likely down to updating the statistics table. Perhaps relationships should be removed from the statistics table so that records can be removed later from there, after a delete has taken place.
The text was updated successfully, but these errors were encountered:
SQL profiler showed that comfortably the slowest part of saving match scorecards was updating probability. Changed the probability calculation to remove that update entirely. Profiler now shows every part of the save at <10ms locally, yet it still feels slow in production.
Deleting a match with a scorecard timed out consistently, but removing the scores and then deleting the remaining match didn't. Removing the scores was slow but worked (as it usually is), and removing the match was fast.
This suggests that smaller, faster operations might be the answer to SQL timeouts and slow performance. Slow scorecard saves are likely down to updating the statistics table. Perhaps relationships should be removed from the statistics table so that records can be removed later from there, after a delete has taken place.
The text was updated successfully, but these errors were encountered: