linuxlab.io
Tutorials▾
  • Linux & networking
    File system, processes, TCP/IP, BGP and OSPF
    →
  • Terraform & IaC
    HCL, state, plan/apply on a LocalStack sandbox
    →
  • Git & GitHub
    Object model, plumbing, branching, GitHub Actions
    →
All tutorials →
PricingAboutSign inCreate account
/
  • Introduction
  • Lessons
  • How it works
  • Simulator
  • Knowledge base
  • Interview prep
Lessons
Footer
linuxlab-TutorialsPricingAboutPrivacy & cookies
Copyright © 2026 LinuxLab. All rights reserved.

← из прошлого урока

You saw individual processes: who is alive, how to send a signal. Now step back to the system level and ask, "does everyone have enough CPU?". Next come those three numbers in uptime that everyone quotes and almost nobody reads correctly.

← к прошлому уроку

Базовый

Load average: what the three numbers mean

12 мин · урок входит в курс «Базовый»

When you see three numbers like 0.45 0.30 0.18 in top or uptime, that is the load-average (LA). It is the most quoted and least understood indicator of system health. In this lesson you work out what they mean, how to read them against the CPU count, and why a high LA does not always mean the CPU is overloaded.

Урок закрыт

Чтобы запустить sandbox и пройти этот урок целиком, нужен соответствующий курс. Внутри - ещё много практических уроков того же уровня и сквозной прогресс.

Купить курсВойти← Все уроки

дальше →

System metrics are under control. Next you set up your own workspace: PATH, environment variables, aliases, and history. This is about not typing the same thing a hundred times.

Открыть превью: Environment and shell: PATH, variables, aliases, historyв курсе «Базовый» - /pricing
Footer
linuxlab-
Copyright © 2026 LinuxLab. All rights reserved.
Tutorials
Pricing
About
Privacy & cookies