This video demonstrates how to use SysTrack Health Visualizer and Resolve to identify systems experiencing CPU-related performance issues and determine whether the cause is application behavior, user activity, or hardware limitations.
Video Transcript
Today we are going to take a look at whether a system is being impacted by CPU. Now, there are a couple different ways to do that, and that's okay. It depends on how you're going to look at it.
Today, we're going to look at it from a high level. I want to see overall, for demonstration purposes, and then we're going to dig into a particular system. What I have pulled up here is our Desktop Visualizer, and we're looking at health. Something that SysTrack does is track all those different impacts for our users. So when we're looking at CPU impact, we're either looking at very high CPU utilization and/or a very high processor queue, which is going to impact that system. From the Health Visualizer, I can come in here and quickly find the systems that have CPU impact. You can see that I've already sorted the data, so I'm seeing a number of systems. This is over a longer period of time, so these are going to help surface some of those problem systems. We have several here. This one looks like we're doing some automations with a heavy workload, so we could probably understand that. But this system here is probably a user system, so let's go ahead and take a look at that one. What we're seeing here is that over the last 30 days, we've measured over 11 hours on average of impact. So I'm going to go ahead and drill into this system.
That's going to take us into Resolve. It's going to drill down into that system, and now I can start taking a look at it on a day-by-day basis. If they're impacted by CPU, what is it? Is it an application? Is it user behavior? Or is it both? Maybe the system needs to be upgraded or repurposed based on that user's job duties. This is where I always come when I'm looking at a particular system individually. I want to see this 30-day breakdown. I want to see what's happening. The reason I want to see that is because it may be something that's only happening on Thursday and Friday, or Monday and Tuesday. That would give you additional context that it's not necessarily an application issue, such as an upgraded application using significantly more CPU or a buggy application hanging and consuming resources. Instead, that might indicate a pattern in user behavior. Maybe on Thursdays and Fridays they're tasked with doing something that places additional demand on the CPU.
There is a whole lot more that we can dig into, but this allows you to determine whether a system is being impacted by CPU.