SCSM Console gets slower with each hardware asset I open
Ingrid_Glatz
Customer Adept IT Monkey ✭✭
when working with the Cireson Hardware assets nodes to check on different things, correct serial numbers to match computers, add remarks an so on, with each asset I open the console gets slower. After a while it takes up to 15-20 seconds for an asset form to open or for the console to refresh when setting new filters.
Right now, I have to close and re-open the console to have better response times. During a day, I might have to re-open the console up to 5-6 times which is a little bit annoying. Who has the same effect and maybe a solution?
Thanks
Ingrid
0
Best Answer
-
Brett_Moffett
Cireson PACE Super IT Monkey ✭✭✭✭✭
Check the History tab for the Asset and see if there are a LOT of updates for each time the connector or workflow runs.
This is a know issues with ECL (Entity Change List) table that it records EVERY time the connector runs and updates the record, even if it's just the "Last Updated Date".
With all these entries it can really add to the SQL transactions needed to open a record.
Within SCSM 2016 this can be disabled via a registry setting and will really help people control this Bloat!
If you are still running 2012, the other issue that can be causing this is a memory leak in the Console when it is set to full screen. It is a well known error that has been around since RTM and has never been fixed. Running the console in any mode other than full screen stops this issue, even if the screen is stretch to almost fill the screen.
Finally, 2016 has a memory leak issue if you run the console for too long. After several hours it will consume 90%+ of RAM and will need to be restarted.
To test, next time it slows down, look at the Task Manager on your PC and see what resources are being consumed.
Good luck!
I hope this answers your question5
Answers
This is a know issues with ECL (Entity Change List) table that it records EVERY time the connector runs and updates the record, even if it's just the "Last Updated Date".
With all these entries it can really add to the SQL transactions needed to open a record.
Within SCSM 2016 this can be disabled via a registry setting and will really help people control this Bloat!
If you are still running 2012, the other issue that can be causing this is a memory leak in the Console when it is set to full screen. It is a well known error that has been around since RTM and has never been fixed. Running the console in any mode other than full screen stops this issue, even if the screen is stretch to almost fill the screen.
Finally, 2016 has a memory leak issue if you run the console for too long. After several hours it will consume 90%+ of RAM and will need to be restarted.
To test, next time it slows down, look at the Task Manager on your PC and see what resources are being consumed.
Good luck!
I hope this answers your question
Thanks for the information.
Unfortunately, we'll be running SCSM 2012 still for quite a while. An update schedule is not planned yet. I thought the Memory leak with the console had been fixed with one of the lastest UR for SCSM. I'll give it a try to leave the console almost at full size to see whether this changes the behavior.