Using HP Global Workload Manager with SAP

12
This definition places all the processes run by user c03adm into the workload we created and named
c03.sap.instance.
When we click OK, we’re returned to step 3 of the SRD creation wizard.
Click OK again, and in step 4 confirm the sizes and click OK. You may receive a warning about
compartment and policy max values not matching. You can ignore this, as our gWLM-provided policy
has a max 8, but we cannot achieve quite that amount while reserving 0.05 cores for the default fss
workload.
You’ve successfully created the SRD and are now placed in a screen that monitors the SRD resources.
Confirming process placement
To confirm that the correct processes are now being placed within the workload, use the ps
command to list all the processes in the workload:
root@cutst128:/tmp ps -fR c03.sap.instance
UID PID PPID C STIME TTY TIME COMMAND
c03adm 28090 28059 0 22:31:59 ? 0:00 se.sapC03_DVEBMGS00 -F
pf=/usr/sap/C03/SYS/profile/C03_DVEBMGS00_cutst128
c03adm 28095 28088 0 22:32:03 ? 0:05 dw.sapC03_DVEBMGS00
pf=/usr/sap/C03/SYS/profile/C03_DVEBMGS00_cutst128
c03adm 28094 28088 0 22:32:03 ? 0:00 icman -attach
pf=/usr/sap/C03/SYS/profile/C03_DVEBMGS00_cutst128
c03adm 28019 1 2 22:31:52 ? 0:20
/usr/sap/C03/SYS/exe/run/saposcol
c03adm 28088 28059 0 22:31:59 ? 0:01 dw.sapC03_DVEBMGS00
pf=/usr/sap/C03/SYS/profile/C03_DVEBMGS00_cutst128
c03adm 28106 28088 0 22:32:04 ? 0:00 dw.sapC03_DVEBMGS00
pf=/usr/sap/C03/SYS/profile/C03_DVEBMGS00_cutst128
...
Monitoring during stress
Force activity on the instance or on the other system workload to see the allocations change. The next
figure shows the SRD when the SAP instance is busy, but the cutst128.OTHER workload is not. The
activity results in a request of 1.6 cores beyond the 4 owned cores for the SAP instance. The request
is not fully met in that the c03.sap.instance workload gets 5.45 instead of 5.6 cores. The
cutst128.OTHER workload keeps 2.55 cores.