Paper VIII visual guide · Visual 31 of 32 · SHARED COMPILATION HAS ITS OWN OBJECTIVE

One tree can serve a weighted family

Traditional p. 31 / Corollary 9.5, Theorem 9.4.

Start reading

Resources & source

Original plate in the visual-guide PDF · Original atlas source

Skip contents and start reading

Use a tree with one root and two terminal children. There are exactly two admissible prunings: keep the root, or split into both children. All declared errors and the split overhead are zero. Their additive total costs are:

Additive costs for keeping or splitting the common tree
Cost componentKeepSplit
Setup paid once42
Operator 1, per use28
Operator 2, per use72
One common pruning under changing reuse weights
Original drawing. Read the description below; expand the labels and data for selectable text.

Reading the drawing

Solid and dashed affine cost lines compare keeping and splitting the same supplied tree. Their crossing and the marked integer samples determine the declared shared optimum.

Drawing labels and data 11 labels

Read the original labels as selectable text. Tables preserve grid relationships; other short labels are grouped compactly.

  • \(r_2\)
  • modeled cost
  • \(6+7r_2\) : keep
  • \(10+2r_2\) : split
  • \(4/5\)
  • \(0\)
  • \(2\)
  • \(3\)
  • \(4\)
  • \(27\)
  • \(16\)

Open the full-size drawing

With reuse weights \((r_1,r_2)=(1,3)\), the aggregated objectives are

\[ J_{\rm keep}=4+2+3\cdot7=27,\qquad J_{\rm split}=2+8+3\cdot2=16. \]

The exact shared optimum is split. Operator 1 alone prefers keep on its per-use costs, while operator 2 prefers split. Choosing independently and trying to combine those decisions would not solve the declared one-pruning problem.

A hand-computable decision threshold

Fix \(r_1=1\) and vary \(r_2=r\ge0\). Keeping costs \(6+7r\) and splitting costs \(10+2r\). Splitting is strictly cheaper when \(r>4/5\); its first integer reuse win is \(r=1\). The checker evaluates both admissible choices for integers zero through four and checks the displayed totals at three.

Where the common-tree proof applies

The family corollary aggregates local keep costs and errors, then uses the same exact subtree recurrence. In this example, each row denotes the sum of the selected local leaf terms; it does not conceal a nonlocal discount. A setup shared by distant unrelated nodes, overlapping candidates, or a global resource constraint would need an enlarged state or a different model.

Read this as

Reuse weights change the objective before compilation. Shared optimality is exact for the supplied common tree and additive family costs, rather than for an unspecified set of future workloads.

Source and conversion record

The original atlas wording, equations, and drawing labels are retained. Drawings are views of the retained visual-guide PDF. Text descriptions and table headings are added reading aids. This conversion does not rebuild TeX, rerun the examples, audit proofs or compile Lean.

The revised crosswalk binds all 32 plates to the retained PDF. Manuscript links use stable source labels checked against the manuscript. The guide’s “Classical input 7.5” resolves to the manuscript’s “Standard fact 7.5” at the same label.

Conversion checks and source hashes

Notation in Paper VIII

Look up a symbol without leaving this chapter. Select text before opening help to search for it.

Search this work’s notation.

    Symbols can have different meanings in different passages. Read each result in its own context.

    Open the full notation index