Linux performance / Intermediate: mechanism and scoped diagnosis

Linux performance β€” Intermediate: mechanism and scoped diagnosis

Connect perf, scheduling, pressure, writeback, managed budgets, and application waits.

6 lessons Β· No account required

What you will learn

  • Interpret bounded counter and controller evidence.
  • Correlate application and Linux observations without weakening correctness.

  1. Use perf counters to test CPU hypotheses

    Choose scoped events, interpret counter ratios, and recognize hardware and permission limits before profiling an application.

    Start learning

  2. Find scheduling and synchronization delay

    Distinguish runnable waiting, blocked synchronization, oversubscription, and affinity constraints before changing scheduling policy.

    Start learning

  3. Diagnose memory pressure and OOM boundaries

    Use PSI, reclaim activity, cgroup events, and application evidence to distinguish expensive pressure from harmless occupancy.

    Start learning

  4. Trace writeback and filesystem delay

    Relate dirty memory, filesystem metadata, durability boundaries, and block queues without sacrificing correctness for apparent speed.

    Start learning

  5. Read effective cgroup and systemd budgets

    Explain how hierarchical resource policy can create latency while the host still appears to have spare capacity.

    Start learning

  6. Connect Linux evidence to application waits

    Correlate request stages, connection pools, database waits, and host observations before blaming a generic system resource.

    Start learning
Back to course