Ask the Community
Groups
How to diagnose high kernel (CPU) times - Connect IT Community | Kaseya
<main> <article class="userContent"> <p><strong>Problem</strong></p> <p>You have noticed that your Kaseya VSA server's CPU <strong>Kernel Time</strong> (noted in RED) is taking up much of the resources.</p> <p><img src="/attachments/token/vux1vZGbfghBwX5DpxwQUzYpJ/?name=Kernel.jpg" alt="Kernel.jpg" class="embedImage-img importedEmbed-img"></img></p> <p> </p> <p><strong>Cause</strong></p> <p>This can be happening for a number of different reasons:</p> <ol><li>Malfunctioning or buggy device driver - network/disk, etc.</li> <li>Management of the file system - especially when there are directories with extremely large number of files in them, and/or may sub-directories</li> <li>Act of aggressive memory management - especially if there are several "log lived" processes that have allocated HUGE working sets and are competing</li> <li>Related to #1, 2 and 3 above - Anti-virus software's driver which hook the file-system and intercept / scan file as they are modified</li> <li>If the Operating System is Virtual, and the host of over-subscribed in terms of memory or CPU resources</li> <li>VERY HIGH network activity</li> <li>Very frequent access / update of registry</li> <li>VERY high rate of MSMQ messages</li> </ol><p> </p> <p><strong>Solution</strong></p> <p>Run through the items in the <strong>Causes</strong> section above to determine if you can isolate the issue. </p> <p>In one case, (based on item #4 above) <strong>Trend Micro</strong> was installed on the VSA which was causing the high kernel times as you see in the screenshot above. Disabling the <strong>TrendMicro</strong> product and services didn't help however after uninstalling <strong>TrendMicro</strong> from the VSA and rebooting system was functioning normal and resulted in the performance below:</p> <p><img src="/attachments/token/ek8JzJWuZpabtCNRYxEZKC0QY/?name=perf.jpg" alt="perf.jpg" class="embedImage-img importedEmbed-img"></img></p> </article> </main>