Hello @Matt,
have you already came across the "SAS® 9.4 Web Applications: Tuning for Performance and Scalability, Third Edition" https://support.sas.com/documentation/cdl/en/appsrvtuning/69859/HTML/default/viewer.htm#titlepage.ht... ?
You should probably start from this chapter Initial Sizing and Tuning Configuration Options for Deployments and build up from there, with help of the whole document.
This guide includes every tuning tip that is official from SAS. All of the tips are based on 3 default sizing ( Small, Medium and Large). This being said, a few other tips I can give you:
- Regarding Xms-Xmx-XX:PermSize-XX:MaxPermSize settings of the JVMs, I would advise to stick always to the recommendations from SAS and the selected sizing. Perhaps you can extend a bit the Xms but O would not touch the others. Anyway, if you have never done this before, please align first with SAS Technical Support. Reason: BIgger or smaller limits on JVM might help performance, but you need to be careful, it cal also degrade it A LOT doe to times on setting JVM memory or GC-garbage collection time.
- Sometimes, the SASServer1_1 requires additional memory, if you have enabled the Auditing framwork, because of the audit collection done on WIP. If there is too much data, and no enough Heap size on your JVM, the SASServer1_1 might collapse or take forever to start. If this happens, you can either extend the heap size (Xms, which is not infinite) or clean your audit data ( http://support.sas.com/kb/58/599.html ).
- SAS Environment Manager is a great tool to analyse the performance of your middle-tier/ Why? Because it keeps track of every single factor of your JVMs. Set and keep an eye of your monitors on EVM, and you will understand much better what is going on behind the scenes.
In short:
- Have a good overview of your deployment and what loads your environment
- Monitor its load with SAS Environment Manager and keeping an eye on WIP audit tables.
- Align with SAS Technical Support for changes on your environment's JVM settings.
