Agreed memory utilization of the server isn't something you can really optimize down and I wouldn't waste time on it beyond monitoring the extremes for your environment (IE alert >90%).
For memory, the component I would focus on is monitoring the individual JVMs heap sizes to see if they ever get close to hitting their heap size as that's an indicator of a potential problem and will impact user experience. When the free space in the heap gets low the garbage collection has to run more often and if it can't free up enough then it would heap dump and bring down your JVM which is never good.
CPU is more difficult. I try to look at over a prolonged period (IE over a 5 minute timespan) vs individual spikes. I also look at the load per CPU core because you could have a CPU core running at 100% constantly and the overall average would only represent that as 12.5% (with 8 cores). So you might be running at 30% overall for example but still have a problem because one process is under a high CPU load.
My starting point for CPU allocation is 2 for the OS (and other applications like antivirus) and 1 per JVM. So if you have 4 JVMs I would typically allocate 6 CPU cores by default. You having 8 cores with the RAM allocated means you're probably good with CPU allocations based on my starting point.
I'd start by looking to see utilization per core to see if you have high load on some of those cores. I'd also map the java processes with the highest CPU utilization to the JVM (IE MXMIF1/MXUI1) and review that for potential issues like hung threads, heap space issues, ensure thread pools are configured properly, etc. You could also look to take a java core of the JVM and analyze that if you want to see what's utilizing CPU time. It's possible that it's normal and every environment is different.
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Tue November 23, 2021 04:18 PM
From: Jason Verly
Subject: CPU/Memory Utilization for a "normal" Maximo server
We've had some new people come into our IT Support group and one of the new group managers installed some new monitoring software on all the servers. I'm now in a heated debate with IT Support on why I can't "fix" our Maximo servers and stop using 50-60% memory utilization and up to 80% CPU utilization.
I've been using Maximo for over 15 years and every server setup I've had ran the same way. I've tried to explain that the middleware is sometimes locking up resources to ensure the application has needed memory or CPU capacity when a user connects to Maximo. I know that's a bit simplified, but am I wrong that a Maximo server never really "powers down" when only a few people are logged in?
------------------------------
Jason Verly
Reliability Engineering Manager
Agropur US
Le Sueur MN
------------------------------
#AssetandFacilitiesManagement
#Maximo