Web Site unresponsive after saving
Simon_Zeinhofer
Customer Ninja IT Monkey ✭✭✭✭
In our environment, we have an issue when we are saving something in the console into a management pack or import a new one.
The Cireson Site is unresponsive for about 30 seconds then and the IIS goes up and consumes a lot of CPU and RAM. As soon as it "calms down" everything works fine again.
I guess there was a community post about this issue, that the scsm console got unresponsie for an amount of time, because the health service has to publish the xml to all other management servers - but imo this does not explain the spike in the IIS service and the unresponsiveness of the portal.
Before we went productive it was hanging for about 5 seconds after saving at most - but now it is from 30 seconds to 1 minute.
So for us as admins it is pretty much impossible to change/save our stuff during the day, as everyone complains about the "slow IT portal".
Is this a normal behaviour? If yes, what leads to this?
Best Answer
-
Justin_Workman
Cireson Support Super IT Monkey ✭✭✭✭✭
@Simon_Zeinhofer - Yes this is normal behavior. When a user connects to SCSM (even if it's via the portal) a cache object is created on the server. When a management pack is changed, each one of those cache objects gets updated. This is what causes the spike in activity for the web process. There's not a way around this other than adjusting management packs outside of heavy traffic times.
0
Answers
@Simon_Zeinhofer - Yes this is normal behavior. When a user connects to SCSM (even if it's via the portal) a cache object is created on the server. When a management pack is changed, each one of those cache objects gets updated. This is what causes the spike in activity for the web process. There's not a way around this other than adjusting management packs outside of heavy traffic times.
@Justin_Workman Thank you very much for the explanation :)
Things like these help us understand the fundamentals much more :)