docs(11): re-measure the overhead budget, and keep both readings by codeitlikemiley · Pull Request #43 · codeitlikemiley/panday

codeitlikemiley · 2026-08-24T04:02:27Z

Task 9: run the overhead bench; if the numbers no longer hold, correct the doc, not the measurement.

	2026-08-20	2026-08-24	budget
establishment p50	21.6µs	49.6µs	—
establishment p99	52.0µs	99.1µs	3ms
per-frame p50	41ns	167ns	—
per-frame p99	1.17µs	2.21µs	1ms

The budget holds with ~30× headroom, and every figure roughly doubled. Both are true, and the second isn't dismissed by the first — a number that moves 2× is worth noticing while the margin is large, because that's the only time it's cheap to.

The doubling is deliberately not attributed

Two things changed between the readings and this measurement cannot separate them:

Real work was added to the establishment path — ExactCache became async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork, merged an hour ago).
The host was not quiet — load average ~4 with another application at ~68% of a core. The 2026-08-20 figures came from an idle machine.

Choosing either cause would be inventing one. Both are named, and a clean re-measurement on an idle host is what would settle it. It has not been done.

Both dated readings are kept rather than the new overwriting the old: one number reads as "this is what it is", two read as "this is how it moves".

Doc-only; fmt --check locally, CI is the gate.

https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

Task 9 of the run brief: run the overhead bench, and if the numbers no longer hold, correct the doc rather than the measurement. The budget holds — establishment p99 99.1µs against 3ms, per-frame p99 2.21µs against 1ms, roughly thirty times the headroom. But every figure is about double what docs/11 recorded on 2026-08-20, and that is worth writing down while the margin is large, because that is the only time it is cheap to. **The doubling is not attributed, because it cannot honestly be.** Two things changed. The establishment path gained real work: `ExactCache` went async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork). And the host was not quiet — load average ~4 with another application holding ~68% of a core, where the original figures came from an idle machine. Picking either cause would be inventing one. Both are named; a clean re-measurement on an idle host is what would settle it and has not been done. Both dated readings are kept rather than the new one overwriting the old. One number reads as "this is what it is"; two read as "this is how it moves", which is the more useful thing to know about a budget with this much room. Claude-Session: https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

codeitlikemiley · 2026-08-24T04:02:27Z

Task 9: run the overhead bench; if the numbers no longer hold, correct the doc, not the measurement.

	2026-08-20	2026-08-24	budget
establishment p50	21.6µs	49.6µs	—
establishment p99	52.0µs	99.1µs	3ms
per-frame p50	41ns	167ns	—
per-frame p99	1.17µs	2.21µs	1ms

The budget holds with ~30× headroom, and every figure roughly doubled. Both are true, and the second isn't dismissed by the first — a number that moves 2× is worth noticing while the margin is large, because that's the only time it's cheap to.

The doubling is deliberately not attributed

Two things changed between the readings and this measurement cannot separate them:

Real work was added to the establishment path — ExactCache became async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork, merged an hour ago).
The host was not quiet — load average ~4 with another application at ~68% of a core. The 2026-08-20 figures came from an idle machine.

Choosing either cause would be inventing one. Both are named, and a clean re-measurement on an idle host is what would settle it. It has not been done.

Both dated readings are kept rather than the new overwriting the old: one number reads as "this is what it is", two read as "this is how it moves".

Doc-only; fmt --check locally, CI is the gate.

https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

Task 9 of the run brief: run the overhead bench, and if the numbers no longer hold, correct the doc rather than the measurement. The budget holds — establishment p99 99.1µs against 3ms, per-frame p99 2.21µs against 1ms, roughly thirty times the headroom. But every figure is about double what docs/11 recorded on 2026-08-20, and that is worth writing down while the margin is large, because that is the only time it is cheap to. **The doubling is not attributed, because it cannot honestly be.** Two things changed. The establishment path gained real work: `ExactCache` went async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork). And the host was not quiet — load average ~4 with another application holding ~68% of a core, where the original figures came from an idle machine. Picking either cause would be inventing one. Both are named; a clean re-measurement on an idle host is what would settle it and has not been done. Both dated readings are kept rather than the new one overwriting the old. One number reads as "this is what it is"; two read as "this is how it moves", which is the more useful thing to know about a budget with this much room. Claude-Session: https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

codeitlikemiley · 2026-08-24T04:02:27Z

Task 9: run the overhead bench; if the numbers no longer hold, correct the doc, not the measurement.

	2026-08-20	2026-08-24	budget
establishment p50	21.6µs	49.6µs	—
establishment p99	52.0µs	99.1µs	3ms
per-frame p50	41ns	167ns	—
per-frame p99	1.17µs	2.21µs	1ms

The budget holds with ~30× headroom, and every figure roughly doubled. Both are true, and the second isn't dismissed by the first — a number that moves 2× is worth noticing while the margin is large, because that's the only time it's cheap to.

The doubling is deliberately not attributed

Two things changed between the readings and this measurement cannot separate them:

Real work was added to the establishment path — ExactCache became async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork, merged an hour ago).
The host was not quiet — load average ~4 with another application at ~68% of a core. The 2026-08-20 figures came from an idle machine.

Choosing either cause would be inventing one. Both are named, and a clean re-measurement on an idle host is what would settle it. It has not been done.

Both dated readings are kept rather than the new overwriting the old: one number reads as "this is what it is", two read as "this is how it moves".

Doc-only; fmt --check locally, CI is the gate.

https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

Task 9 of the run brief: run the overhead bench, and if the numbers no longer hold, correct the doc rather than the measurement. The budget holds — establishment p99 99.1µs against 3ms, per-frame p99 2.21µs against 1ms, roughly thirty times the headroom. But every figure is about double what docs/11 recorded on 2026-08-20, and that is worth writing down while the margin is large, because that is the only time it is cheap to. **The doubling is not attributed, because it cannot honestly be.** Two things changed. The establishment path gained real work: `ExactCache` went async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork). And the host was not quiet — load average ~4 with another application holding ~68% of a core, where the original figures came from an idle machine. Picking either cause would be inventing one. Both are named; a clean re-measurement on an idle host is what would settle it and has not been done. Both dated readings are kept rather than the new one overwriting the old. One number reads as "this is what it is"; two read as "this is how it moves", which is the more useful thing to know about a budget with this much room. Claude-Session: https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

codeitlikemiley · 2026-08-24T04:02:27Z

Task 9: run the overhead bench; if the numbers no longer hold, correct the doc, not the measurement.

	2026-08-20	2026-08-24	budget
establishment p50	21.6µs	49.6µs	—
establishment p99	52.0µs	99.1µs	3ms
per-frame p50	41ns	167ns	—
per-frame p99	1.17µs	2.21µs	1ms

The budget holds with ~30× headroom, and every figure roughly doubled. Both are true, and the second isn't dismissed by the first — a number that moves 2× is worth noticing while the margin is large, because that's the only time it's cheap to.

The doubling is deliberately not attributed

Two things changed between the readings and this measurement cannot separate them:

Real work was added to the establishment path — ExactCache became async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork, merged an hour ago).
The host was not quiet — load average ~4 with another application at ~68% of a core. The 2026-08-20 figures came from an idle machine.

Choosing either cause would be inventing one. Both are named, and a clean re-measurement on an idle host is what would settle it. It has not been done.

Both dated readings are kept rather than the new overwriting the old: one number reads as "this is what it is", two read as "this is how it moves".

Doc-only; fmt --check locally, CI is the gate.

https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

Task 9 of the run brief: run the overhead bench, and if the numbers no longer hold, correct the doc rather than the measurement. The budget holds — establishment p99 99.1µs against 3ms, per-frame p99 2.21µs against 1ms, roughly thirty times the headroom. But every figure is about double what docs/11 recorded on 2026-08-20, and that is worth writing down while the margin is large, because that is the only time it is cheap to. **The doubling is not attributed, because it cannot honestly be.** Two things changed. The establishment path gained real work: `ExactCache` went async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork). And the host was not quiet — load average ~4 with another application holding ~68% of a core, where the original figures came from an idle machine. Picking either cause would be inventing one. Both are named; a clean re-measurement on an idle host is what would settle it and has not been done. Both dated readings are kept rather than the new one overwriting the old. One number reads as "this is what it is"; two read as "this is how it moves", which is the more useful thing to know about a budget with this much room. Claude-Session: https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

codeitlikemiley · 2026-08-24T04:02:27Z

Task 9: run the overhead bench; if the numbers no longer hold, correct the doc, not the measurement.

	2026-08-20	2026-08-24	budget
establishment p50	21.6µs	49.6µs	—
establishment p99	52.0µs	99.1µs	3ms
per-frame p50	41ns	167ns	—
per-frame p99	1.17µs	2.21µs	1ms

The budget holds with ~30× headroom, and every figure roughly doubled. Both are true, and the second isn't dismissed by the first — a number that moves 2× is worth noticing while the margin is large, because that's the only time it's cheap to.

The doubling is deliberately not attributed

Two things changed between the readings and this measurement cannot separate them:

Real work was added to the establishment path — ExactCache became async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork, merged an hour ago).
The host was not quiet — load average ~4 with another application at ~68% of a core. The 2026-08-20 figures came from an idle machine.

Choosing either cause would be inventing one. Both are named, and a clean re-measurement on an idle host is what would settle it. It has not been done.

Both dated readings are kept rather than the new overwriting the old: one number reads as "this is what it is", two read as "this is how it moves".

Doc-only; fmt --check locally, CI is the gate.

https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

Task 9 of the run brief: run the overhead bench, and if the numbers no longer hold, correct the doc rather than the measurement. The budget holds — establishment p99 99.1µs against 3ms, per-frame p99 2.21µs against 1ms, roughly thirty times the headroom. But every figure is about double what docs/11 recorded on 2026-08-20, and that is worth writing down while the margin is large, because that is the only time it is cheap to. **The doubling is not attributed, because it cannot honestly be.** Two things changed. The establishment path gained real work: `ExactCache` went async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork). And the host was not quiet — load average ~4 with another application holding ~68% of a core, where the original figures came from an idle machine. Picking either cause would be inventing one. Both are named; a clean re-measurement on an idle host is what would settle it and has not been done. Both dated readings are kept rather than the new one overwriting the old. One number reads as "this is what it is"; two read as "this is how it moves", which is the more useful thing to know about a budget with this much room. Claude-Session: https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

codeitlikemiley · 2026-08-24T04:02:27Z

Task 9: run the overhead bench; if the numbers no longer hold, correct the doc, not the measurement.

	2026-08-20	2026-08-24	budget
establishment p50	21.6µs	49.6µs	—
establishment p99	52.0µs	99.1µs	3ms
per-frame p50	41ns	167ns	—
per-frame p99	1.17µs	2.21µs	1ms

The budget holds with ~30× headroom, and every figure roughly doubled. Both are true, and the second isn't dismissed by the first — a number that moves 2× is worth noticing while the margin is large, because that's the only time it's cheap to.

The doubling is deliberately not attributed

Two things changed between the readings and this measurement cannot separate them:

Real work was added to the establishment path — ExactCache became async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork, merged an hour ago).
The host was not quiet — load average ~4 with another application at ~68% of a core. The 2026-08-20 figures came from an idle machine.

Choosing either cause would be inventing one. Both are named, and a clean re-measurement on an idle host is what would settle it. It has not been done.

Both dated readings are kept rather than the new overwriting the old: one number reads as "this is what it is", two read as "this is how it moves".

Doc-only; fmt --check locally, CI is the gate.

https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

Task 9 of the run brief: run the overhead bench, and if the numbers no longer hold, correct the doc rather than the measurement. The budget holds — establishment p99 99.1µs against 3ms, per-frame p99 2.21µs against 1ms, roughly thirty times the headroom. But every figure is about double what docs/11 recorded on 2026-08-20, and that is worth writing down while the margin is large, because that is the only time it is cheap to. **The doubling is not attributed, because it cannot honestly be.** Two things changed. The establishment path gained real work: `ExactCache` went async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork). And the host was not quiet — load average ~4 with another application holding ~68% of a core, where the original figures came from an idle machine. Picking either cause would be inventing one. Both are named; a clean re-measurement on an idle host is what would settle it and has not been done. Both dated readings are kept rather than the new one overwriting the old. One number reads as "this is what it is"; two read as "this is how it moves", which is the more useful thing to know about a budget with this much room. Claude-Session: https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

codeitlikemiley · 2026-08-24T04:02:27Z

Task 9: run the overhead bench; if the numbers no longer hold, correct the doc, not the measurement.

	2026-08-20	2026-08-24	budget
establishment p50	21.6µs	49.6µs	—
establishment p99	52.0µs	99.1µs	3ms
per-frame p50	41ns	167ns	—
per-frame p99	1.17µs	2.21µs	1ms

The budget holds with ~30× headroom, and every figure roughly doubled. Both are true, and the second isn't dismissed by the first — a number that moves 2× is worth noticing while the margin is large, because that's the only time it's cheap to.

The doubling is deliberately not attributed

Two things changed between the readings and this measurement cannot separate them:

Real work was added to the establishment path — ExactCache became async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork, merged an hour ago).
The host was not quiet — load average ~4 with another application at ~68% of a core. The 2026-08-20 figures came from an idle machine.

Choosing either cause would be inventing one. Both are named, and a clean re-measurement on an idle host is what would settle it. It has not been done.

Both dated readings are kept rather than the new overwriting the old: one number reads as "this is what it is", two read as "this is how it moves".

Doc-only; fmt --check locally, CI is the gate.

https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

Task 9 of the run brief: run the overhead bench, and if the numbers no longer hold, correct the doc rather than the measurement. The budget holds — establishment p99 99.1µs against 3ms, per-frame p99 2.21µs against 1ms, roughly thirty times the headroom. But every figure is about double what docs/11 recorded on 2026-08-20, and that is worth writing down while the margin is large, because that is the only time it is cheap to. **The doubling is not attributed, because it cannot honestly be.** Two things changed. The establishment path gained real work: `ExactCache` went async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork). And the host was not quiet — load average ~4 with another application holding ~68% of a core, where the original figures came from an idle machine. Picking either cause would be inventing one. Both are named; a clean re-measurement on an idle host is what would settle it and has not been done. Both dated readings are kept rather than the new one overwriting the old. One number reads as "this is what it is"; two read as "this is how it moves", which is the more useful thing to know about a budget with this much room. Claude-Session: https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

codeitlikemiley · 2026-08-24T04:02:27Z

Task 9: run the overhead bench; if the numbers no longer hold, correct the doc, not the measurement.

	2026-08-20	2026-08-24	budget
establishment p50	21.6µs	49.6µs	—
establishment p99	52.0µs	99.1µs	3ms
per-frame p50	41ns	167ns	—
per-frame p99	1.17µs	2.21µs	1ms

The budget holds with ~30× headroom, and every figure roughly doubled. Both are true, and the second isn't dismissed by the first — a number that moves 2× is worth noticing while the margin is large, because that's the only time it's cheap to.

The doubling is deliberately not attributed

Two things changed between the readings and this measurement cannot separate them:

Real work was added to the establishment path — ExactCache became async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork, merged an hour ago).
The host was not quiet — load average ~4 with another application at ~68% of a core. The 2026-08-20 figures came from an idle machine.

Choosing either cause would be inventing one. Both are named, and a clean re-measurement on an idle host is what would settle it. It has not been done.

Both dated readings are kept rather than the new overwriting the old: one number reads as "this is what it is", two read as "this is how it moves".

Doc-only; fmt --check locally, CI is the gate.

https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

Task 9 of the run brief: run the overhead bench, and if the numbers no longer hold, correct the doc rather than the measurement. The budget holds — establishment p99 99.1µs against 3ms, per-frame p99 2.21µs against 1ms, roughly thirty times the headroom. But every figure is about double what docs/11 recorded on 2026-08-20, and that is worth writing down while the margin is large, because that is the only time it is cheap to. **The doubling is not attributed, because it cannot honestly be.** Two things changed. The establishment path gained real work: `ExactCache` went async with a bounded lookup (M11.10), per-route TTL resolution (M11.11), and the classifier's confidence now rides to the audit (M12.5 groundwork). And the host was not quiet — load average ~4 with another application holding ~68% of a core, where the original figures came from an idle machine. Picking either cause would be inventing one. Both are named; a clean re-measurement on an idle host is what would settle it and has not been done. Both dated readings are kept rather than the new one overwriting the old. One number reads as "this is what it is"; two read as "this is how it moves", which is the more useful thing to know about a budget with this much room. Claude-Session: https://claude.ai/code/session_017kFpYDqvz6sKGSkM4YKaRf

Conversation

codeitlikemiley commented Aug 24, 2026

The doubling is deliberately not attributed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

codeitlikemiley commented Aug 24, 2026

The doubling is deliberately not attributed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

codeitlikemiley commented Aug 24, 2026

The doubling is deliberately not attributed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

codeitlikemiley commented Aug 24, 2026

The doubling is deliberately not attributed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

codeitlikemiley commented Aug 24, 2026

The doubling is deliberately not attributed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

codeitlikemiley commented Aug 24, 2026

The doubling is deliberately not attributed

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

codeitlikemiley commented Aug 24, 2026

The doubling is deliberately not attributed

Uh oh!

Reviewers

Assignees

Labels

Projects