KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesTrial Division up to a Small BoundEngineering · Engineering MathematicsLesson 620/887← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AITrial Division up to a Small Bound

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Primality Testing

Trial Division up to a Small Bound

Choosing the trial division bound ahead of a probabilistic test, and the cost balance that determines it.

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

Executive summary

Trial division ahead of Miller-Rabin removes most composites cheaply. How far to divide is an optimisation with a clear structure: division cost rises linearly in the bound while the rejection rate improves only logarithmically.

Mertens' theorem supplies the survival rate, making the optimum computable rather than guessed.

Learning objectives

  1. Quantify the survival rate as a function of the bound.
  2. Balance division cost against saved exponentiations.
  3. Implement the filter efficiently.

01Survival rate

The proportion of odd integers with no prime factor below y follows from Mertens' theorem.

survival ≈ 2 e^{−γ} / ln y    (the factor 2 because even numbers are excluded already)
Filter survival by bound
Bound yPrimes below yOdd candidates surviving
10025≈ 24%
1,000168≈ 16%
10,0001,229≈ 12%
65,5366,542≈ 10%
Note
The logarithmic denominator is the key fact: increasing the bound by a factor of ten improves the survival rate only modestly, while the division cost rises by a factor of about ten. Diminishing returns set in quickly.

02The cost balance

  1. Cost of filtering

    Roughly π(y) single-precision divisions per candidate, or one multiprecision gcd.

  2. Cost of a Miller-Rabin round

    One modular exponentiation, O(len(n)³) — thousands of times more expensive.

  3. Expected total

    candidates × filter cost + survivors × exponentiation cost.

  4. Optimise

    Increase y while the marginal reduction in survivors saves more than the added divisions cost.

Because an exponentiation costs so much more than a division, the optimum sits well beyond where the survival curve has flattened. Bounds in the low thousands to tens of thousands are typical, and the optimum is broad — anywhere in that range performs within a few per cent of the best.

For larger moduli the balance shifts upward, since the exponentiation cost grows cubically in the bit length while the division cost is roughly constant.

03Efficient implementation

Rather than dividing by each small prime in turn, compute a single gcd against a precomputed product.

Algorithm

Filter by gcd against a primorial

Inputcandidate n, precomputed primorial P
Outputreject, or pass to Miller-Rabin
  1. Precompute P = product of all primes in (2, y].
  2. For each candidate n:
  3.   Compute g = gcd(n, P).
  4.   If g ≠ 1, reject n as composite.
  5.   Otherwise pass n to the probabilistic test.
Cost  one gcd, O(len(n) · len(P))
Caution
The gcd approach rejects but does not identify which small prime divides the candidate. That is usually irrelevant during prime generation, where a rejected candidate is simply discarded, but it matters if the factor is wanted.

A further refinement used in incremental search: compute the residue of a base candidate against each small prime once, then update the residues by addition as the candidate is stepped, avoiding a fresh division per step. This is the standard sieve-based generation technique.

04Frequently asked questions

Why exclude 2 from the primorial?

Because candidates are already odd by construction. Including 2 would make every gcd even and reject everything.

Is one large gcd really faster than many small divisions?

For multiprecision candidates, yes, because the divisions are all multiprecision-by-single-precision and there are thousands of them. The gcd is a single operation on operands of comparable size.

Does the optimum depend on the Miller-Rabin round count?

Only weakly. Most rejected candidates fail on the first round, so the marginal cost of a survivor is roughly one exponentiation regardless of how many rounds a survivor would eventually receive.

Related pages

  • The Sieve of Eratosthenes
  • Mertens' Theorem
  • Generating a Random Prime Between 2 and M
  • Generating a Random k-Bit Prime with Miller-Rabin

Sources and method

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

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 up to a Small Bound. 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 up to a Small Bound as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—trial, division, bound, cost, balance—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 up to a Small Bound?

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

Generating a Random Prime Between 2 and MGuide · Engineering MathematicsNEXT LESSON →Generating a Random k-Bit Prime with Miller-RabinGuide · Engineering MathematicsThe Miller-Rabin Primality TestGuide · Engineering MathematicsPerfect Power Testing and Prime Power FactoringGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®