Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just wondering whether it's "normal" for Solaris' "Common
Agent Container" and some other basic java processes that
come with the OS for whatever reason to consume ~ 20%
CPU just running by themselves.
Most of our Midrange systems are running on Linux, I was
hired for my Linux skills, but find myself looking after
several Solaris machines as well while I'm on-call. And
they're costing me lots of sleep with alerts for high CPU
usage (when apps kick in, e.g. Oracle or Sun LDAP Directory
have actual load) the machines easily sit on 95-100%
CPU for extended periods of time - I get alerted after
6 consecutive 5 minute intervals over 95%.
I'm wondering whether there's a way to stop Solaris
from "playing with itself". If I could eliminate those
20% base load for cvm (and the xVM Ops Centre agent)
I could get away w/o being woken every so often. Our
in-house Solaris resource seems to be happy w/ the
status quo, I'm not. Which is why I'm asking here ;D
We don't use any Veritas software on our Solaris kit any more, so I can't really comment on the xVM stuff. 20% CPU time sounds pretty suspect though.
The Common Agent (cacao) stuff shouldn't be using noticeable CPU time. I'd check the logs at:
/var/cacao/instances/*/logs/*
for weirdness.
Could you post a prstat run so we can see what's chewing on the CPUs? Might be worth running a 'truss -p <pid>' to see what the troublesome processes are up to as well.
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
I guess xVM was confused with VXVM, quite different beasts ...
My first move would be to figure out what the busy processes are doing during these peak periods. Useful tools would be "prstat -L" to identify the threads consuming the CPU and then repeat "pstack and/or jstack" at regular intervals to identify what code is called. "dtrace" might also help there.
Not quite sure whether any of this is normal or to be expected, as I
have nothing to compare it to. :} I thought that the line in red was
a bit suspicious.
Not quite sure whether any of this is normal or to be expected, as I
have nothing to compare it to. :} I thought that the line in red was
a bit suspicious.
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
Hi Tinkster. There is nothing really suspicious in your stats. Is the CPU load mostly in userland or in the kernel ? Please try what I suggested (prstat then [p/j]stack) instead of directly suspecting system calls.
Hi Tinkster. There is nothing really suspicious in your stats. Is the CPU load mostly in userland or in the kernel ? Please try what I suggested (prstat then [p/j]stack) instead of directly suspecting system calls.
OK, I picked out the two busiest LWPs (busy at the time,
and very high in over-all CPU time).
Userspace has roughly double the CPU usage of Kernel,
e.g. 30% idle, 45% User, 25% Kernel
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.