KEVOS
ArticlesServicesCase studiesAboutContact
ArticlesServicesCase studiesAboutContact
← ArticlesBetter Smoothness Density EstimatesEngineering · Engineering MathematicsLesson 632/883← PrevNext →
GuidePublished 7 Aug 2026Updated 13 Aug 20268 min readBy Kevin Jogin
On this page

Ask about this page

KEVOS AIBetter Smoothness Density Estimates

KEVOS knowledge first · trusted web sources when needed

Engineering  /  Mathematics  — Discrete Logarithms and Factoring

Better Smoothness Density Estimates

Refined estimates for smooth number density and how they determine optimal sieve parameters.

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

Executive summary

The crude Dickman estimate is enough to derive the asymptotic complexity of sieve algorithms, but not to choose parameters for a specific factorisation.

Practical parameter selection uses refined estimates together with empirical calibration, because the optimum is flat near its minimum and the asymptotics hide substantial constants.

Learning objectives

  1. State the refined smoothness estimates.
  2. Derive the optimal smoothness bound.
  3. Explain why empirical calibration remains necessary.

01Refining the estimate

The Dickman function ρ(u) satisfies a differential-delay equation and its asymptotic u^{−u} is accurate only to within factors that matter in practice.

ρ(u) = u^{−u(1 + o(1))},   with the o(1) term significant for the u values arising in practice

For sieve algorithms the relevant u is typically between 2 and 5, where the asymptotic form is noticeably off. Numerical evaluation of the Dickman function, or tabulated values, is used instead.

Note
A further refinement matters for the sieve setting: the candidates are not random integers but values of a polynomial, whose smoothness behaviour differs. Sieve implementations account for this with correction factors derived from the polynomial's root structure modulo small primes.

02Deriving the optimal bound

  1. Write the total cost

    Cost of collecting relations plus cost of the linear algebra, both as functions of the smoothness bound y.

  2. Express relation cost

    Number of candidates needed is proportional to 1/ρ(u), with u = ln n / ln y.

  3. Express algebra cost

    Roughly the square or a low power of the factor base size, which is π(y).

  4. Minimise

    Differentiate the sum with respect to y and solve, giving y of the form L(1/2) or L(1/3).

The resulting optimum is what produces the subexponential complexity. The derivation is the reason those particular exponents appear rather than any others.

  1. Quadratic sievey ≈ L(1/2, 1/2)Total cost L(1/2, 1)
  2. Number field sievey ≈ L(1/3, c)Total cost L(1/3, 1.92)

03Why calibration is still needed

Caution
The asymptotic optimum is derived with constants absorbed into o(1) terms, which at practical sizes are not negligible. Using the asymptotic formula directly can be off by a factor of several in the parameter, and while the cost curve is flat near its minimum, being far off is expensive.

Serious implementations tune parameters empirically against the target size, using the theory to locate the neighbourhood and measurement to find the point within it.

Sieve parameters and their sensitivity
ParameterSet bySensitivity
Smoothness boundTheory plus calibrationFlat near optimum; costly if far off
Sieve interval lengthMemory and cache sizeHardware dependent
Large prime boundsEmpiricalSubstantial gains from partial relations
Polynomial selectionExtensive searchAmong the highest-value choices in NFS

Polynomial selection in the number field sieve is worth singling out: a substantial fraction of total effort is spent searching for a good polynomial before sieving begins, because the choice affects the smoothness rate of every candidate that follows.

04Frequently asked questions

Why is the cost curve flat near the optimum?

Because the two opposing costs cross at a shallow angle — one rising and one falling smoothly. That flatness is forgiving of imprecise parameter choice, which is why rough calibration suffices in practice.

Are large primes worth allowing?

Yes, substantially. Permitting one or two primes above the smoothness bound in a relation produces partial relations that combine into full ones, and this yields large practical gains at little cost.

Does polynomial selection affect the asymptotic complexity?

Only in the constant, but that constant is significant. A better polynomial improves smoothness rates across the entire sieving phase, so the search effort pays back many times over.

Related pages

  • Smooth Numbers
  • Subexponential Integer Factoring
  • The Quadratic Sieve Algorithm

Sources and method

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

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 Better Smoothness Density Estimates. 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 Better Smoothness Density Estimates as a network of definitions and implications, not as a list of formulas. The working vocabulary on this page—density, estimates, optimal, better, smoothness—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 Better Smoothness Density Estimates?

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 density 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 — Number Theory I — Massachusetts Institute of Technology. Used for algebraic and analytic number theory. Accessed 2026-08-13.
  • MIT OpenCourseWare — Algebra I — Massachusetts Institute of Technology. Used for groups, vector spaces, linear transformations and linear groups. Accessed 2026-08-13.

Continue learning

Subexponential Integer FactoringGuide · Engineering MathematicsNEXT LESSON →The Quadratic Sieve AlgorithmGuide · Engineering MathematicsSubexponential Discrete Logarithm AlgorithmsGuide · Engineering MathematicsThe Number Field Sieve and Factoring RecordsGuide · Engineering Mathematics
KEVOS · Engineering, manufacturing and project improvement
ArticlesServicesCase studiesAboutContact
© 2026 KEVOS®