Examining load average
Examining load average
复制标题
DOI：
--
复制
发表时间：
2006-12
期刊：
影响因子：
--
通讯作者：
Rachel E. Walker
中科院分区：
文献类型：
--
作者：
Rachel E. Walker
许多 Linux 管理员和支持技术人员经常使用 top 实用程序来实时监控系统状态。在一些商店，当出现任何问题迹象时，通常会先检查顶部。在这种情况下，top 实际上成为机器健康状况的关键衡量指标。如果top看起来没问题，那么系统一定没有问题。 top 信息丰富——内存使用情况、内核状态、进程优先级、进程所有者等都可以从 top 获取。但是，这三个奇怪的负载平均值的目的是什么？它们到底想告诉我什么？要回答这些问题，需要对价值观的形成方式有直观且详细的了解。让我们从直觉开始。
Many Linux administrators and support technicians regularly use the top utility for real-time monitoring of their system state. In some shops, it is very typical to check top first when there is any sign of trouble. In that case, top becomes the de facto critical measurement of the machine's health. If top looks good, there must not be any system problems. top is rich with information—memory usage, kernel states, process priorities, process owner and so forth all can be obtained from top. But, what is the purpose of those three curious load averages, and what exactly are they trying to tell me? To answer those questions, an intuitive as well as a detailed understanding of how the values are formed are necessary. Let's start with intuition.