CPU utilization tells you how busy the CPUs are right now, and load average tells you how many tasks are waiting for or running on the CPUs, on average, over the recent past. But they do not measure the same thing, and they do not always directly correlate to one another. These two often-checked metrics are sometimes conflated because both have to do with the CPUs and both may be high when a server is apparently overburdened.
What do they measure? CPU Utilization vs. Backgroundīefore we look at how to check and track CPU utilization and load average, let’s consider them conceptually. The two command-line utilities featured in this guide, uptime and top, are available by default on most Linux distributions. Use apt or dnf to install stress from your distribution’s repositories. The stress utility installed on your Droplet.Also read the guide How To Install the DigitalOcean Metrics Agent to learn how to enable Monitoring on your new Droplet or add the Monitoring Agent to an existing Droplet. Read our documentation if you don’t know how to create a Droplet. A two-core DigitalOcean Droplet with Monitoring enabled.To follow along with this guide, you need: Finally, we’ll look at how to track these metrics over time with DigitalOcean Monitoring and set an alerting policy so you can get notified by email or Slack when the metrics rise above their usual values.
We’ll explore the difference between these two metrics and then see how to check their values using two command-line utilities, uptime and top. We’ll start by understanding two of the most commonly referenced metrics of resource usage on any Linux server: CPU utilization and load average. This guide will help you find out whether that is the case for you.
How do you begin to investigate the problem? There are so many causes for a slow application, but sometimes it’s because your server’s CPUs are maxed out. Suppose your website or application is more sluggish than usual.
0 kommentar(er)
