Show buffer size tradeoff
run_buffer_tradeoffBuffer Tradeoff experiment — sweep a buffer's capacity from 50 → 10,000 units, measure throughput gain. Shows the diminishing-returns elbow for buffer sizing. Only defined on bs4-ct and bs4-leds; each chapter has THREE inline buffers with different placements (pass buffer id to pick one). Compare CT vs LEDS on the same slot to see why interrupt-detail level changes buffer ROI math (e.g. b3: CT +23.7% vs LEDS +64.2%). Use when the user asks 'how big should the buffer be?' / 'do buffers help on this line?' / 'which buffer position gives the most gain?' / 'what's the diminishing-returns point?'. ANTI-FABRICATION (CRITICAL): the specific tradeoff numbers (e.g. CT +23.7% vs LEDS +64.2%) are sweep-derived reference values. Quote VERBATIM in your reply; do NOT recall similar percentages from training data — every buffer position has different math.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "run_buffer_tradeoff"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| buffer | No | Buffer id to sweep. The Buffer-Options Constraint-Level model has `b3` (Buffer 1, between Capper↔Labeler), `b4` (Buffer 2, between Labeler↔Case Packer), `b5` (Buffer 3, between Case Packer↔Palletizer). The Buffer-Options LEDS model has `b2` (Buffer Option 1, earliest), `b3` (Buffer Option 2, middle), `b4` (Buffer Option 3, last). Defaults to b3 if omitted — but pick the buffer that matches the question (e.g. 'the first inline buffer' = b3 on CT, b2 on LEDS). | b3 |
| chapter | No | Chapter id. Only `bs4-ct` and `bs4-leds` have buffer tradeoffs defined. | bs4-ct |