Why does cpu utility go high when we restart sas services?
With this little information it's only a guessing game.
What SAS services do you restart?
Which processes have high CPU utilization?
For how long is the CPU utilization elevated?
Have you check the logs for relevant services in your deployment?
Involve your infrastrucure team, they might be able to some signaling etc that is not visible to you.
The Java runtimes used by Tomcat (the web application server) eat a lot of CPU while the web apps are loaded (which can take half an hour, depending on how many apps you have and CPU performance).
In our case, when we restart the services, not only we respect an order but we monitor the CPU and wait till it goes back to an acceptable level before starting the next service. It takes about 25 min to complete.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.