KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesTrial Division and Basic Primality TestingEngineering · Engineering MathematicsLesson 612/883← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AITrial Division and Basic Primality Testing

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Primality Testing

Trial Division and Basic Primality Testing

Trial division as a primality test and as a filter, its exponential cost, and the role it still plays in practice.

Page KV-MATH-0385Reading time 4 minReviewed 2026-08-07Author Kevin Jogin

Executive summary

Trial division tests primality by attempting division by every candidate factor up to the square root. It is correct, simple, and exponential in the input length.

It survives in practice not as a test but as a filter: rejecting candidates with small factors cheaply before an expensive test is applied.

Learning objectives

  1. State trial division and prove its correctness bound.
  2. Explain why it is exponential despite appearing polynomial.
  3. Size the filter bound for use ahead of Miller-Rabin.

01The method

Algorithm

Trial division

Inputinteger n
Outputprime, or composite with a factor
  1. If n < 2, report composite or unit.
  2. For each candidate d = 2, 3, 5, 7, ... while d² ≤ n:
  3.   If d divides n, report composite with factor d.
  4. Report prime.
Cost  O(√n) divisions = O(2^{ℓ/2}) in the bit length ℓ
Theorem

Square root bound

If n is composite then it has a prime factor not exceeding √n.

Reason. Write n = ab with 1 < a ≤ b. Then a² ≤ ab = n, so a ≤ √n, and any prime factor of a is at most a.

Caution
The √n cost looks modest but is exponential in the input size. For a 2048-bit modulus it is about 2^1024 divisions, which is not merely slow but physically impossible.

02Trial division as a filter

Its real use is eliminating candidates with small factors before an expensive probabilistic test. Most composites have a small factor, so a short division loop removes most of them for a fraction of one modular exponentiation.

Filtering effectiveness
Filter boundOdd candidates survivingCost per candidate
3 only≈ 67%One division
Primes below 100≈ 12%About 25 divisions
Primes below 1000≈ 8%About 168 divisions
Primes below 65536≈ 5%About 6500 divisions

The survival proportion follows from Mertens' theorem as approximately e^{−γ}/ln y for bound y, and the diminishing returns are visible: going from 1000 to 65536 costs forty times the divisions to remove another three per cent.

Note
The optimal bound balances division cost against the saved exponentiations. In practice a few thousand is typical, often implemented as a single gcd against a precomputed product of small primes rather than as a division loop.

03Where it remains the right tool

  • Numbers small enough that √n is trivially reachable — under a few billion, trial division against a sieved prime table is faster than any probabilistic test.
  • Filtering candidates in prime generation, as above.
  • Completely factoring a number known to be smooth, where every factor is small by hypothesis.
  • Extracting small factors before invoking a general factoring algorithm, which almost all such algorithms assume has been done.

A useful implementation trick: rather than dividing by each small prime, compute a single gcd against the product of all primes below the bound. One gcd replaces thousands of divisions, and the product is precomputed once.

04Frequently asked questions

Is trial division ever preferable to Miller-Rabin?

For small inputs, yes. Below roughly 2^32 a lookup against a sieved table or a short division loop beats a modular exponentiation. The crossover is where the square root cost exceeds the exponentiation cost.

Why divide only by primes rather than all integers?

Because a composite divisor's prime factors would have been found earlier. Dividing by primes only reduces the work by a factor of about ln n, at the cost of needing a prime table.

Does finding no factor below the square root prove primality?

Yes, unconditionally. Trial division is a proof, not a probabilistic test — which is why it remains the definitive method for small numbers despite its cost on large ones.

Related pages

  • The Sieve of Eratosthenes
  • Divisibility and Primality
  • The Structure of the Group of Units Modulo n

Sources and method

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

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 Trial Division and Basic Primality Testing. 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 Trial Division and Basic Primality Testing as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—trial, division, primality, filter, method—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 Trial Division and Basic Primality Testing?

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 trial 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

Ring Homomorphisms and IsomorphismsGuide · Engineering MathematicsNEXT LESSON →The Structure of the Group of Units Modulo nGuide · Engineering MathematicsIdeals and Quotient RingsGuide · Engineering MathematicsThe Fermat Test and Carmichael NumbersGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®