Ambiguity
methodology/envelope.md says: “Per-entrant parallelism knobs are therefore sized to the partition count, not to the CPU count.” The current topic has 32 partitions. PR #75 screened widths 8 and 16 without treating this sentence as a separate contract question.
The stated rationale is uneven partition ownership. Divisors of 32 can assign partitions uniformly (two per consumer at width 16), but that does not make the normative requirement disappear. Configuration freedom under rule 1 and this prescribed width need an explicit resolution.
Proposed resolution
Discuss in a contract-only PR whether every entrant may use a divisor of the partition count within the unchanged CPU/memory envelope. Require reporting raw throughput as well as CPU efficiency so using fewer workers cannot hide a throughput tradeoff.
Until resolved, PR #75 targets one TaskManager at width 32. Width-8/16 measurements remain exploratory evidence, ineligible for a default promotion under the current wording. The multi-process proposal #76 is a separate question and does not settle consumer width.
Ambiguity
methodology/envelope.mdsays: “Per-entrant parallelism knobs are therefore sized to the partition count, not to the CPU count.” The current topic has 32 partitions. PR #75 screened widths 8 and 16 without treating this sentence as a separate contract question.The stated rationale is uneven partition ownership. Divisors of 32 can assign partitions uniformly (two per consumer at width 16), but that does not make the normative requirement disappear. Configuration freedom under rule 1 and this prescribed width need an explicit resolution.
Proposed resolution
Discuss in a contract-only PR whether every entrant may use a divisor of the partition count within the unchanged CPU/memory envelope. Require reporting raw throughput as well as CPU efficiency so using fewer workers cannot hide a throughput tradeoff.
Until resolved, PR #75 targets one TaskManager at width 32. Width-8/16 measurements remain exploratory evidence, ineligible for a default promotion under the current wording. The multi-process proposal #76 is a separate question and does not settle consumer width.