we need to go with the recommendaton and standard set by RSA as per the planning guide.
few things to check:-
1. run the instance report from ACP and it will highlight the potential issue with current instance if any.
2. Are the database maintenance jobs as recommended by RSA in place?
3. Any network latency may cause the slowness within the organization.
You need to find the root cause first, adding extra cores will not help otherwise. E.g. look into resource monitor to find what process is eating resources and memory. Check ACP for potential running feed or job. Analyze Event logs and IIS logs.
Thank you IIya and Shubham.
During the slow performance, the server utilization never goes about 33% which I don't think is considered as heavy load for a webserver.
We have noticed that it is the IIS process that consumes 18% of the CPU during the issue. Also, we didn't observe any resource consuming feed or calculation. Moreover, this happens after every 2-3 months if the server isn't rebooted. If this is related to resource issue, then it should occur frequently like weekly basis.
We also opened a case with RSA, shared all the logs including windows event and archer framework with them. They are suggesting to add more CPU's which I don't think will resolve the problem in longer run.
Well, not much I can say about without root cause evidence. As you opened the case with RSA Support, then seek further with them.
If during the slow mode you have 33% of CPU utilization, you need to figure out what consumes it. Suggest to take together your IT Team and Network team, as might be due to the latency as well.
Another way is to drop the Web server as a culprit and take a look into SQL or Services server for the possible causes.
We did involve our database and network team. They didn't find anything unusual from their end. The utilization of services and database server hardly went up to 10% during the issue.
If it was due to network , it would have affected our other applications running in the same network. And this didn't happen.
Again, the issue gets resolved when we reboot just the web server which points ultimately to web server.
I would say that leads mainly to the IIS then. But you said that iisreset does not help, right?
In that scenario, how about cutting other processes 1 by 1 to see impact, like AV?
In case of many cores, it might also be that 1 core is fully utilized to 100%, but overall it would be seen only as XX% (let us say 30% in your case) of CPU.
Just wondering if there was a solution to this, we are experiencing the same issues on all 3 web servers. Its IIS Worker Process that is using up all the memory and seems to be foundation/Print.asp URL that is causing all the issues.
I also had a case open with RSA for the issue. After all the troubleshooting, we came to the conclusion that the problem is with in IIS. As per RSA and our investigation, the performance of IIS degrades after a month if the server is not rebooted. We are now rebooting the server after almost every 30 days, and we haven't faced this issue from a long time.