KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesMarkov's and Chebyshev's InequalitiesEngineering · Engineering MathematicsLesson 576/887← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20267 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIMarkov's and Chebyshev's Inequalities

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Discrete Probability

Markov's and Chebyshev's Inequalities

Markov's and Chebyshev's inequalities, their proofs, and how they bound deviation from the mean.

Page KV-MATH-0345Reading time 3 minReviewed 2026-08-07Author Kevin Jogin

Executive summary

Markov's inequality bounds the probability that a non-negative variable greatly exceeds its mean, using only the mean. Chebyshev's inequality sharpens this using the variance.

Both are weak compared with exponential bounds but require far less: Markov needs only non-negativity, Chebyshev only a finite variance and pairwise independence within sums.

Learning objectives

  1. State and prove both inequalities.
  2. Choose between them based on available information.
  3. Apply Chebyshev to a sum of pairwise independent variables.

01Markov's inequality

Theorem

Markov's inequality

For a non-negative random variable X and any t > 0:

P(X ≥ t) ≤ E[X] / t.

Proof. E[X] ≥ E[X · 1_{X ≥ t}] ≥ t · P(X ≥ t).

The bound is tight in the worst case — a variable equal to t with probability E[X]/t and 0 otherwise achieves it — so no improvement is possible from the mean alone.

Note
Non-negativity is essential. Without it the inequality is false: a variable symmetric about zero has mean zero, and the bound would claim it never deviates.

02Chebyshev's inequality

Theorem

Chebyshev's inequality

For any random variable X with finite variance and any t > 0:

P(|X − E[X]| ≥ t) ≤ Var[X] / t².

Proof. Apply Markov to the non-negative variable (X − E[X])² at threshold t².

Expressed in standard deviations, the bound says the probability of being k deviations from the mean is at most 1/k². That is weak — the true figure for well-behaved distributions is exponentially small — but it holds universally.

P(|X − μ| ≥ kσ) ≤ 1/k²

03Choosing between them

Comparison of tail bounds
BoundRequiresDecay in tTypical use
MarkovX ≥ 0, finite mean1/tQuick crude bound; proving Chebyshev
ChebyshevFinite variance1/t²Sums of pairwise independent variables
Exponential boundsMutual independence, bounded termse^{−ct²}Repeated-trial amplification

The decisive practical point is the independence requirement. For a sum of n pairwise independent variables the variance is the sum of variances, so Chebyshev gives concentration within O(√n) — enough for most sampling arguments, and available from a hash family needing only logarithmic randomness.

Exponential bounds give concentration within O(√(n log n)) with far better probability, but they need mutual independence, which is expensive to supply.

04Frequently asked questions

Why is Chebyshev only quadratic in decay?

Because it uses only the second moment. Bounding higher moments gives faster decay, and taking all moments through the moment generating function gives exponential decay — which is precisely how the sharper bounds are derived.

Can Chebyshev be applied to a one-sided deviation?

Directly it bounds two-sided deviation, so a one-sided bound follows by halving only when the distribution is symmetric. Cantelli's inequality gives a sharper one-sided version without a symmetry assumption.

When is Markov alone sufficient?

When the conclusion needs only that a quantity is rarely a large constant factor above its mean — for instance, showing a randomised algorithm exceeds twice its expected running time with probability at most one half, which is enough to justify restarting.

Related pages

  • Approximating Functions by Random Sampling
  • Useful Facts and Standard Estimates
  • Expectation and Variance
  • The Birthday Paradox

Sources and method

Structural reference: Victor Shoup, A Computational Introduction to Number Theory and Algebra, Version 1, Cambridge University Press, 2005 — book pages 117-121.

This page carries the durable method layer only: definitions, constructions, algorithms, complexity results and selection criteria, authored originally for KEVOS. No text is transcribed or paraphrased from the source, and no numeric tables or benchmark data are reproduced — these are routed to live authoritative sources instead.

Author: Kevin Jogin. Last reviewed 2026-08-07.

Handbook application: from concept to controlled practice

Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Markov's and Chebyshev's Inequalities. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.

The operating aim is to turn a compact mathematical statement into a usable chain of definitions, claims, examples and checks. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.

Treat Markov's and Chebyshev's Inequalities as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—markov's, chebyshev's, inequalities, inequality, proofs—should be made explicit before any proof or computation begins. Record the ambient set or structure, the permitted operations and the equality or equivalence relation in use. A compact theorem often changes meaning when the base field, finiteness condition, commutativity assumption or direction of an action changes.

For a proof, write the hypotheses as a checklist and mark the line at which each one is used. For a computation, state the representation of the input, the arithmetic model, the termination condition and the output invariant. For a classification problem, distinguish existence from uniqueness and distinguish an object from its representation. These separations prevent a correct local calculation from being mistaken for the general result.

A useful worked example should be small enough to inspect completely but rich enough to exercise the main mechanism. Compute the result in two ways where practical: symbolically and by substitution, structurally and numerically, or directly and through a normal form. Then include one near-miss example in which a hypothesis fails. The contrast explains why the theorem is shaped as it is and gives the reader a diagnostic pattern for later problems.

Verification is part of the mathematics. Check domains and codomains, substitute proposed solutions, test identity and zero cases, compare dimensions or cardinalities, and confirm that maps respect the required operations. In numerical work, report precision, conditioning and a residual rather than digits alone. In algorithmic work, separate mathematical correctness from implementation complexity and resource limits.

Step-by-step operating method

  1. Fix the setting. State the objects, ambient structure, notation and assumptions before manipulating symbols.
  2. Separate claims. Distinguish definitions, hypotheses, conclusions, equivalent conditions and consequences.
  3. Choose a method. Select proof, construction, calculation or algorithm according to the question actually asked.
  4. Work a small case. Use the smallest non-trivial example to expose the mechanism and test edge behaviour.
  5. Verify independently. Substitute back, check invariants, test boundary cases or use an alternative derivation.

Worked-example protocol

Illustrative method—not a source theorem. Start with a small admissible input and list the definitions it must satisfy. Carry out each transformation on a separate line, citing the property that permits it. Preserve exact values until approximation is necessary. At the end, verify the output against the original definition and one invariant such as dimension, degree, determinant, order, norm or residual. Then alter one hypothesis and observe which step ceases to be valid. This protocol creates a reusable example without inventing a theorem-specific numerical answer.

StageRecordQuality check
InputObjects, domain, notation, assumptionsEvery symbol is defined
MethodPermitted operation or cited result at each stepAll hypotheses hold
OutputExact result and representationCorrect type, domain and form
VerificationSubstitution, invariant or alternative derivationIndependent agreement
Boundary testZero, identity, degenerate or failed hypothesisScope is understood

Common failure modes and recovery actions

1. Watch for

Using a theorem without checking every hypothesis.

Recovery: Return to the governing definition or requirement and restate the decision in one sentence.

2. Watch for

Treating a suggestive example as a proof of the general case.

Recovery: Separate evidence from assumption, assign an owner and set a date for validation.

3. Watch for

Changing notation or conventions part-way through an argument.

Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.

4. Watch for

Hiding a division-by-zero, convergence, finiteness or commutativity assumption.

Recovery: Record the consequence, decision and rationale, then update the controlled baseline.

5. Watch for

Reporting a computed result without a residual, substitution or structural check.

Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.

Review checklist

  • Can every symbol be traced to a definition or prior result?
  • Which hypothesis does each major step use?
  • Does the method cover zero, identity, degenerate and boundary cases?
  • Can the conclusion be checked by a second representation or calculation?
  • Are mandatory requirements distinguished from recommendations and illustrative values?
  • Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
  • Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
  • Is there a named owner and a trigger for review, escalation, change or retirement?

Questions for deeper application

What is the most important distinction a practitioner must preserve when applying Markov's and Chebyshev's Inequalities?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which assumption about markov's would change the result most if it proved false?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What evidence would allow an independent reviewer to reproduce or challenge the conclusion?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Which boundary, exception or failure case has not yet been tested?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

What must be handed over, monitored or reviewed after the immediate work is complete?

Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.

Authoritative references and use notes

The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.

  • MIT OpenCourseWare — Algebra I — Massachusetts Institute of Technology. Used for groups, vector spaces, linear transformations and linear groups. Accessed 2026-08-13.
  • The Stacks Project — table of contents — The Stacks Project. Used for commutative algebra, homological algebra, modules and derived categories. Accessed 2026-08-13.

Continue learning

Expectation and VarianceGuide · Engineering MathematicsNEXT LESSON →The Birthday ParadoxGuide · Engineering MathematicsRandom VariablesGuide · Engineering MathematicsHash Function FamiliesGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®