How to tackle slow running scripts?

[Suggy]

There is a module to track the slow scripts OOB.  

Questions:

1. There are 1000s of records present in that table (sys_script_pattern). How should we evaluate them? Should we check all them? It would be tedious job. 

2. Lets say we have taken actions of few records, evaluated them and corrected them. But how to TRACK that corrective actions are taken in this table (sys_script_pattern)? 

I dont want repetitive work of evaluation to be done by others where I have already evaluated and taken actions!

[Robbie · Accepted solution]

Hi @Suggy,

As always, you have some great questions which gets the brain into gear. (Thanks - I think - Haha)

The key fields (that I use) on this table are:

- 'Average execution time (ms)'

- 'Execution count' (or Occurrences)

- 'Last sighted'

- 'First sighted'

- 'Source script'

- 'Tags'

You'll notice I highlighted the 'Tags' field. Leveraging the Out Of Box fields, this would be a key field and one at least where I have implemented tags which help 'manage' these slow scripts and 'track' what actions have been taken. Suggested tags could be 'Under review', ' Fix implemented' etc. I appreciate these are very high level and additional details would be useful.

Additionally you could create additional fields for you purpose for tracking.

This table is reviewed for ongoing monitoring and performance optimization.

To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.




Thanks, Robbie

[Suggy]

Thanks for your response @Robbie 

So I understand that there is no OOB capability/method to track it, we need to either create custom fields/use the tags.

[Robbie]

Hi @Suggy,

This table is the tracking of the slow transactions, but there is no further state or additional field that I see to manage the action taken against these. My recommendation is to use Tags or create a field.

To help others (and for me to gain recognition for my efforts), please mark this response correct by clicking on Accept as Solution and/or Kudos.




Thanks, Robbie