{"schema_version":"1.0","gateway":{"key":"plano","display":"Plano","lang":"Rust","cls":"AI proxy / data plane","repo":"https://github.com/katanemo/plano","version":"0.4.39","stars":7117,"stars_as_of":"2026-11-14","first_commit":"2024-07-09","matrix":{"gateway":"plano","build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","matrix_version":null,"served":true,"serve_error":"","upstream_shape":"","upstream_note":"","egress_configured":"","probe_first":false,"capability_note":"","cell_perf_sweep":true,"sweep_rung_selection":null,"sweep_ttft_ms":null,"p99_ceiling_ms":null,"sweep_dur":null,"cell_stream":true,"cell_memory":true,"memory":null,"cells":{},"upstreams":{"bedrock":{"configurable":true,"served":true,"egress_config":null,"serve_error":"","cells":{"openai":{"served":true,"reason":null,"status":"","path":"/v1/chat/completions","verdict_note":"","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":{"added_latency_p50_us":{"value":205998,"certified":true,"suppressed":false},"added_latency_p99_us":{"value":212984,"certified":true,"suppressed":false},"gateway_c1_p99_us":{"value":213012,"certified":true,"suppressed":false},"direct_c1_p99_us":{"value":28,"certified":true,"suppressed":false},"cpu_us_per_request":{"value":189176.47058823527,"certified":true,"suppressed":false},"rps_per_cpu_second":{"value":5.286069651741294,"certified":true,"suppressed":false},"cost_window_conc":{"value":8,"certified":true,"suppressed":false},"cost_core_utilisation":{"value":0.6169920805069831,"certified":true,"suppressed":false},"cost_window_ok":{"value":85,"certified":true,"suppressed":false},"cost_window_rps":{"value":14,"certified":true,"suppressed":false},"cost_threads":{"value":68,"certified":true,"suppressed":false},"cost_nonvol_ctxt_per_request":{"value":5.141176470588236,"certified":true,"suppressed":false},"cost_majflt":{"value":0,"certified":true,"suppressed":false},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false},"concurrency":8,"p99_us":831737,"first_disqualified_conc":256,"lower_bound":false,"samples":127}],"sweep":[{"conc":1,"ok":29,"rps":4,"p99_us":208994,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":201000,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":210011,"fail":0},{"conc":2,"ok":32,"rps":5,"p99_us":378986,"fail":0},{"conc":2,"ok":32,"rps":5,"p99_us":384977,"fail":0},{"conc":2,"ok":32,"rps":5,"p99_us":378725,"fail":0},{"conc":4,"ok":89,"rps":14,"p99_us":391015,"fail":0},{"conc":4,"ok":84,"rps":13,"p99_us":392647,"fail":0},{"conc":4,"ok":88,"rps":14,"p99_us":388017,"fail":0},{"conc":8,"ok":126,"rps":20,"p99_us":727628,"fail":0},{"conc":8,"ok":126,"rps":20,"p99_us":724829,"fail":0},{"conc":8,"ok":127,"rps":21,"p99_us":831737,"fail":0},{"conc":16,"ok":113,"rps":18,"p99_us":2128828,"fail":0},{"conc":16,"ok":115,"rps":19,"p99_us":3168838,"fail":0},{"conc":16,"ok":114,"rps":18,"p99_us":2209817,"fail":0},{"conc":32,"ok":101,"rps":16,"p99_us":3094514,"fail":0},{"conc":32,"ok":102,"rps":16,"p99_us":3335594,"fail":0},{"conc":32,"ok":92,"rps":14,"p99_us":5131938,"fail":0},{"conc":64,"ok":72,"rps":11,"p99_us":5716273,"fail":0},{"conc":64,"ok":76,"rps":12,"p99_us":5912282,"fail":0},{"conc":64,"ok":79,"rps":13,"p99_us":5476791,"fail":0},{"conc":128,"ok":13,"rps":2,"p99_us":5800221,"fail":0},{"conc":128,"ok":41,"rps":6,"p99_us":5913884,"fail":0},{"conc":128,"ok":26,"rps":4,"p99_us":5066908,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0}],"rungs":[{"conc":1,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":208994,"windows":3,"clean_windows":3},{"conc":2,"rps":{"value":5,"certified":true,"suppressed":false},"p99_us":378986,"windows":3,"clean_windows":3},{"conc":4,"rps":{"value":14,"certified":true,"suppressed":false},"p99_us":391015,"windows":3,"clean_windows":3},{"conc":8,"rps":{"value":20,"certified":true,"suppressed":false},"p99_us":727628,"windows":3,"clean_windows":3},{"conc":16,"rps":{"value":18,"certified":true,"suppressed":false},"p99_us":2209817,"windows":3,"clean_windows":3},{"conc":32,"rps":{"value":16,"certified":true,"suppressed":false},"p99_us":3335594,"windows":3,"clean_windows":3},{"conc":64,"rps":{"value":12,"certified":true,"suppressed":false},"p99_us":5716273,"windows":3,"clean_windows":3},{"conc":128,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":5800221,"windows":3,"clean_windows":3},{"conc":256,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"no window at c=256 was clean: 0 of 3 failed requests, the rest carried no usable rate or failure count"},"p99_us":null,"windows":3,"clean_windows":0}],"egress_reverified":true,"c1_note":"the c=1 percentiles are taken over 29 successful gateway round trip(s) and 262765 direct-to-mock round trip(s), each leg a single clean window with no failures","gateway_c1_samples":29,"direct_c1_samples":262765},"stream":{"stream_served":"untestable","stream_error":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","reason":"untestable","stream_c1_note":null,"added_ttft_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"added_ttft_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"streams_sustained_fps":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"streams_sustained":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"}},"memory":{"protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","served":true,"serve_error":"","load_recipe":null,"idle_rss_mib":{"value":598.80078125,"certified":true,"suppressed":false},"steady_state_rss_mib":{"value":1006.28515625,"certified":true,"suppressed":false},"recovered_rss_mib":{"value":1006.22265625,"certified":true,"suppressed":false},"peak_rss_mib":{"value":1006.6875,"certified":true,"suppressed":false},"peak_rss_hwm_mib":{"value":1006.46875,"certified":true,"suppressed":false},"plateaued":true,"time_to_plateau_s":{"value":61,"certified":true,"suppressed":false},"growth_rate_mib_per_min":{"value":-0.329296963138252,"certified":true,"suppressed":false},"load_s":{"value":306,"certified":true,"suppressed":false},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"idle_static":{"value":1,"certified":true,"suppressed":false},"idle_growth_rate_mib_per_min":{"value":0.046660991313913644,"certified":true,"suppressed":false},"rss_series":[{"t_s":0,"rss_mib":599.30859375},{"t_s":2,"rss_mib":1002.515625},{"t_s":2,"rss_mib":1002.53125},{"t_s":5,"rss_mib":1002.875},{"t_s":6,"rss_mib":1002.875},{"t_s":9,"rss_mib":1003.140625},{"t_s":9,"rss_mib":1003.1484375},{"t_s":12,"rss_mib":1003.2421875},{"t_s":12,"rss_mib":1003.25390625},{"t_s":15,"rss_mib":1003.734375},{"t_s":15,"rss_mib":1003.73828125},{"t_s":17,"rss_mib":1003.8125},{"t_s":18,"rss_mib":1003.8125},{"t_s":20,"rss_mib":1003.94140625},{"t_s":21,"rss_mib":1003.94140625},{"t_s":24,"rss_mib":1004.015625},{"t_s":24,"rss_mib":1004.015625},{"t_s":27,"rss_mib":1004.2109375},{"t_s":27,"rss_mib":1004.2109375},{"t_s":29,"rss_mib":1004.25},{"t_s":30,"rss_mib":1004.23046875},{"t_s":33,"rss_mib":1004.26171875},{"t_s":34,"rss_mib":1004.21484375},{"t_s":36,"rss_mib":1004.37890625},{"t_s":36,"rss_mib":1004.390625},{"t_s":39,"rss_mib":1004.44140625},{"t_s":40,"rss_mib":1004.37109375},{"t_s":42,"rss_mib":1004.58984375},{"t_s":42,"rss_mib":1004.5390625},{"t_s":45,"rss_mib":1004.578125},{"t_s":45,"rss_mib":1004.578125},{"t_s":47,"rss_mib":1004.62109375},{"t_s":50,"rss_mib":1004.625},{"t_s":51,"rss_mib":1004.61328125},{"t_s":51,"rss_mib":1004.61328125},{"t_s":54,"rss_mib":1004.6640625},{"t_s":54,"rss_mib":1004.6640625},{"t_s":57,"rss_mib":1004.72265625},{"t_s":57,"rss_mib":1004.7265625},{"t_s":60,"rss_mib":1004.73828125},{"t_s":61,"rss_mib":1004.73828125},{"t_s":63,"rss_mib":1004.87890625},{"t_s":64,"rss_mib":1004.87890625},{"t_s":67,"rss_mib":1004.9375},{"t_s":67,"rss_mib":1004.9375},{"t_s":69,"rss_mib":1005.140625},{"t_s":70,"rss_mib":1005.140625},{"t_s":72,"rss_mib":1005.28125},{"t_s":73,"rss_mib":1005.28125},{"t_s":76,"rss_mib":1005.42578125},{"t_s":76,"rss_mib":1005.42578125},{"t_s":78,"rss_mib":1005.46875},{"t_s":81,"rss_mib":1005.31640625},{"t_s":81,"rss_mib":1005.578125},{"t_s":82,"rss_mib":1005.578125},{"t_s":85,"rss_mib":1005.66796875},{"t_s":85,"rss_mib":1005.66796875},{"t_s":87,"rss_mib":1005.6796875},{"t_s":89,"rss_mib":1005.7109375},{"t_s":90,"rss_mib":1005.546875},{"t_s":91,"rss_mib":1005.546875},{"t_s":92,"rss_mib":1005.55078125},{"t_s":94,"rss_mib":1005.55078125},{"t_s":95,"rss_mib":1005.5078125},{"t_s":97,"rss_mib":1005.52734375},{"t_s":100,"rss_mib":1005.55078125},{"t_s":100,"rss_mib":1005.55078125},{"t_s":103,"rss_mib":1005.5625},{"t_s":103,"rss_mib":1005.5625},{"t_s":106,"rss_mib":1005.57421875},{"t_s":106,"rss_mib":1005.57421875},{"t_s":109,"rss_mib":1005.82421875},{"t_s":109,"rss_mib":1005.82421875},{"t_s":112,"rss_mib":1005.96484375},{"t_s":114,"rss_mib":1005.98828125},{"t_s":115,"rss_mib":1005.86328125},{"t_s":115,"rss_mib":1005.86328125},{"t_s":116,"rss_mib":1005.83203125},{"t_s":119,"rss_mib":1005.85546875},{"t_s":120,"rss_mib":1005.8671875},{"t_s":123,"rss_mib":1005.88671875},{"t_s":125,"rss_mib":1005.78125},{"t_s":125,"rss_mib":1005.78125},{"t_s":126,"rss_mib":1005.78515625},{"t_s":128,"rss_mib":1005.78515625},{"t_s":128,"rss_mib":1005.7890625},{"t_s":133,"rss_mib":1005.77734375},{"t_s":134,"rss_mib":1005.79296875},{"t_s":134,"rss_mib":1005.79296875},{"t_s":137,"rss_mib":1005.85546875},{"t_s":137,"rss_mib":1005.85546875},{"t_s":139,"rss_mib":1005.875},{"t_s":140,"rss_mib":1005.875},{"t_s":141,"rss_mib":1005.87890625},{"t_s":145,"rss_mib":1005.921875},{"t_s":145,"rss_mib":1005.75390625},{"t_s":146,"rss_mib":1005.765625},{"t_s":147,"rss_mib":1005.77734375},{"t_s":149,"rss_mib":1005.77734375},{"t_s":150,"rss_mib":1005.76953125},{"t_s":152,"rss_mib":1005.78125},{"t_s":155,"rss_mib":1005.80078125},{"t_s":156,"rss_mib":1005.8125},{"t_s":156,"rss_mib":1005.671875},{"t_s":158,"rss_mib":1005.72265625},{"t_s":161,"rss_mib":1005.83984375},{"t_s":161,"rss_mib":1005.83984375},{"t_s":164,"rss_mib":1005.88671875},{"t_s":164,"rss_mib":1005.88671875},{"t_s":166,"rss_mib":1005.90234375},{"t_s":167,"rss_mib":1005.90234375},{"t_s":170,"rss_mib":1005.921875},{"t_s":171,"rss_mib":1005.921875},{"t_s":173,"rss_mib":1006.11328125},{"t_s":174,"rss_mib":1006.1171875},{"t_s":176,"rss_mib":1006.15234375},{"t_s":177,"rss_mib":1006.15234375},{"t_s":180,"rss_mib":1006.15234375},{"t_s":183,"rss_mib":1006.15234375},{"t_s":184,"rss_mib":1006.09765625},{"t_s":186,"rss_mib":1006.10546875},{"t_s":186,"rss_mib":1006.109375},{"t_s":189,"rss_mib":1006.109375},{"t_s":191,"rss_mib":1006.26953125},{"t_s":192,"rss_mib":1006.26953125},{"t_s":193,"rss_mib":1006.31640625},{"t_s":195,"rss_mib":1006.31640625},{"t_s":198,"rss_mib":1006.51171875},{"t_s":198,"rss_mib":1006.51171875},{"t_s":201,"rss_mib":1006.5703125},{"t_s":202,"rss_mib":1006.578125},{"t_s":202,"rss_mib":1006.56640625},{"t_s":204,"rss_mib":1006.57421875},{"t_s":206,"rss_mib":1006.578125},{"t_s":207,"rss_mib":1006.578125},{"t_s":210,"rss_mib":1006.5859375},{"t_s":210,"rss_mib":1006.5859375},{"t_s":212,"rss_mib":1006.67578125},{"t_s":213,"rss_mib":1006.67578125},{"t_s":216,"rss_mib":1006.6875},{"t_s":216,"rss_mib":1006.6875},{"t_s":218,"rss_mib":1006.390625},{"t_s":219,"rss_mib":1006.390625},{"t_s":221,"rss_mib":1006.33203125},{"t_s":222,"rss_mib":1006.3359375},{"t_s":225,"rss_mib":1006.32421875},{"t_s":225,"rss_mib":1006.32421875},{"t_s":228,"rss_mib":1006.33203125},{"t_s":229,"rss_mib":1006.33203125},{"t_s":232,"rss_mib":1006.33203125},{"t_s":234,"rss_mib":1006.3203125},{"t_s":235,"rss_mib":1006.3203125},{"t_s":236,"rss_mib":1006.32421875},{"t_s":238,"rss_mib":1006.32421875},{"t_s":239,"rss_mib":1006.30078125},{"t_s":241,"rss_mib":1006.296875},{"t_s":243,"rss_mib":1006.40625},{"t_s":244,"rss_mib":1006.40625},{"t_s":246,"rss_mib":1006.6328125},{"t_s":247,"rss_mib":1006.62890625},{"t_s":250,"rss_mib":1006.6796875},{"t_s":250,"rss_mib":1006.6796875},{"t_s":252,"rss_mib":1006.63671875},{"t_s":255,"rss_mib":1006.6640625},{"t_s":255,"rss_mib":1006.23828125},{"t_s":256,"rss_mib":1006.2421875},{"t_s":258,"rss_mib":1006.26171875},{"t_s":259,"rss_mib":1006.26171875},{"t_s":261,"rss_mib":1006.27734375},{"t_s":262,"rss_mib":1006.27734375},{"t_s":264,"rss_mib":1006.2890625},{"t_s":265,"rss_mib":1006.2890625},{"t_s":268,"rss_mib":1006.2890625},{"t_s":271,"rss_mib":1006.171875},{"t_s":271,"rss_mib":1006.171875},{"t_s":272,"rss_mib":1006.13671875},{"t_s":274,"rss_mib":1006.14453125},{"t_s":276,"rss_mib":1006.15234375},{"t_s":279,"rss_mib":1006.12109375},{"t_s":279,"rss_mib":1006.1953125},{"t_s":280,"rss_mib":1006.1640625},{"t_s":283,"rss_mib":1006.21484375},{"t_s":286,"rss_mib":1006.15625},{"t_s":286,"rss_mib":1006.27734375},{"t_s":288,"rss_mib":1006.29296875},{"t_s":289,"rss_mib":1006.19140625},{"t_s":290,"rss_mib":1006.1953125},{"t_s":291,"rss_mib":1006.23046875},{"t_s":293,"rss_mib":1006.20703125},{"t_s":295,"rss_mib":1006.30078125},{"t_s":296,"rss_mib":1006.30078125},{"t_s":296,"rss_mib":1006.30859375},{"t_s":299,"rss_mib":1006.3125},{"t_s":299,"rss_mib":1006.25},{"t_s":302,"rss_mib":1006.25},{"t_s":304,"rss_mib":1006.21875},{"t_s":305,"rss_mib":1006.21875},{"t_s":306,"rss_mib":1006.22265625},{"t_s":308,"rss_mib":1006.22265625},{"t_s":311,"rss_mib":1006.22265625},{"t_s":314,"rss_mib":1006.22265625},{"t_s":317,"rss_mib":1006.22265625},{"t_s":320,"rss_mib":1006.22265625},{"t_s":323,"rss_mib":1006.22265625},{"t_s":326,"rss_mib":1006.22265625},{"t_s":329,"rss_mib":1006.22265625},{"t_s":332,"rss_mib":1006.22265625},{"t_s":335,"rss_mib":1006.22265625},{"t_s":338,"rss_mib":1006.22265625},{"t_s":341,"rss_mib":1006.22265625},{"t_s":345,"rss_mib":1006.22265625},{"t_s":348,"rss_mib":1006.22265625},{"t_s":351,"rss_mib":1006.22265625},{"t_s":354,"rss_mib":1006.22265625},{"t_s":357,"rss_mib":1006.22265625},{"t_s":360,"rss_mib":1006.22265625},{"t_s":363,"rss_mib":1006.22265625},{"t_s":366,"rss_mib":1006.22265625}],"idle_rss_series":[{"t_s":0,"rss_mib":598.72265625},{"t_s":0,"rss_mib":598.72265625},{"t_s":0,"rss_mib":598.72265625},{"t_s":1,"rss_mib":598.72265625},{"t_s":1,"rss_mib":598.72265625},{"t_s":2,"rss_mib":598.72265625},{"t_s":2,"rss_mib":598.72265625},{"t_s":3,"rss_mib":598.72265625},{"t_s":3,"rss_mib":598.72265625},{"t_s":4,"rss_mib":598.72265625},{"t_s":4,"rss_mib":598.72265625},{"t_s":5,"rss_mib":598.72265625},{"t_s":5,"rss_mib":598.72265625},{"t_s":6,"rss_mib":598.72265625},{"t_s":6,"rss_mib":598.80078125},{"t_s":6,"rss_mib":598.80078125},{"t_s":7,"rss_mib":598.80078125},{"t_s":7,"rss_mib":598.80078125},{"t_s":8,"rss_mib":598.80078125},{"t_s":8,"rss_mib":598.80078125},{"t_s":9,"rss_mib":598.80078125},{"t_s":9,"rss_mib":598.80078125},{"t_s":10,"rss_mib":598.80078125},{"t_s":11,"rss_mib":598.80078125},{"t_s":11,"rss_mib":598.80078125},{"t_s":11,"rss_mib":598.80078125},{"t_s":12,"rss_mib":598.80078125},{"t_s":12,"rss_mib":598.80078125},{"t_s":13,"rss_mib":598.80078125},{"t_s":13,"rss_mib":598.80078125},{"t_s":14,"rss_mib":598.80078125},{"t_s":15,"rss_mib":598.80078125},{"t_s":15,"rss_mib":598.80078125},{"t_s":15,"rss_mib":598.80078125},{"t_s":16,"rss_mib":598.80078125},{"t_s":16,"rss_mib":598.80078125},{"t_s":17,"rss_mib":598.80078125},{"t_s":17,"rss_mib":598.80078125},{"t_s":18,"rss_mib":598.80078125},{"t_s":18,"rss_mib":598.80078125},{"t_s":19,"rss_mib":598.80078125},{"t_s":19,"rss_mib":598.80078125},{"t_s":20,"rss_mib":598.80078125},{"t_s":20,"rss_mib":598.80078125},{"t_s":21,"rss_mib":598.80078125},{"t_s":22,"rss_mib":598.80078125},{"t_s":22,"rss_mib":598.80078125},{"t_s":22,"rss_mib":598.80078125},{"t_s":23,"rss_mib":598.80078125},{"t_s":23,"rss_mib":598.80078125},{"t_s":24,"rss_mib":598.80078125},{"t_s":24,"rss_mib":598.80078125},{"t_s":25,"rss_mib":598.80078125},{"t_s":26,"rss_mib":598.80078125},{"t_s":26,"rss_mib":598.80078125},{"t_s":26,"rss_mib":598.80078125},{"t_s":27,"rss_mib":598.80078125},{"t_s":27,"rss_mib":598.80078125},{"t_s":28,"rss_mib":598.80078125},{"t_s":28,"rss_mib":598.80078125},{"t_s":29,"rss_mib":598.80078125},{"t_s":30,"rss_mib":598.80078125},{"t_s":30,"rss_mib":598.80078125},{"t_s":30,"rss_mib":598.80078125},{"t_s":31,"rss_mib":598.80078125},{"t_s":31,"rss_mib":598.80078125},{"t_s":32,"rss_mib":598.80078125},{"t_s":33,"rss_mib":598.80078125},{"t_s":33,"rss_mib":598.80078125},{"t_s":33,"rss_mib":598.80078125},{"t_s":34,"rss_mib":598.80078125},{"t_s":34,"rss_mib":598.80078125},{"t_s":35,"rss_mib":598.80078125},{"t_s":35,"rss_mib":598.80078125},{"t_s":36,"rss_mib":598.80078125},{"t_s":37,"rss_mib":598.80078125},{"t_s":37,"rss_mib":598.80078125},{"t_s":37,"rss_mib":598.80078125},{"t_s":38,"rss_mib":598.80078125},{"t_s":38,"rss_mib":598.80078125},{"t_s":39,"rss_mib":598.80078125},{"t_s":39,"rss_mib":598.80078125},{"t_s":40,"rss_mib":598.80078125},{"t_s":41,"rss_mib":598.80078125},{"t_s":41,"rss_mib":598.80078125},{"t_s":41,"rss_mib":598.80078125},{"t_s":42,"rss_mib":598.80078125},{"t_s":42,"rss_mib":598.80078125},{"t_s":43,"rss_mib":598.80078125},{"t_s":44,"rss_mib":598.80078125},{"t_s":44,"rss_mib":598.80078125},{"t_s":44,"rss_mib":598.80078125},{"t_s":45,"rss_mib":598.80078125},{"t_s":45,"rss_mib":598.80078125},{"t_s":46,"rss_mib":598.80078125},{"t_s":46,"rss_mib":598.80078125},{"t_s":47,"rss_mib":598.80078125},{"t_s":48,"rss_mib":598.80078125},{"t_s":48,"rss_mib":598.80078125},{"t_s":48,"rss_mib":598.80078125},{"t_s":49,"rss_mib":598.80078125},{"t_s":49,"rss_mib":598.80078125},{"t_s":50,"rss_mib":598.80078125},{"t_s":50,"rss_mib":598.80078125},{"t_s":51,"rss_mib":598.80078125},{"t_s":52,"rss_mib":598.80078125},{"t_s":52,"rss_mib":598.80078125},{"t_s":52,"rss_mib":598.80078125},{"t_s":53,"rss_mib":598.80078125},{"t_s":53,"rss_mib":598.80078125},{"t_s":54,"rss_mib":598.80078125},{"t_s":54,"rss_mib":598.80078125},{"t_s":55,"rss_mib":598.80078125},{"t_s":56,"rss_mib":598.80078125},{"t_s":56,"rss_mib":598.80078125},{"t_s":56,"rss_mib":598.80078125},{"t_s":57,"rss_mib":598.80078125},{"t_s":57,"rss_mib":598.80078125},{"t_s":58,"rss_mib":598.80078125},{"t_s":59,"rss_mib":598.80078125},{"t_s":59,"rss_mib":598.8046875},{"t_s":59,"rss_mib":598.8046875},{"t_s":59,"rss_mib":598.8046875}],"idle_window_s":60,"recovery_window_s":30},"timings_s":{"added_latency":12.159955381,"cost":6.52951537,"memory":431.857555645,"streaming":0.000002439,"streams_sustained":0.00000222,"throughput":207.058530746},"upstream_transport":"http","absences":{"memory.idle_shape":{"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"memory.shape":{"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"perf.frontier.100ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.sweep.c256.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c256.w2.p99_us":{"reason":"not_measured"},"perf.sweep.c256.w3.p99_us":{"reason":"not_measured"},"stream.added_gap_p50_us":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_gap_p99_us":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_ttft_p50_us":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_ttft_p99_us":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.gap_direct_samples":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.gap_gw_samples":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_fps":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_headroom":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_mock_ceiling":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.ttft_direct_samples":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.ttft_gw_samples":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"}}},"cohere":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v2/chat","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"gemini":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1beta/models/amazon_bedrock/anthropic.claude-3-sonnet-20240229-v1:0:generateContent","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"openai-responses":{"served":true,"reason":null,"status":"","path":"/v1/responses","verdict_note":"","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":{"added_latency_p50_us":{"value":200013,"certified":true,"suppressed":false},"added_latency_p99_us":{"value":205956,"certified":true,"suppressed":false},"gateway_c1_p99_us":{"value":205984,"certified":true,"suppressed":false},"direct_c1_p99_us":{"value":28,"certified":true,"suppressed":false},"cpu_us_per_request":{"value":182500,"certified":true,"suppressed":false},"rps_per_cpu_second":{"value":5.47945205479452,"certified":true,"suppressed":false},"cost_window_conc":{"value":8,"certified":true,"suppressed":false},"cost_core_utilisation":{"value":0.8586890105703885,"certified":true,"suppressed":false},"cost_window_ok":{"value":116,"certified":true,"suppressed":false},"cost_window_rps":{"value":19,"certified":true,"suppressed":false},"cost_threads":{"value":68,"certified":true,"suppressed":false},"cost_nonvol_ctxt_per_request":{"value":4.620689655172414,"certified":true,"suppressed":false},"cost_majflt":{"value":0,"certified":true,"suppressed":false},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":20,"certified":true,"suppressed":false},"concurrency":16,"p99_us":1943615,"first_disqualified_conc":512,"lower_bound":false,"samples":121}],"sweep":[{"conc":1,"ok":28,"rps":4,"p99_us":212026,"fail":0},{"conc":1,"ok":29,"rps":4,"p99_us":207985,"fail":0},{"conc":1,"ok":28,"rps":4,"p99_us":218020,"fail":0},{"conc":2,"ok":32,"rps":5,"p99_us":385951,"fail":0},{"conc":2,"ok":32,"rps":5,"p99_us":393001,"fail":0},{"conc":2,"ok":30,"rps":4,"p99_us":395993,"fail":0},{"conc":4,"ok":61,"rps":10,"p99_us":558916,"fail":0},{"conc":4,"ok":61,"rps":10,"p99_us":558032,"fail":0},{"conc":4,"ok":63,"rps":10,"p99_us":607805,"fail":0},{"conc":8,"ok":93,"rps":15,"p99_us":731027,"fail":0},{"conc":8,"ok":93,"rps":15,"p99_us":733194,"fail":0},{"conc":8,"ok":91,"rps":15,"p99_us":826859,"fail":0},{"conc":16,"ok":123,"rps":20,"p99_us":2147034,"fail":0},{"conc":16,"ok":124,"rps":20,"p99_us":1746794,"fail":0},{"conc":16,"ok":121,"rps":20,"p99_us":1943615,"fail":0},{"conc":32,"ok":106,"rps":17,"p99_us":3356906,"fail":0},{"conc":32,"ok":106,"rps":17,"p99_us":4269675,"fail":0},{"conc":32,"ok":102,"rps":16,"p99_us":5084355,"fail":0},{"conc":64,"ok":82,"rps":13,"p99_us":5991674,"fail":0},{"conc":64,"ok":81,"rps":13,"p99_us":5204097,"fail":0},{"conc":64,"ok":76,"rps":12,"p99_us":5708432,"fail":0},{"conc":128,"ok":40,"rps":6,"p99_us":5928852,"fail":0},{"conc":128,"ok":28,"rps":4,"p99_us":5554539,"fail":0},{"conc":128,"ok":36,"rps":5,"p99_us":5907677,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":256,"ok":6,"rps":0.9997974693603026,"p99_us":3601620,"fail":0},{"conc":256,"ok":10,"rps":1,"p99_us":5617304,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0}],"rungs":[{"conc":1,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":212026,"windows":3,"clean_windows":3},{"conc":2,"rps":{"value":5,"certified":true,"suppressed":false},"p99_us":393001,"windows":3,"clean_windows":3},{"conc":4,"rps":{"value":10,"certified":true,"suppressed":false},"p99_us":558916,"windows":3,"clean_windows":3},{"conc":8,"rps":{"value":15,"certified":true,"suppressed":false},"p99_us":733194,"windows":3,"clean_windows":3},{"conc":16,"rps":{"value":20,"certified":true,"suppressed":false},"p99_us":1943615,"windows":3,"clean_windows":3},{"conc":32,"rps":{"value":17,"certified":true,"suppressed":false},"p99_us":4269675,"windows":3,"clean_windows":3},{"conc":64,"rps":{"value":13,"certified":true,"suppressed":false},"p99_us":5708432,"windows":3,"clean_windows":3},{"conc":128,"rps":{"value":5,"certified":true,"suppressed":false},"p99_us":5907677,"windows":3,"clean_windows":3},{"conc":256,"rps":{"value":0.9997974693603026,"certified":true,"suppressed":false},"p99_us":3601620,"windows":3,"clean_windows":2},{"conc":512,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"no window at c=512 was clean: 0 of 3 failed requests, the rest carried no usable rate or failure count"},"p99_us":null,"windows":3,"clean_windows":0}],"egress_reverified":true,"c1_note":"the c=1 percentiles are taken over 30 successful gateway round trip(s) and 265071 direct-to-mock round trip(s), each leg a single clean window with no failures","gateway_c1_samples":30,"direct_c1_samples":265071},"stream":{"stream_served":"untestable","stream_error":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","reason":"untestable","stream_c1_note":null,"added_ttft_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"added_ttft_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"streams_sustained_fps":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"streams_sustained":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"}},"memory":{"protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","served":true,"serve_error":"","load_recipe":null,"idle_rss_mib":{"value":621.60546875,"certified":true,"suppressed":false},"steady_state_rss_mib":{"value":1055.50390625,"certified":true,"suppressed":false},"recovered_rss_mib":{"value":1055.875,"certified":true,"suppressed":false},"peak_rss_mib":{"value":1055.9375,"certified":true,"suppressed":false},"peak_rss_hwm_mib":{"value":1055.87109375,"certified":true,"suppressed":false},"plateaued":true,"time_to_plateau_s":{"value":66,"certified":true,"suppressed":false},"growth_rate_mib_per_min":{"value":0.07183335358262208,"certified":true,"suppressed":false},"load_s":{"value":305,"certified":true,"suppressed":false},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"idle_static":{"value":1,"certified":true,"suppressed":false},"idle_growth_rate_mib_per_min":{"value":0.04844942521841008,"certified":true,"suppressed":false},"rss_series":[{"t_s":0,"rss_mib":622.1171875},{"t_s":2,"rss_mib":1052.125},{"t_s":2,"rss_mib":1052.125},{"t_s":5,"rss_mib":1052.26953125},{"t_s":6,"rss_mib":1052.26953125},{"t_s":8,"rss_mib":1052.85546875},{"t_s":9,"rss_mib":1052.85546875},{"t_s":11,"rss_mib":1053.03515625},{"t_s":12,"rss_mib":1053.0390625},{"t_s":14,"rss_mib":1053.3984375},{"t_s":15,"rss_mib":1053.3984375},{"t_s":16,"rss_mib":1053.49609375},{"t_s":19,"rss_mib":1053.4765625},{"t_s":21,"rss_mib":1053.6796875},{"t_s":21,"rss_mib":1053.6796875},{"t_s":23,"rss_mib":1053.8125},{"t_s":24,"rss_mib":1053.82421875},{"t_s":27,"rss_mib":1053.96875},{"t_s":27,"rss_mib":1053.94140625},{"t_s":29,"rss_mib":1054.01171875},{"t_s":30,"rss_mib":1054.01953125},{"t_s":31,"rss_mib":1054.046875},{"t_s":33,"rss_mib":1054.046875},{"t_s":36,"rss_mib":1054.375},{"t_s":36,"rss_mib":1054.375},{"t_s":39,"rss_mib":1054.61328125},{"t_s":39,"rss_mib":1054.6171875},{"t_s":42,"rss_mib":1054.66796875},{"t_s":42,"rss_mib":1054.66796875},{"t_s":45,"rss_mib":1054.6953125},{"t_s":47,"rss_mib":1054.765625},{"t_s":48,"rss_mib":1054.65625},{"t_s":50,"rss_mib":1054.67578125},{"t_s":50,"rss_mib":1054.625},{"t_s":51,"rss_mib":1054.625},{"t_s":53,"rss_mib":1054.78125},{"t_s":54,"rss_mib":1054.78515625},{"t_s":57,"rss_mib":1054.953125},{"t_s":59,"rss_mib":1054.9609375},{"t_s":60,"rss_mib":1054.8671875},{"t_s":61,"rss_mib":1054.890625},{"t_s":61,"rss_mib":1054.703125},{"t_s":64,"rss_mib":1054.76171875},{"t_s":66,"rss_mib":1054.703125},{"t_s":67,"rss_mib":1054.703125},{"t_s":69,"rss_mib":1054.40625},{"t_s":71,"rss_mib":1054.43359375},{"t_s":72,"rss_mib":1054.3984375},{"t_s":73,"rss_mib":1054.3984375},{"t_s":76,"rss_mib":1054.5390625},{"t_s":76,"rss_mib":1054.5390625},{"t_s":77,"rss_mib":1054.5859375},{"t_s":79,"rss_mib":1054.5859375},{"t_s":82,"rss_mib":1054.671875},{"t_s":82,"rss_mib":1054.671875},{"t_s":85,"rss_mib":1054.69140625},{"t_s":85,"rss_mib":1054.69140625},{"t_s":88,"rss_mib":1054.90625},{"t_s":88,"rss_mib":1054.90625},{"t_s":91,"rss_mib":1054.98828125},{"t_s":91,"rss_mib":1054.98828125},{"t_s":94,"rss_mib":1055.07421875},{"t_s":94,"rss_mib":1054.9765625},{"t_s":97,"rss_mib":1055.01171875},{"t_s":99,"rss_mib":1055.0078125},{"t_s":99,"rss_mib":1055.0234375},{"t_s":100,"rss_mib":1055.0234375},{"t_s":103,"rss_mib":1055.125},{"t_s":103,"rss_mib":1055.1328125},{"t_s":106,"rss_mib":1055.1796875},{"t_s":106,"rss_mib":1055.171875},{"t_s":109,"rss_mib":1055.20703125},{"t_s":109,"rss_mib":1055.2109375},{"t_s":111,"rss_mib":1055.203125},{"t_s":112,"rss_mib":1055.203125},{"t_s":115,"rss_mib":1055.234375},{"t_s":116,"rss_mib":1055.25},{"t_s":117,"rss_mib":1055.0546875},{"t_s":119,"rss_mib":1055.109375},{"t_s":119,"rss_mib":1055.0625},{"t_s":122,"rss_mib":1055.09375},{"t_s":124,"rss_mib":1055.09765625},{"t_s":125,"rss_mib":1055.09765625},{"t_s":127,"rss_mib":1055.1640625},{"t_s":128,"rss_mib":1055.1640625},{"t_s":129,"rss_mib":1055.1796875},{"t_s":131,"rss_mib":1055.1796875},{"t_s":133,"rss_mib":1055.26171875},{"t_s":136,"rss_mib":1055.2890625},{"t_s":137,"rss_mib":1055.1640625},{"t_s":137,"rss_mib":1055.1640625},{"t_s":139,"rss_mib":1055.234375},{"t_s":140,"rss_mib":1055.234375},{"t_s":143,"rss_mib":1055.2734375},{"t_s":143,"rss_mib":1055.2734375},{"t_s":146,"rss_mib":1055.265625},{"t_s":146,"rss_mib":1055.3515625},{"t_s":149,"rss_mib":1055.45703125},{"t_s":149,"rss_mib":1055.45703125},{"t_s":149,"rss_mib":1055.484375},{"t_s":152,"rss_mib":1055.484375},{"t_s":154,"rss_mib":1055.57421875},{"t_s":155,"rss_mib":1055.57421875},{"t_s":158,"rss_mib":1055.625},{"t_s":158,"rss_mib":1055.64453125},{"t_s":159,"rss_mib":1055.65625},{"t_s":162,"rss_mib":1055.66015625},{"t_s":163,"rss_mib":1055.62109375},{"t_s":164,"rss_mib":1055.62109375},{"t_s":166,"rss_mib":1055.46484375},{"t_s":168,"rss_mib":1055.515625},{"t_s":169,"rss_mib":1055.4375},{"t_s":171,"rss_mib":1055.43359375},{"t_s":173,"rss_mib":1055.5234375},{"t_s":176,"rss_mib":1055.5390625},{"t_s":176,"rss_mib":1055.3515625},{"t_s":176,"rss_mib":1055.3515625},{"t_s":177,"rss_mib":1055.12109375},{"t_s":179,"rss_mib":1055.1328125},{"t_s":180,"rss_mib":1055.13671875},{"t_s":184,"rss_mib":1055.140625},{"t_s":185,"rss_mib":1054.9765625},{"t_s":186,"rss_mib":1054.9765625},{"t_s":188,"rss_mib":1055.0078125},{"t_s":189,"rss_mib":1055.0078125},{"t_s":191,"rss_mib":1055.03515625},{"t_s":192,"rss_mib":1055.03515625},{"t_s":194,"rss_mib":1055.28125},{"t_s":195,"rss_mib":1055.2890625},{"t_s":196,"rss_mib":1055.23046875},{"t_s":198,"rss_mib":1055.21484375},{"t_s":200,"rss_mib":1055.25},{"t_s":202,"rss_mib":1055.26171875},{"t_s":203,"rss_mib":1055.22265625},{"t_s":204,"rss_mib":1055.2265625},{"t_s":206,"rss_mib":1055.25390625},{"t_s":207,"rss_mib":1055.2421875},{"t_s":209,"rss_mib":1055.265625},{"t_s":210,"rss_mib":1055.265625},{"t_s":211,"rss_mib":1055.08984375},{"t_s":213,"rss_mib":1055.1796875},{"t_s":216,"rss_mib":1055.2421875},{"t_s":216,"rss_mib":1055.25},{"t_s":217,"rss_mib":1055.16796875},{"t_s":219,"rss_mib":1055.25390625},{"t_s":221,"rss_mib":1055.30078125},{"t_s":222,"rss_mib":1055.30078125},{"t_s":225,"rss_mib":1055.30078125},{"t_s":228,"rss_mib":1055.3125},{"t_s":228,"rss_mib":1055.3125},{"t_s":229,"rss_mib":1055.3203125},{"t_s":232,"rss_mib":1055.30078125},{"t_s":234,"rss_mib":1055.359375},{"t_s":234,"rss_mib":1055.36328125},{"t_s":235,"rss_mib":1055.3828125},{"t_s":237,"rss_mib":1055.37109375},{"t_s":240,"rss_mib":1055.41796875},{"t_s":240,"rss_mib":1055.41796875},{"t_s":242,"rss_mib":1055.44140625},{"t_s":246,"rss_mib":1055.41015625},{"t_s":246,"rss_mib":1055.65234375},{"t_s":247,"rss_mib":1055.65625},{"t_s":250,"rss_mib":1055.7890625},{"t_s":252,"rss_mib":1055.7734375},{"t_s":253,"rss_mib":1055.8359375},{"t_s":253,"rss_mib":1055.8359375},{"t_s":254,"rss_mib":1055.83984375},{"t_s":256,"rss_mib":1055.83984375},{"t_s":256,"rss_mib":1055.84375},{"t_s":259,"rss_mib":1055.84375},{"t_s":262,"rss_mib":1055.765625},{"t_s":262,"rss_mib":1055.76953125},{"t_s":266,"rss_mib":1055.7734375},{"t_s":266,"rss_mib":1055.68359375},{"t_s":268,"rss_mib":1055.68359375},{"t_s":270,"rss_mib":1055.70703125},{"t_s":271,"rss_mib":1055.70703125},{"t_s":273,"rss_mib":1055.66015625},{"t_s":274,"rss_mib":1055.66015625},{"t_s":277,"rss_mib":1055.66015625},{"t_s":277,"rss_mib":1055.5234375},{"t_s":280,"rss_mib":1055.5859375},{"t_s":283,"rss_mib":1055.69921875},{"t_s":284,"rss_mib":1055.7265625},{"t_s":285,"rss_mib":1055.61328125},{"t_s":286,"rss_mib":1055.640625},{"t_s":288,"rss_mib":1055.6484375},{"t_s":291,"rss_mib":1055.6640625},{"t_s":292,"rss_mib":1055.453125},{"t_s":292,"rss_mib":1055.83203125},{"t_s":295,"rss_mib":1055.92578125},{"t_s":295,"rss_mib":1055.92578125},{"t_s":297,"rss_mib":1055.9375},{"t_s":298,"rss_mib":1055.9375},{"t_s":299,"rss_mib":1055.8671875},{"t_s":301,"rss_mib":1055.875},{"t_s":304,"rss_mib":1055.87109375},{"t_s":305,"rss_mib":1055.87109375},{"t_s":306,"rss_mib":1055.875},{"t_s":308,"rss_mib":1055.875},{"t_s":311,"rss_mib":1055.875},{"t_s":314,"rss_mib":1055.875},{"t_s":317,"rss_mib":1055.875},{"t_s":320,"rss_mib":1055.875},{"t_s":323,"rss_mib":1055.875},{"t_s":326,"rss_mib":1055.875},{"t_s":329,"rss_mib":1055.875},{"t_s":332,"rss_mib":1055.875},{"t_s":335,"rss_mib":1055.875},{"t_s":338,"rss_mib":1055.875},{"t_s":341,"rss_mib":1055.875},{"t_s":344,"rss_mib":1055.875},{"t_s":347,"rss_mib":1055.875},{"t_s":350,"rss_mib":1055.875},{"t_s":353,"rss_mib":1055.875},{"t_s":356,"rss_mib":1055.875},{"t_s":357,"rss_mib":1055.87890625},{"t_s":359,"rss_mib":1055.87890625},{"t_s":362,"rss_mib":1055.87890625},{"t_s":365,"rss_mib":1055.87890625}],"idle_rss_series":[{"t_s":0,"rss_mib":621.52734375},{"t_s":0,"rss_mib":621.52734375},{"t_s":0,"rss_mib":621.52734375},{"t_s":1,"rss_mib":621.52734375},{"t_s":1,"rss_mib":621.52734375},{"t_s":2,"rss_mib":621.52734375},{"t_s":2,"rss_mib":621.52734375},{"t_s":3,"rss_mib":621.52734375},{"t_s":4,"rss_mib":621.52734375},{"t_s":4,"rss_mib":621.52734375},{"t_s":4,"rss_mib":621.52734375},{"t_s":5,"rss_mib":621.52734375},{"t_s":5,"rss_mib":621.52734375},{"t_s":6,"rss_mib":621.52734375},{"t_s":6,"rss_mib":621.60546875},{"t_s":6,"rss_mib":621.60546875},{"t_s":7,"rss_mib":621.60546875},{"t_s":8,"rss_mib":621.60546875},{"t_s":8,"rss_mib":621.60546875},{"t_s":8,"rss_mib":621.60546875},{"t_s":9,"rss_mib":621.60546875},{"t_s":9,"rss_mib":621.60546875},{"t_s":10,"rss_mib":621.60546875},{"t_s":10,"rss_mib":621.60546875},{"t_s":11,"rss_mib":621.60546875},{"t_s":12,"rss_mib":621.60546875},{"t_s":12,"rss_mib":621.60546875},{"t_s":12,"rss_mib":621.60546875},{"t_s":13,"rss_mib":621.60546875},{"t_s":13,"rss_mib":621.60546875},{"t_s":14,"rss_mib":621.60546875},{"t_s":14,"rss_mib":621.60546875},{"t_s":15,"rss_mib":621.60546875},{"t_s":16,"rss_mib":621.60546875},{"t_s":16,"rss_mib":621.60546875},{"t_s":16,"rss_mib":621.60546875},{"t_s":17,"rss_mib":621.60546875},{"t_s":17,"rss_mib":621.60546875},{"t_s":18,"rss_mib":621.60546875},{"t_s":18,"rss_mib":621.60546875},{"t_s":19,"rss_mib":621.60546875},{"t_s":20,"rss_mib":621.60546875},{"t_s":20,"rss_mib":621.60546875},{"t_s":20,"rss_mib":621.60546875},{"t_s":21,"rss_mib":621.60546875},{"t_s":21,"rss_mib":621.60546875},{"t_s":22,"rss_mib":621.60546875},{"t_s":22,"rss_mib":621.60546875},{"t_s":23,"rss_mib":621.60546875},{"t_s":24,"rss_mib":621.60546875},{"t_s":24,"rss_mib":621.60546875},{"t_s":24,"rss_mib":621.60546875},{"t_s":25,"rss_mib":621.60546875},{"t_s":25,"rss_mib":621.60546875},{"t_s":26,"rss_mib":621.60546875},{"t_s":26,"rss_mib":621.60546875},{"t_s":27,"rss_mib":621.60546875},{"t_s":28,"rss_mib":621.60546875},{"t_s":28,"rss_mib":621.60546875},{"t_s":28,"rss_mib":621.60546875},{"t_s":29,"rss_mib":621.60546875},{"t_s":29,"rss_mib":621.60546875},{"t_s":30,"rss_mib":621.60546875},{"t_s":30,"rss_mib":621.60546875},{"t_s":31,"rss_mib":621.60546875},{"t_s":32,"rss_mib":621.60546875},{"t_s":32,"rss_mib":621.60546875},{"t_s":32,"rss_mib":621.60546875},{"t_s":33,"rss_mib":621.60546875},{"t_s":33,"rss_mib":621.60546875},{"t_s":34,"rss_mib":621.60546875},{"t_s":35,"rss_mib":621.60546875},{"t_s":35,"rss_mib":621.60546875},{"t_s":36,"rss_mib":621.60546875},{"t_s":36,"rss_mib":621.60546875},{"t_s":36,"rss_mib":621.60546875},{"t_s":37,"rss_mib":621.60546875},{"t_s":37,"rss_mib":621.60546875},{"t_s":38,"rss_mib":621.60546875},{"t_s":39,"rss_mib":621.60546875},{"t_s":39,"rss_mib":621.60546875},{"t_s":40,"rss_mib":621.60546875},{"t_s":40,"rss_mib":621.60546875},{"t_s":40,"rss_mib":621.60546875},{"t_s":41,"rss_mib":621.60546875},{"t_s":41,"rss_mib":621.60546875},{"t_s":42,"rss_mib":621.60546875},{"t_s":43,"rss_mib":621.60546875},{"t_s":43,"rss_mib":621.60546875},{"t_s":44,"rss_mib":621.60546875},{"t_s":44,"rss_mib":621.60546875},{"t_s":44,"rss_mib":621.60546875},{"t_s":45,"rss_mib":621.60546875},{"t_s":45,"rss_mib":621.60546875},{"t_s":46,"rss_mib":621.60546875},{"t_s":47,"rss_mib":621.60546875},{"t_s":47,"rss_mib":621.60546875},{"t_s":48,"rss_mib":621.60546875},{"t_s":48,"rss_mib":621.60546875},{"t_s":48,"rss_mib":621.60546875},{"t_s":49,"rss_mib":621.60546875},{"t_s":50,"rss_mib":621.60546875},{"t_s":50,"rss_mib":621.60546875},{"t_s":51,"rss_mib":621.60546875},{"t_s":51,"rss_mib":621.60546875},{"t_s":52,"rss_mib":621.60546875},{"t_s":52,"rss_mib":621.60546875},{"t_s":52,"rss_mib":621.60546875},{"t_s":53,"rss_mib":621.60546875},{"t_s":53,"rss_mib":621.609375},{"t_s":54,"rss_mib":621.609375},{"t_s":54,"rss_mib":621.609375},{"t_s":55,"rss_mib":621.609375},{"t_s":55,"rss_mib":621.609375},{"t_s":56,"rss_mib":621.609375},{"t_s":56,"rss_mib":621.609375},{"t_s":56,"rss_mib":621.609375},{"t_s":57,"rss_mib":621.609375},{"t_s":58,"rss_mib":621.609375},{"t_s":58,"rss_mib":621.609375},{"t_s":59,"rss_mib":621.609375},{"t_s":59,"rss_mib":621.609375},{"t_s":59,"rss_mib":621.609375}],"idle_window_s":60,"recovery_window_s":30},"timings_s":{"added_latency":12.178760031,"cost":6.177534086,"memory":431.396226585,"streaming":0.000001944,"streams_sustained":0.000001697,"throughput":281.430826698},"upstream_transport":"http","absences":{"memory.idle_shape":{"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"memory.shape":{"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"perf.frontier.100ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.sweep.c256.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w2.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w3.p99_us":{"reason":"not_measured"},"stream.added_gap_p50_us":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_gap_p99_us":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_ttft_p50_us":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_ttft_p99_us":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.gap_direct_samples":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.gap_gw_samples":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_fps":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_headroom":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_mock_ceiling":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.ttft_direct_samples":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.ttft_gw_samples":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"}}},"anthropic":{"served":true,"reason":null,"status":"","path":"/v1/messages","verdict_note":"","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":{"added_latency_p50_us":{"value":193978,"certified":true,"suppressed":false},"added_latency_p99_us":{"value":197949,"certified":true,"suppressed":false},"gateway_c1_p99_us":{"value":197977,"certified":true,"suppressed":false},"direct_c1_p99_us":{"value":28,"certified":true,"suppressed":false},"cpu_us_per_request":{"value":175360,"certified":true,"suppressed":false},"rps_per_cpu_second":{"value":5.702554744525547,"certified":true,"suppressed":false},"cost_window_conc":{"value":8,"certified":true,"suppressed":false},"cost_core_utilisation":{"value":0.8601191828446305,"certified":true,"suppressed":false},"cost_window_ok":{"value":125,"certified":true,"suppressed":false},"cost_window_rps":{"value":20,"certified":true,"suppressed":false},"cost_threads":{"value":68,"certified":true,"suppressed":false},"cost_nonvol_ctxt_per_request":{"value":5.32,"certified":true,"suppressed":false},"cost_majflt":{"value":0,"certified":true,"suppressed":false},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false},"concurrency":16,"p99_us":1585939,"first_disqualified_conc":1024,"lower_bound":false,"samples":127}],"sweep":[{"conc":1,"ok":30,"rps":4,"p99_us":205978,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":206979,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":200004,"fail":0},{"conc":2,"ok":34,"rps":5,"p99_us":368025,"fail":0},{"conc":2,"ok":34,"rps":5,"p99_us":371000,"fail":0},{"conc":2,"ok":34,"rps":5,"p99_us":354993,"fail":0},{"conc":4,"ok":58,"rps":9,"p99_us":960596,"fail":0},{"conc":4,"ok":62,"rps":10,"p99_us":522149,"fail":0},{"conc":4,"ok":62,"rps":10,"p99_us":534149,"fail":0},{"conc":8,"ok":121,"rps":20,"p99_us":987009,"fail":0},{"conc":8,"ok":121,"rps":20,"p99_us":671891,"fail":0},{"conc":8,"ok":123,"rps":20,"p99_us":683777,"fail":0},{"conc":16,"ok":123,"rps":20,"p99_us":2142735,"fail":0},{"conc":16,"ok":123,"rps":20,"p99_us":1639087,"fail":0},{"conc":16,"ok":127,"rps":21,"p99_us":1585939,"fail":0},{"conc":32,"ok":107,"rps":17,"p99_us":3671203,"fail":0},{"conc":32,"ok":106,"rps":17,"p99_us":4004485,"fail":0},{"conc":32,"ok":106,"rps":17,"p99_us":4513090,"fail":0},{"conc":64,"ok":80,"rps":13,"p99_us":5310882,"fail":0},{"conc":64,"ok":83,"rps":13,"p99_us":5682467,"fail":0},{"conc":64,"ok":83,"rps":13,"p99_us":5898653,"fail":0},{"conc":128,"ok":21,"rps":3,"p99_us":5974875,"fail":0},{"conc":128,"ok":40,"rps":6,"p99_us":5769229,"fail":0},{"conc":128,"ok":39,"rps":6,"p99_us":5983954,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":256,"ok":7,"rps":1,"p99_us":5746061,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":6,"rps":0.9998286480331953,"p99_us":5162460,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":1024,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":1024,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":1024,"ok":0,"rps":0,"p99_us":null,"fail":0}],"rungs":[{"conc":1,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":205978,"windows":3,"clean_windows":3},{"conc":2,"rps":{"value":5,"certified":true,"suppressed":false},"p99_us":368025,"windows":3,"clean_windows":3},{"conc":4,"rps":{"value":10,"certified":true,"suppressed":false},"p99_us":534149,"windows":3,"clean_windows":3},{"conc":8,"rps":{"value":20,"certified":true,"suppressed":false},"p99_us":683777,"windows":3,"clean_windows":3},{"conc":16,"rps":{"value":20,"certified":true,"suppressed":false},"p99_us":1639087,"windows":3,"clean_windows":3},{"conc":32,"rps":{"value":17,"certified":true,"suppressed":false},"p99_us":4004485,"windows":3,"clean_windows":3},{"conc":64,"rps":{"value":13,"certified":true,"suppressed":false},"p99_us":5682467,"windows":3,"clean_windows":3},{"conc":128,"rps":{"value":6,"certified":true,"suppressed":false},"p99_us":5974875,"windows":3,"clean_windows":3},{"conc":256,"rps":{"value":1,"certified":true,"suppressed":false},"p99_us":5746061,"windows":3,"clean_windows":1},{"conc":512,"rps":{"value":0.9998286480331953,"certified":true,"suppressed":false},"p99_us":5162460,"windows":3,"clean_windows":1},{"conc":1024,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"no window at c=1024 was clean: 0 of 3 failed requests, the rest carried no usable rate or failure count"},"p99_us":null,"windows":3,"clean_windows":0}],"egress_reverified":true,"c1_note":"the c=1 percentiles are taken over 31 successful gateway round trip(s) and 259772 direct-to-mock round trip(s), each leg a single clean window with no failures","gateway_c1_samples":31,"direct_c1_samples":259772},"stream":{"stream_served":"untestable","stream_error":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","reason":"untestable","stream_c1_note":null,"added_ttft_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"added_ttft_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"streams_sustained_fps":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"streams_sustained":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"}},"memory":{"protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","served":true,"serve_error":"","load_recipe":null,"idle_rss_mib":{"value":612.45703125,"certified":true,"suppressed":false},"steady_state_rss_mib":{"value":967.6796875,"certified":true,"suppressed":false},"recovered_rss_mib":{"value":967.421875,"certified":true,"suppressed":false},"peak_rss_mib":{"value":967.99609375,"certified":true,"suppressed":false},"peak_rss_hwm_mib":{"value":967.70703125,"certified":true,"suppressed":false},"plateaued":true,"time_to_plateau_s":{"value":60,"certified":true,"suppressed":false},"growth_rate_mib_per_min":{"value":0.25204829296188547,"certified":true,"suppressed":false},"load_s":{"value":302,"certified":true,"suppressed":false},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"idle_static":{"value":1,"certified":true,"suppressed":false},"idle_growth_rate_mib_per_min":{"value":0.05193333183537614,"certified":true,"suppressed":false},"rss_series":[{"t_s":0,"rss_mib":612.9765625},{"t_s":2,"rss_mib":963.953125},{"t_s":2,"rss_mib":963.9609375},{"t_s":5,"rss_mib":964.15625},{"t_s":5,"rss_mib":964.15625},{"t_s":8,"rss_mib":964.8984375},{"t_s":9,"rss_mib":964.90234375},{"t_s":11,"rss_mib":965.10546875},{"t_s":13,"rss_mib":965.06640625},{"t_s":14,"rss_mib":965.24609375},{"t_s":15,"rss_mib":965.24609375},{"t_s":17,"rss_mib":965.33984375},{"t_s":18,"rss_mib":965.33984375},{"t_s":20,"rss_mib":965.49609375},{"t_s":21,"rss_mib":965.49609375},{"t_s":23,"rss_mib":965.60546875},{"t_s":24,"rss_mib":965.546875},{"t_s":26,"rss_mib":965.609375},{"t_s":27,"rss_mib":965.6484375},{"t_s":30,"rss_mib":965.7421875},{"t_s":30,"rss_mib":965.75},{"t_s":32,"rss_mib":965.796875},{"t_s":33,"rss_mib":965.7734375},{"t_s":35,"rss_mib":965.875},{"t_s":37,"rss_mib":965.91796875},{"t_s":38,"rss_mib":965.87109375},{"t_s":39,"rss_mib":965.89453125},{"t_s":42,"rss_mib":966.265625},{"t_s":42,"rss_mib":966.2734375},{"t_s":44,"rss_mib":966.42578125},{"t_s":45,"rss_mib":966.42578125},{"t_s":48,"rss_mib":966.484375},{"t_s":48,"rss_mib":966.484375},{"t_s":51,"rss_mib":966.53515625},{"t_s":51,"rss_mib":966.53515625},{"t_s":54,"rss_mib":966.78125},{"t_s":54,"rss_mib":966.78125},{"t_s":57,"rss_mib":966.8671875},{"t_s":57,"rss_mib":966.8671875},{"t_s":59,"rss_mib":966.875},{"t_s":60,"rss_mib":966.87109375},{"t_s":62,"rss_mib":966.91796875},{"t_s":63,"rss_mib":966.91796875},{"t_s":65,"rss_mib":966.9453125},{"t_s":66,"rss_mib":966.953125},{"t_s":68,"rss_mib":966.9765625},{"t_s":69,"rss_mib":966.9765625},{"t_s":72,"rss_mib":967.0078125},{"t_s":74,"rss_mib":966.984375},{"t_s":75,"rss_mib":967.296875},{"t_s":75,"rss_mib":967.27734375},{"t_s":77,"rss_mib":967.34765625},{"t_s":78,"rss_mib":967.34765625},{"t_s":79,"rss_mib":967.28125},{"t_s":81,"rss_mib":967.28125},{"t_s":82,"rss_mib":967.234375},{"t_s":84,"rss_mib":967.234375},{"t_s":86,"rss_mib":967.23828125},{"t_s":87,"rss_mib":967.23828125},{"t_s":89,"rss_mib":967.25390625},{"t_s":91,"rss_mib":967.265625},{"t_s":91,"rss_mib":967.18359375},{"t_s":93,"rss_mib":967.1953125},{"t_s":96,"rss_mib":967.22265625},{"t_s":96,"rss_mib":967.19921875},{"t_s":99,"rss_mib":967.234375},{"t_s":99,"rss_mib":967.23828125},{"t_s":100,"rss_mib":966.96484375},{"t_s":102,"rss_mib":967.07421875},{"t_s":103,"rss_mib":967.09375},{"t_s":106,"rss_mib":967.1015625},{"t_s":108,"rss_mib":966.984375},{"t_s":108,"rss_mib":967.1015625},{"t_s":111,"rss_mib":967.13671875},{"t_s":111,"rss_mib":967.13671875},{"t_s":114,"rss_mib":967.140625},{"t_s":114,"rss_mib":967.140625},{"t_s":117,"rss_mib":967.2109375},{"t_s":118,"rss_mib":967.21484375},{"t_s":118,"rss_mib":967.1875},{"t_s":120,"rss_mib":967.20703125},{"t_s":121,"rss_mib":967.2421875},{"t_s":123,"rss_mib":967.2421875},{"t_s":126,"rss_mib":967.30078125},{"t_s":126,"rss_mib":967.30078125},{"t_s":128,"rss_mib":967.3671875},{"t_s":129,"rss_mib":967.3671875},{"t_s":130,"rss_mib":967.37109375},{"t_s":132,"rss_mib":967.37109375},{"t_s":135,"rss_mib":967.5},{"t_s":137,"rss_mib":967.58984375},{"t_s":138,"rss_mib":967.48828125},{"t_s":138,"rss_mib":967.515625},{"t_s":140,"rss_mib":967.53125},{"t_s":142,"rss_mib":967.56640625},{"t_s":143,"rss_mib":967.4609375},{"t_s":147,"rss_mib":967.4921875},{"t_s":147,"rss_mib":967.22265625},{"t_s":148,"rss_mib":967.22265625},{"t_s":150,"rss_mib":967.4921875},{"t_s":150,"rss_mib":967.5078125},{"t_s":152,"rss_mib":967.61328125},{"t_s":154,"rss_mib":967.53125},{"t_s":156,"rss_mib":967.7109375},{"t_s":157,"rss_mib":967.7109375},{"t_s":157,"rss_mib":967.73828125},{"t_s":160,"rss_mib":967.73828125},{"t_s":161,"rss_mib":967.56640625},{"t_s":163,"rss_mib":967.56640625},{"t_s":165,"rss_mib":967.578125},{"t_s":166,"rss_mib":967.578125},{"t_s":167,"rss_mib":967.3515625},{"t_s":169,"rss_mib":967.5546875},{"t_s":171,"rss_mib":967.6484375},{"t_s":172,"rss_mib":967.65625},{"t_s":172,"rss_mib":967.62109375},{"t_s":175,"rss_mib":967.62109375},{"t_s":177,"rss_mib":967.640625},{"t_s":178,"rss_mib":967.640625},{"t_s":180,"rss_mib":967.68359375},{"t_s":181,"rss_mib":967.68359375},{"t_s":184,"rss_mib":967.68359375},{"t_s":186,"rss_mib":967.6875},{"t_s":188,"rss_mib":967.59765625},{"t_s":188,"rss_mib":967.84375},{"t_s":190,"rss_mib":967.84375},{"t_s":192,"rss_mib":967.8984375},{"t_s":193,"rss_mib":967.8984375},{"t_s":195,"rss_mib":967.92578125},{"t_s":196,"rss_mib":967.92578125},{"t_s":199,"rss_mib":967.95703125},{"t_s":199,"rss_mib":967.95703125},{"t_s":202,"rss_mib":967.99609375},{"t_s":202,"rss_mib":967.99609375},{"t_s":204,"rss_mib":967.54296875},{"t_s":205,"rss_mib":967.54296875},{"t_s":206,"rss_mib":967.546875},{"t_s":208,"rss_mib":967.546875},{"t_s":210,"rss_mib":967.58203125},{"t_s":212,"rss_mib":967.62890625},{"t_s":213,"rss_mib":967.5625},{"t_s":215,"rss_mib":967.50390625},{"t_s":217,"rss_mib":967.96875},{"t_s":217,"rss_mib":967.96875},{"t_s":217,"rss_mib":967.78515625},{"t_s":220,"rss_mib":967.8046875},{"t_s":222,"rss_mib":967.8359375},{"t_s":223,"rss_mib":967.8359375},{"t_s":226,"rss_mib":967.83984375},{"t_s":227,"rss_mib":967.69140625},{"t_s":229,"rss_mib":967.69140625},{"t_s":232,"rss_mib":967.640625},{"t_s":233,"rss_mib":967.65234375},{"t_s":234,"rss_mib":967.51171875},{"t_s":235,"rss_mib":967.578125},{"t_s":238,"rss_mib":967.59375},{"t_s":238,"rss_mib":967.59375},{"t_s":238,"rss_mib":967.28515625},{"t_s":241,"rss_mib":967.28515625},{"t_s":244,"rss_mib":967.5390625},{"t_s":244,"rss_mib":967.5390625},{"t_s":246,"rss_mib":967.58984375},{"t_s":247,"rss_mib":967.58984375},{"t_s":248,"rss_mib":967.45703125},{"t_s":250,"rss_mib":967.45703125},{"t_s":254,"rss_mib":967.3203125},{"t_s":256,"rss_mib":967.6015625},{"t_s":258,"rss_mib":967.64453125},{"t_s":258,"rss_mib":967.59765625},{"t_s":261,"rss_mib":967.52734375},{"t_s":262,"rss_mib":967.66015625},{"t_s":262,"rss_mib":967.6796875},{"t_s":264,"rss_mib":967.734375},{"t_s":265,"rss_mib":967.734375},{"t_s":268,"rss_mib":967.7578125},{"t_s":268,"rss_mib":967.7578125},{"t_s":271,"rss_mib":967.80078125},{"t_s":272,"rss_mib":967.80859375},{"t_s":273,"rss_mib":967.765625},{"t_s":274,"rss_mib":967.7734375},{"t_s":277,"rss_mib":967.7890625},{"t_s":278,"rss_mib":967.80078125},{"t_s":280,"rss_mib":967.51171875},{"t_s":280,"rss_mib":967.515625},{"t_s":283,"rss_mib":967.54296875},{"t_s":283,"rss_mib":967.54296875},{"t_s":286,"rss_mib":967.74609375},{"t_s":288,"rss_mib":967.72265625},{"t_s":288,"rss_mib":967.86328125},{"t_s":291,"rss_mib":967.8828125},{"t_s":291,"rss_mib":967.65234375},{"t_s":293,"rss_mib":967.66796875},{"t_s":295,"rss_mib":967.7109375},{"t_s":296,"rss_mib":967.7109375},{"t_s":298,"rss_mib":967.74609375},{"t_s":299,"rss_mib":967.75},{"t_s":301,"rss_mib":967.421875},{"t_s":302,"rss_mib":967.421875},{"t_s":305,"rss_mib":967.421875},{"t_s":308,"rss_mib":967.421875},{"t_s":311,"rss_mib":967.421875},{"t_s":314,"rss_mib":967.421875},{"t_s":317,"rss_mib":967.421875},{"t_s":320,"rss_mib":967.421875},{"t_s":323,"rss_mib":967.421875},{"t_s":326,"rss_mib":967.421875},{"t_s":329,"rss_mib":967.421875},{"t_s":332,"rss_mib":967.421875},{"t_s":335,"rss_mib":967.421875},{"t_s":338,"rss_mib":967.421875},{"t_s":341,"rss_mib":967.421875},{"t_s":344,"rss_mib":967.421875},{"t_s":347,"rss_mib":967.421875},{"t_s":350,"rss_mib":967.421875},{"t_s":353,"rss_mib":967.421875},{"t_s":356,"rss_mib":967.421875},{"t_s":359,"rss_mib":967.421875},{"t_s":362,"rss_mib":967.421875}],"idle_rss_series":[{"t_s":0,"rss_mib":612.37890625},{"t_s":0,"rss_mib":612.37890625},{"t_s":0,"rss_mib":612.37890625},{"t_s":1,"rss_mib":612.37890625},{"t_s":1,"rss_mib":612.37890625},{"t_s":2,"rss_mib":612.37890625},{"t_s":2,"rss_mib":612.37890625},{"t_s":3,"rss_mib":612.37890625},{"t_s":3,"rss_mib":612.37890625},{"t_s":4,"rss_mib":612.37890625},{"t_s":4,"rss_mib":612.37890625},{"t_s":5,"rss_mib":612.37890625},{"t_s":5,"rss_mib":612.37890625},{"t_s":6,"rss_mib":612.37890625},{"t_s":6,"rss_mib":612.45703125},{"t_s":6,"rss_mib":612.45703125},{"t_s":7,"rss_mib":612.45703125},{"t_s":7,"rss_mib":612.45703125},{"t_s":8,"rss_mib":612.45703125},{"t_s":9,"rss_mib":612.45703125},{"t_s":9,"rss_mib":612.45703125},{"t_s":9,"rss_mib":612.45703125},{"t_s":10,"rss_mib":612.45703125},{"t_s":10,"rss_mib":612.45703125},{"t_s":11,"rss_mib":612.45703125},{"t_s":11,"rss_mib":612.45703125},{"t_s":12,"rss_mib":612.45703125},{"t_s":12,"rss_mib":612.45703125},{"t_s":13,"rss_mib":612.45703125},{"t_s":13,"rss_mib":612.45703125},{"t_s":14,"rss_mib":612.45703125},{"t_s":14,"rss_mib":612.45703125},{"t_s":15,"rss_mib":612.45703125},{"t_s":15,"rss_mib":612.45703125},{"t_s":16,"rss_mib":612.45703125},{"t_s":16,"rss_mib":612.45703125},{"t_s":17,"rss_mib":612.45703125},{"t_s":18,"rss_mib":612.45703125},{"t_s":18,"rss_mib":612.45703125},{"t_s":18,"rss_mib":612.45703125},{"t_s":19,"rss_mib":612.45703125},{"t_s":19,"rss_mib":612.45703125},{"t_s":20,"rss_mib":612.45703125},{"t_s":20,"rss_mib":612.45703125},{"t_s":21,"rss_mib":612.45703125},{"t_s":22,"rss_mib":612.45703125},{"t_s":22,"rss_mib":612.45703125},{"t_s":23,"rss_mib":612.45703125},{"t_s":23,"rss_mib":612.45703125},{"t_s":23,"rss_mib":612.45703125},{"t_s":24,"rss_mib":612.45703125},{"t_s":24,"rss_mib":612.45703125},{"t_s":25,"rss_mib":612.45703125},{"t_s":25,"rss_mib":612.45703125},{"t_s":26,"rss_mib":612.45703125},{"t_s":27,"rss_mib":612.45703125},{"t_s":27,"rss_mib":612.45703125},{"t_s":27,"rss_mib":612.45703125},{"t_s":28,"rss_mib":612.45703125},{"t_s":28,"rss_mib":612.45703125},{"t_s":29,"rss_mib":612.45703125},{"t_s":29,"rss_mib":612.45703125},{"t_s":30,"rss_mib":612.45703125},{"t_s":31,"rss_mib":612.45703125},{"t_s":31,"rss_mib":612.45703125},{"t_s":32,"rss_mib":612.45703125},{"t_s":32,"rss_mib":612.45703125},{"t_s":32,"rss_mib":612.4609375},{"t_s":32,"rss_mib":612.4609375},{"t_s":33,"rss_mib":612.4609375},{"t_s":33,"rss_mib":612.4609375},{"t_s":34,"rss_mib":612.4609375},{"t_s":34,"rss_mib":612.4609375},{"t_s":35,"rss_mib":612.4609375},{"t_s":36,"rss_mib":612.4609375},{"t_s":36,"rss_mib":612.4609375},{"t_s":36,"rss_mib":612.4609375},{"t_s":37,"rss_mib":612.4609375},{"t_s":37,"rss_mib":612.4609375},{"t_s":38,"rss_mib":612.4609375},{"t_s":38,"rss_mib":612.4609375},{"t_s":39,"rss_mib":612.4609375},{"t_s":40,"rss_mib":612.4609375},{"t_s":40,"rss_mib":612.4609375},{"t_s":41,"rss_mib":612.4609375},{"t_s":41,"rss_mib":612.4609375},{"t_s":41,"rss_mib":612.4609375},{"t_s":42,"rss_mib":612.4609375},{"t_s":42,"rss_mib":612.4609375},{"t_s":43,"rss_mib":612.4609375},{"t_s":43,"rss_mib":612.4609375},{"t_s":44,"rss_mib":612.4609375},{"t_s":45,"rss_mib":612.4609375},{"t_s":45,"rss_mib":612.4609375},{"t_s":46,"rss_mib":612.4609375},{"t_s":46,"rss_mib":612.4609375},{"t_s":46,"rss_mib":612.4609375},{"t_s":47,"rss_mib":612.4609375},{"t_s":47,"rss_mib":612.4609375},{"t_s":48,"rss_mib":612.4609375},{"t_s":49,"rss_mib":612.4609375},{"t_s":49,"rss_mib":612.4609375},{"t_s":50,"rss_mib":612.4609375},{"t_s":50,"rss_mib":612.4609375},{"t_s":50,"rss_mib":612.4609375},{"t_s":51,"rss_mib":612.4609375},{"t_s":51,"rss_mib":612.4609375},{"t_s":52,"rss_mib":612.4609375},{"t_s":52,"rss_mib":612.4609375},{"t_s":53,"rss_mib":612.4609375},{"t_s":54,"rss_mib":612.4609375},{"t_s":54,"rss_mib":612.4609375},{"t_s":55,"rss_mib":612.4609375},{"t_s":55,"rss_mib":612.4609375},{"t_s":55,"rss_mib":612.4609375},{"t_s":56,"rss_mib":612.4609375},{"t_s":56,"rss_mib":612.4609375},{"t_s":57,"rss_mib":612.4609375},{"t_s":58,"rss_mib":612.4609375},{"t_s":58,"rss_mib":612.4609375},{"t_s":59,"rss_mib":612.4609375},{"t_s":59,"rss_mib":612.4609375},{"t_s":59,"rss_mib":612.4609375}],"idle_window_s":60,"recovery_window_s":30},"timings_s":{"added_latency":12.184581235,"cost":6.384787327,"memory":427.701455994,"streaming":0.000002369,"streams_sustained":0.000002166,"throughput":363.032778917},"upstream_transport":"http","absences":{"memory.idle_shape":{"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"memory.shape":{"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"perf.frontier.100ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.sweep.c1024.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c1024.w2.p99_us":{"reason":"not_measured"},"perf.sweep.c1024.w3.p99_us":{"reason":"not_measured"},"perf.sweep.c256.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c256.w2.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w3.p99_us":{"reason":"not_measured"},"stream.added_gap_p50_us":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_gap_p99_us":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_ttft_p50_us":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_ttft_p99_us":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.gap_direct_samples":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.gap_gw_samples":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_fps":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_headroom":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_mock_ceiling":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.ttft_direct_samples":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"},"stream.ttft_gw_samples":{"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here"}}},"bedrock":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/model/amazon_bedrock/anthropic.claude-3-sonnet-20240229-v1:0/converse","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}}}},"anthropic":{"configurable":true,"served":true,"egress_config":null,"serve_error":"","cells":{"openai":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/chat/completions","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"openai-responses":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/responses","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"anthropic":{"served":true,"reason":null,"status":"","path":"/v1/messages","verdict_note":"","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":{"added_latency_p50_us":{"value":193933,"certified":true,"suppressed":false},"added_latency_p99_us":{"value":195022,"certified":true,"suppressed":false},"gateway_c1_p99_us":{"value":195049,"certified":true,"suppressed":false},"direct_c1_p99_us":{"value":27,"certified":true,"suppressed":false},"cpu_us_per_request":{"value":181353.38345864663,"certified":true,"suppressed":false},"rps_per_cpu_second":{"value":5.514096185737976,"certified":true,"suppressed":false},"cost_window_conc":{"value":8,"certified":true,"suppressed":false},"cost_core_utilisation":{"value":0.9610214676333437,"certified":true,"suppressed":false},"cost_window_ok":{"value":133,"certified":true,"suppressed":false},"cost_window_rps":{"value":22,"certified":true,"suppressed":false},"cost_threads":{"value":69,"certified":true,"suppressed":false},"cost_nonvol_ctxt_per_request":{"value":5.879699248120301,"certified":true,"suppressed":false},"cost_majflt":{"value":0,"certified":true,"suppressed":false},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false},"concurrency":8,"p99_us":559997,"first_disqualified_conc":512,"lower_bound":false,"samples":128}],"sweep":[{"conc":1,"ok":30,"rps":4,"p99_us":200008,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":199016,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":199004,"fail":0},{"conc":2,"ok":34,"rps":5,"p99_us":354016,"fail":0},{"conc":2,"ok":34,"rps":5,"p99_us":354011,"fail":0},{"conc":2,"ok":34,"rps":5,"p99_us":367986,"fail":0},{"conc":4,"ok":62,"rps":10,"p99_us":522022,"fail":0},{"conc":4,"ok":66,"rps":10,"p99_us":720813,"fail":0},{"conc":4,"ok":64,"rps":10,"p99_us":589118,"fail":0},{"conc":8,"ok":128,"rps":21,"p99_us":559997,"fail":0},{"conc":8,"ok":126,"rps":20,"p99_us":695663,"fail":0},{"conc":8,"ok":124,"rps":20,"p99_us":863112,"fail":0},{"conc":16,"ok":125,"rps":20,"p99_us":1707954,"fail":0},{"conc":16,"ok":125,"rps":20,"p99_us":1678425,"fail":0},{"conc":16,"ok":128,"rps":21,"p99_us":1605446,"fail":0},{"conc":32,"ok":107,"rps":17,"p99_us":5735403,"fail":0},{"conc":32,"ok":107,"rps":17,"p99_us":4891393,"fail":0},{"conc":32,"ok":104,"rps":17,"p99_us":3862610,"fail":0},{"conc":64,"ok":88,"rps":14,"p99_us":5776844,"fail":0},{"conc":64,"ok":87,"rps":14,"p99_us":5952239,"fail":0},{"conc":64,"ok":82,"rps":13,"p99_us":5932854,"fail":0},{"conc":128,"ok":34,"rps":5,"p99_us":5957367,"fail":0},{"conc":128,"ok":38,"rps":6,"p99_us":5694259,"fail":0},{"conc":128,"ok":39,"rps":6,"p99_us":5453258,"fail":0},{"conc":256,"ok":6,"rps":0.9999104963449547,"p99_us":3979898,"fail":0},{"conc":256,"ok":12,"rps":1,"p99_us":4083316,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0}],"rungs":[{"conc":1,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":199016,"windows":3,"clean_windows":3},{"conc":2,"rps":{"value":5,"certified":true,"suppressed":false},"p99_us":354016,"windows":3,"clean_windows":3},{"conc":4,"rps":{"value":10,"certified":true,"suppressed":false},"p99_us":589118,"windows":3,"clean_windows":3},{"conc":8,"rps":{"value":20,"certified":true,"suppressed":false},"p99_us":695663,"windows":3,"clean_windows":3},{"conc":16,"rps":{"value":20,"certified":true,"suppressed":false},"p99_us":1678425,"windows":3,"clean_windows":3},{"conc":32,"rps":{"value":17,"certified":true,"suppressed":false},"p99_us":4891393,"windows":3,"clean_windows":3},{"conc":64,"rps":{"value":14,"certified":true,"suppressed":false},"p99_us":5932854,"windows":3,"clean_windows":3},{"conc":128,"rps":{"value":6,"certified":true,"suppressed":false},"p99_us":5694259,"windows":3,"clean_windows":3},{"conc":256,"rps":{"value":0.9999104963449547,"certified":true,"suppressed":false},"p99_us":3979898,"windows":3,"clean_windows":2},{"conc":512,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"no window at c=512 was clean: 0 of 3 failed requests, the rest carried no usable rate or failure count"},"p99_us":null,"windows":3,"clean_windows":0}],"reverify_note":"anthropic>anthropic is a same-dialect cell: there is no translation to prove, so a request-shape check upstream cannot distinguish a translating gateway from a forwarding one","c1_note":"the c=1 percentiles are taken over 31 successful gateway round trip(s) and 264589 direct-to-mock round trip(s), each leg a single clean window with no failures","gateway_c1_samples":31,"direct_c1_samples":264589},"stream":{"stream_served":true,"stream_error":null,"reason":null,"stream_c1_note":"the c=1 streaming legs read 64 frame(s) through the gateway and 64 direct to the mock, out of a 64 frame budget. The added-GAP figures are percentiles over the intervals inside those two streams. The added-TTFT figures are percentiles over separate probes - 100 through the gateway and 100 direct, out of 100 attempted per leg - so they carry that weight and no more","added_ttft_p50_us":{"value":153935,"certified":true,"suppressed":false},"added_ttft_p99_us":{"value":165859,"certified":true,"suppressed":false},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21070us) came in under the mock's (21073us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing"},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21167us) came in under the mock's (21758us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing"},"streams_sustained_fps":{"value":919.9861683706454,"certified":true,"suppressed":false,"headroom":0.2786496567661089,"rig_ceiling":3301.5873015873017},"streams_sustained":{"value":65,"certified":true,"suppressed":false,"headroom":0.2786496567661089,"rig_ceiling":3301.5873015873017},"ttft_gw_samples":100,"ttft_direct_samples":100,"gap_gw_samples":63,"gap_direct_samples":63},"memory":{"protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","served":true,"serve_error":"","load_recipe":null,"idle_rss_mib":{"value":593.06640625,"certified":true,"suppressed":false},"steady_state_rss_mib":{"value":948.5078125,"certified":true,"suppressed":false},"recovered_rss_mib":{"value":948.43359375,"certified":true,"suppressed":false},"peak_rss_mib":{"value":949.0078125,"certified":true,"suppressed":false},"peak_rss_hwm_mib":{"value":948.77734375,"certified":true,"suppressed":false},"plateaued":true,"time_to_plateau_s":{"value":67,"certified":true,"suppressed":false},"growth_rate_mib_per_min":{"value":-0.30135980491154135,"certified":true,"suppressed":false},"load_s":{"value":303,"certified":true,"suppressed":false},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"idle_static":{"value":1,"certified":true,"suppressed":false},"idle_growth_rate_mib_per_min":{"value":0.05169704844231903,"certified":true,"suppressed":false},"rss_series":[{"t_s":0,"rss_mib":593.58203125},{"t_s":2,"rss_mib":944.6328125},{"t_s":2,"rss_mib":944.6640625},{"t_s":5,"rss_mib":944.98828125},{"t_s":5,"rss_mib":944.98828125},{"t_s":8,"rss_mib":945.5625},{"t_s":9,"rss_mib":945.5703125},{"t_s":11,"rss_mib":945.671875},{"t_s":12,"rss_mib":945.67578125},{"t_s":14,"rss_mib":946.22265625},{"t_s":15,"rss_mib":946.22265625},{"t_s":17,"rss_mib":946.26953125},{"t_s":18,"rss_mib":946.24609375},{"t_s":20,"rss_mib":946.328125},{"t_s":21,"rss_mib":946.328125},{"t_s":24,"rss_mib":946.39453125},{"t_s":24,"rss_mib":946.36328125},{"t_s":26,"rss_mib":946.4296875},{"t_s":27,"rss_mib":946.44140625},{"t_s":29,"rss_mib":946.48046875},{"t_s":30,"rss_mib":946.48046875},{"t_s":32,"rss_mib":946.51953125},{"t_s":33,"rss_mib":946.50390625},{"t_s":36,"rss_mib":946.83203125},{"t_s":36,"rss_mib":946.83203125},{"t_s":38,"rss_mib":946.87109375},{"t_s":39,"rss_mib":946.875},{"t_s":42,"rss_mib":946.91796875},{"t_s":42,"rss_mib":946.91796875},{"t_s":45,"rss_mib":947.05078125},{"t_s":45,"rss_mib":947.05078125},{"t_s":47,"rss_mib":947.171875},{"t_s":48,"rss_mib":947.0625},{"t_s":50,"rss_mib":947.08203125},{"t_s":51,"rss_mib":947.0625},{"t_s":54,"rss_mib":947.10546875},{"t_s":54,"rss_mib":947.10546875},{"t_s":56,"rss_mib":947.1484375},{"t_s":57,"rss_mib":947.1484375},{"t_s":58,"rss_mib":947.1640625},{"t_s":60,"rss_mib":947.16015625},{"t_s":63,"rss_mib":947.50390625},{"t_s":63,"rss_mib":947.5078125},{"t_s":66,"rss_mib":947.60546875},{"t_s":66,"rss_mib":947.54296875},{"t_s":69,"rss_mib":947.63671875},{"t_s":71,"rss_mib":947.65234375},{"t_s":72,"rss_mib":947.59765625},{"t_s":72,"rss_mib":947.59765625},{"t_s":73,"rss_mib":947.234375},{"t_s":75,"rss_mib":947.35546875},{"t_s":78,"rss_mib":947.41015625},{"t_s":78,"rss_mib":947.41015625},{"t_s":81,"rss_mib":947.5},{"t_s":81,"rss_mib":947.50390625},{"t_s":84,"rss_mib":947.53515625},{"t_s":86,"rss_mib":947.54296875},{"t_s":87,"rss_mib":947.48828125},{"t_s":87,"rss_mib":947.48828125},{"t_s":90,"rss_mib":947.50390625},{"t_s":92,"rss_mib":947.51171875},{"t_s":92,"rss_mib":947.42578125},{"t_s":93,"rss_mib":947.46484375},{"t_s":96,"rss_mib":947.5390625},{"t_s":96,"rss_mib":947.5390625},{"t_s":99,"rss_mib":947.6015625},{"t_s":100,"rss_mib":947.6015625},{"t_s":102,"rss_mib":947.73828125},{"t_s":102,"rss_mib":947.73828125},{"t_s":105,"rss_mib":947.84765625},{"t_s":106,"rss_mib":947.84765625},{"t_s":108,"rss_mib":948.015625},{"t_s":110,"rss_mib":948.0390625},{"t_s":111,"rss_mib":947.7734375},{"t_s":114,"rss_mib":947.55859375},{"t_s":114,"rss_mib":947.828125},{"t_s":115,"rss_mib":947.828125},{"t_s":117,"rss_mib":947.90234375},{"t_s":120,"rss_mib":947.9375},{"t_s":120,"rss_mib":947.89453125},{"t_s":121,"rss_mib":947.90234375},{"t_s":123,"rss_mib":947.98828125},{"t_s":124,"rss_mib":947.98828125},{"t_s":126,"rss_mib":947.9921875},{"t_s":127,"rss_mib":947.96484375},{"t_s":129,"rss_mib":948.19140625},{"t_s":130,"rss_mib":948.19140625},{"t_s":133,"rss_mib":948.20703125},{"t_s":133,"rss_mib":948.20703125},{"t_s":136,"rss_mib":948.3828125},{"t_s":136,"rss_mib":948.3828125},{"t_s":138,"rss_mib":948.4140625},{"t_s":139,"rss_mib":948.4140625},{"t_s":140,"rss_mib":948.421875},{"t_s":144,"rss_mib":948.43359375},{"t_s":145,"rss_mib":948.359375},{"t_s":146,"rss_mib":948.40234375},{"t_s":147,"rss_mib":948.296875},{"t_s":148,"rss_mib":948.32421875},{"t_s":149,"rss_mib":948.3203125},{"t_s":151,"rss_mib":948.32421875},{"t_s":154,"rss_mib":948.32421875},{"t_s":157,"rss_mib":948.625},{"t_s":157,"rss_mib":948.625},{"t_s":160,"rss_mib":948.75},{"t_s":160,"rss_mib":948.63671875},{"t_s":162,"rss_mib":948.734375},{"t_s":165,"rss_mib":948.75},{"t_s":165,"rss_mib":948.4296875},{"t_s":168,"rss_mib":948.3984375},{"t_s":168,"rss_mib":948.5078125},{"t_s":169,"rss_mib":948.5078125},{"t_s":172,"rss_mib":948.66796875},{"t_s":172,"rss_mib":948.66796875},{"t_s":175,"rss_mib":948.546875},{"t_s":175,"rss_mib":948.55859375},{"t_s":178,"rss_mib":948.46875},{"t_s":178,"rss_mib":948.46875},{"t_s":179,"rss_mib":948.48046875},{"t_s":181,"rss_mib":948.48046875},{"t_s":182,"rss_mib":948.47265625},{"t_s":184,"rss_mib":948.47265625},{"t_s":185,"rss_mib":948.43359375},{"t_s":187,"rss_mib":948.44140625},{"t_s":189,"rss_mib":948.47265625},{"t_s":190,"rss_mib":948.47265625},{"t_s":191,"rss_mib":948.4765625},{"t_s":193,"rss_mib":948.4765625},{"t_s":195,"rss_mib":948.1640625},{"t_s":197,"rss_mib":948.1875},{"t_s":199,"rss_mib":948.2109375},{"t_s":200,"rss_mib":948.2109375},{"t_s":200,"rss_mib":948.21875},{"t_s":203,"rss_mib":948.21875},{"t_s":203,"rss_mib":948.2265625},{"t_s":206,"rss_mib":948.23046875},{"t_s":208,"rss_mib":948.1640625},{"t_s":209,"rss_mib":948.0234375},{"t_s":211,"rss_mib":948.20703125},{"t_s":212,"rss_mib":948.20703125},{"t_s":212,"rss_mib":948.2265625},{"t_s":215,"rss_mib":948.21484375},{"t_s":216,"rss_mib":948.23046875},{"t_s":218,"rss_mib":948.234375},{"t_s":221,"rss_mib":948.13671875},{"t_s":221,"rss_mib":948.13671875},{"t_s":224,"rss_mib":948.18359375},{"t_s":224,"rss_mib":948.18359375},{"t_s":226,"rss_mib":948.24609375},{"t_s":227,"rss_mib":948.24609375},{"t_s":230,"rss_mib":948.28125},{"t_s":230,"rss_mib":948.28125},{"t_s":232,"rss_mib":948.328125},{"t_s":233,"rss_mib":948.3359375},{"t_s":235,"rss_mib":948.3125},{"t_s":238,"rss_mib":948.75390625},{"t_s":238,"rss_mib":948.58984375},{"t_s":240,"rss_mib":948.64453125},{"t_s":242,"rss_mib":948.5},{"t_s":242,"rss_mib":948.5},{"t_s":244,"rss_mib":948.71484375},{"t_s":245,"rss_mib":948.71484375},{"t_s":247,"rss_mib":948.73828125},{"t_s":248,"rss_mib":948.7265625},{"t_s":249,"rss_mib":948.75},{"t_s":251,"rss_mib":948.75},{"t_s":253,"rss_mib":948.765625},{"t_s":254,"rss_mib":948.7578125},{"t_s":257,"rss_mib":948.9609375},{"t_s":257,"rss_mib":948.96484375},{"t_s":259,"rss_mib":949.00390625},{"t_s":260,"rss_mib":949.00390625},{"t_s":263,"rss_mib":949.0078125},{"t_s":263,"rss_mib":949.0078125},{"t_s":264,"rss_mib":948.8359375},{"t_s":266,"rss_mib":948.84765625},{"t_s":269,"rss_mib":948.87109375},{"t_s":269,"rss_mib":948.87109375},{"t_s":272,"rss_mib":948.78515625},{"t_s":274,"rss_mib":948.640625},{"t_s":275,"rss_mib":948.640625},{"t_s":278,"rss_mib":948.7890625},{"t_s":278,"rss_mib":948.7890625},{"t_s":281,"rss_mib":948.7890625},{"t_s":283,"rss_mib":948.48046875},{"t_s":285,"rss_mib":948.515625},{"t_s":285,"rss_mib":948.46875},{"t_s":287,"rss_mib":948.48046875},{"t_s":290,"rss_mib":948.71875},{"t_s":291,"rss_mib":948.67578125},{"t_s":293,"rss_mib":948.75390625},{"t_s":294,"rss_mib":948.703125},{"t_s":296,"rss_mib":948.37109375},{"t_s":297,"rss_mib":948.56640625},{"t_s":299,"rss_mib":948.609375},{"t_s":301,"rss_mib":948.65625},{"t_s":302,"rss_mib":948.44921875},{"t_s":303,"rss_mib":948.44921875},{"t_s":303,"rss_mib":948.42578125},{"t_s":306,"rss_mib":948.42578125},{"t_s":306,"rss_mib":948.4296875},{"t_s":309,"rss_mib":948.43359375},{"t_s":312,"rss_mib":948.43359375},{"t_s":315,"rss_mib":948.43359375},{"t_s":318,"rss_mib":948.43359375},{"t_s":321,"rss_mib":948.43359375},{"t_s":324,"rss_mib":948.43359375},{"t_s":327,"rss_mib":948.43359375},{"t_s":330,"rss_mib":948.43359375},{"t_s":333,"rss_mib":948.43359375},{"t_s":336,"rss_mib":948.43359375},{"t_s":339,"rss_mib":948.43359375},{"t_s":342,"rss_mib":948.43359375},{"t_s":345,"rss_mib":948.43359375},{"t_s":348,"rss_mib":948.43359375},{"t_s":351,"rss_mib":948.43359375},{"t_s":354,"rss_mib":948.43359375},{"t_s":357,"rss_mib":948.43359375},{"t_s":360,"rss_mib":948.43359375},{"t_s":363,"rss_mib":948.43359375}],"idle_rss_series":[{"t_s":0,"rss_mib":592.98828125},{"t_s":0,"rss_mib":592.98828125},{"t_s":0,"rss_mib":592.98828125},{"t_s":1,"rss_mib":592.98828125},{"t_s":1,"rss_mib":592.98828125},{"t_s":2,"rss_mib":592.98828125},{"t_s":2,"rss_mib":592.98828125},{"t_s":3,"rss_mib":592.98828125},{"t_s":3,"rss_mib":592.98828125},{"t_s":4,"rss_mib":592.98828125},{"t_s":4,"rss_mib":592.98828125},{"t_s":5,"rss_mib":592.98828125},{"t_s":5,"rss_mib":592.98828125},{"t_s":6,"rss_mib":592.98828125},{"t_s":6,"rss_mib":593.06640625},{"t_s":6,"rss_mib":593.06640625},{"t_s":7,"rss_mib":593.06640625},{"t_s":7,"rss_mib":593.06640625},{"t_s":8,"rss_mib":593.06640625},{"t_s":9,"rss_mib":593.06640625},{"t_s":9,"rss_mib":593.06640625},{"t_s":9,"rss_mib":593.06640625},{"t_s":10,"rss_mib":593.06640625},{"t_s":10,"rss_mib":593.06640625},{"t_s":11,"rss_mib":593.06640625},{"t_s":11,"rss_mib":593.06640625},{"t_s":12,"rss_mib":593.06640625},{"t_s":13,"rss_mib":593.06640625},{"t_s":13,"rss_mib":593.06640625},{"t_s":13,"rss_mib":593.06640625},{"t_s":14,"rss_mib":593.06640625},{"t_s":14,"rss_mib":593.06640625},{"t_s":15,"rss_mib":593.06640625},{"t_s":15,"rss_mib":593.06640625},{"t_s":16,"rss_mib":593.06640625},{"t_s":16,"rss_mib":593.06640625},{"t_s":17,"rss_mib":593.06640625},{"t_s":18,"rss_mib":593.06640625},{"t_s":18,"rss_mib":593.06640625},{"t_s":18,"rss_mib":593.06640625},{"t_s":19,"rss_mib":593.06640625},{"t_s":19,"rss_mib":593.06640625},{"t_s":20,"rss_mib":593.06640625},{"t_s":20,"rss_mib":593.06640625},{"t_s":21,"rss_mib":593.06640625},{"t_s":22,"rss_mib":593.06640625},{"t_s":22,"rss_mib":593.06640625},{"t_s":23,"rss_mib":593.06640625},{"t_s":23,"rss_mib":593.06640625},{"t_s":23,"rss_mib":593.06640625},{"t_s":24,"rss_mib":593.06640625},{"t_s":24,"rss_mib":593.06640625},{"t_s":25,"rss_mib":593.06640625},{"t_s":26,"rss_mib":593.06640625},{"t_s":26,"rss_mib":593.06640625},{"t_s":27,"rss_mib":593.06640625},{"t_s":27,"rss_mib":593.06640625},{"t_s":27,"rss_mib":593.06640625},{"t_s":28,"rss_mib":593.06640625},{"t_s":28,"rss_mib":593.06640625},{"t_s":29,"rss_mib":593.06640625},{"t_s":29,"rss_mib":593.06640625},{"t_s":30,"rss_mib":593.06640625},{"t_s":31,"rss_mib":593.06640625},{"t_s":31,"rss_mib":593.06640625},{"t_s":32,"rss_mib":593.06640625},{"t_s":32,"rss_mib":593.06640625},{"t_s":32,"rss_mib":593.06640625},{"t_s":33,"rss_mib":593.06640625},{"t_s":33,"rss_mib":593.06640625},{"t_s":34,"rss_mib":593.06640625},{"t_s":35,"rss_mib":593.06640625},{"t_s":35,"rss_mib":593.06640625},{"t_s":36,"rss_mib":593.06640625},{"t_s":36,"rss_mib":593.0703125},{"t_s":36,"rss_mib":593.0703125},{"t_s":36,"rss_mib":593.0703125},{"t_s":37,"rss_mib":593.0703125},{"t_s":37,"rss_mib":593.0703125},{"t_s":38,"rss_mib":593.0703125},{"t_s":39,"rss_mib":593.0703125},{"t_s":39,"rss_mib":593.0703125},{"t_s":40,"rss_mib":593.0703125},{"t_s":40,"rss_mib":593.0703125},{"t_s":41,"rss_mib":593.0703125},{"t_s":41,"rss_mib":593.0703125},{"t_s":41,"rss_mib":593.0703125},{"t_s":42,"rss_mib":593.0703125},{"t_s":42,"rss_mib":593.0703125},{"t_s":43,"rss_mib":593.0703125},{"t_s":44,"rss_mib":593.0703125},{"t_s":44,"rss_mib":593.0703125},{"t_s":45,"rss_mib":593.0703125},{"t_s":45,"rss_mib":593.0703125},{"t_s":46,"rss_mib":593.0703125},{"t_s":46,"rss_mib":593.0703125},{"t_s":46,"rss_mib":593.0703125},{"t_s":47,"rss_mib":593.0703125},{"t_s":48,"rss_mib":593.0703125},{"t_s":48,"rss_mib":593.0703125},{"t_s":49,"rss_mib":593.0703125},{"t_s":49,"rss_mib":593.0703125},{"t_s":50,"rss_mib":593.0703125},{"t_s":50,"rss_mib":593.0703125},{"t_s":50,"rss_mib":593.0703125},{"t_s":51,"rss_mib":593.0703125},{"t_s":51,"rss_mib":593.0703125},{"t_s":52,"rss_mib":593.0703125},{"t_s":53,"rss_mib":593.0703125},{"t_s":53,"rss_mib":593.0703125},{"t_s":54,"rss_mib":593.0703125},{"t_s":54,"rss_mib":593.0703125},{"t_s":55,"rss_mib":593.0703125},{"t_s":55,"rss_mib":593.0703125},{"t_s":55,"rss_mib":593.0703125},{"t_s":56,"rss_mib":593.0703125},{"t_s":57,"rss_mib":593.0703125},{"t_s":57,"rss_mib":593.0703125},{"t_s":58,"rss_mib":593.0703125},{"t_s":58,"rss_mib":593.0703125},{"t_s":59,"rss_mib":593.0703125},{"t_s":59,"rss_mib":593.0703125},{"t_s":59,"rss_mib":593.0703125}],"idle_window_s":60,"recovery_window_s":30},"timings_s":{"added_latency":12.155303729,"cost":6.288014824,"memory":428.983429015,"streaming":18.164329373,"streams_sustained":62.98924996,"throughput":274.461520682},"upstream_transport":"http","absences":{"memory.idle_shape":{"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"memory.shape":{"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"perf.frontier.100ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.sweep.c256.w3.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w2.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w3.p99_us":{"reason":"not_measured"},"stream.added_gap_p50_us":{"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21070us) came in under the mock's (21073us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing"},"stream.added_gap_p99_us":{"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21167us) came in under the mock's (21758us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing"}}},"cohere":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v2/chat","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"gemini":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1beta/models/anthropic/claude-3-5-sonnet:generateContent","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"bedrock":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/model/anthropic/claude-3-5-sonnet/converse","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}}}},"openai-responses":{"configurable":true,"served":true,"egress_config":null,"serve_error":"","cells":{"anthropic":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/messages","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"gemini":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1beta/models/openai/gpt-4o-mini:generateContent","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"openai":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/chat/completions","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"openai-responses":{"served":true,"reason":null,"status":"","path":"/v1/responses","verdict_note":"","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":{"added_latency_p50_us":{"value":194984,"certified":true,"suppressed":false},"added_latency_p99_us":{"value":198964,"certified":true,"suppressed":false},"gateway_c1_p99_us":{"value":198991,"certified":true,"suppressed":false},"direct_c1_p99_us":{"value":27,"certified":true,"suppressed":false},"cpu_us_per_request":{"value":177760,"certified":true,"suppressed":false},"rps_per_cpu_second":{"value":5.625562556255626,"certified":true,"suppressed":false},"cost_window_conc":{"value":8,"certified":true,"suppressed":false},"cost_core_utilisation":{"value":0.8678710026382068,"certified":true,"suppressed":false},"cost_window_ok":{"value":125,"certified":true,"suppressed":false},"cost_window_rps":{"value":20,"certified":true,"suppressed":false},"cost_threads":{"value":68,"certified":true,"suppressed":false},"cost_nonvol_ctxt_per_request":{"value":4.712,"certified":true,"suppressed":false},"cost_majflt":{"value":0,"certified":true,"suppressed":false},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false},"concurrency":16,"p99_us":1695035,"first_disqualified_conc":512,"lower_bound":false,"samples":127}],"sweep":[{"conc":1,"ok":30,"rps":4,"p99_us":199968,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":200987,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":201017,"fail":0},{"conc":2,"ok":59,"rps":9,"p99_us":207051,"fail":0},{"conc":2,"ok":60,"rps":9,"p99_us":217000,"fail":0},{"conc":2,"ok":60,"rps":9,"p99_us":207017,"fail":0},{"conc":4,"ok":90,"rps":14,"p99_us":472507,"fail":0},{"conc":4,"ok":85,"rps":14,"p99_us":685408,"fail":0},{"conc":4,"ok":91,"rps":15,"p99_us":414289,"fail":0},{"conc":8,"ok":80,"rps":13,"p99_us":1939855,"fail":0},{"conc":8,"ok":81,"rps":13,"p99_us":1932212,"fail":0},{"conc":8,"ok":93,"rps":15,"p99_us":1050676,"fail":0},{"conc":16,"ok":123,"rps":20,"p99_us":2039192,"fail":0},{"conc":16,"ok":124,"rps":20,"p99_us":2031584,"fail":0},{"conc":16,"ok":127,"rps":21,"p99_us":1695035,"fail":0},{"conc":32,"ok":111,"rps":18,"p99_us":5383629,"fail":0},{"conc":32,"ok":108,"rps":17,"p99_us":3391831,"fail":0},{"conc":32,"ok":106,"rps":17,"p99_us":5972220,"fail":0},{"conc":64,"ok":78,"rps":12,"p99_us":5749022,"fail":0},{"conc":64,"ok":83,"rps":13,"p99_us":5971668,"fail":0},{"conc":64,"ok":80,"rps":13,"p99_us":4990067,"fail":0},{"conc":128,"ok":31,"rps":5,"p99_us":5549086,"fail":0},{"conc":128,"ok":34,"rps":5,"p99_us":5620095,"fail":0},{"conc":128,"ok":35,"rps":5,"p99_us":5652257,"fail":0},{"conc":256,"ok":2,"rps":0.3332552221972279,"p99_us":2543405,"fail":0},{"conc":256,"ok":6,"rps":0.999808942176734,"p99_us":4970497,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0}],"rungs":[{"conc":1,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":200987,"windows":3,"clean_windows":3},{"conc":2,"rps":{"value":9,"certified":true,"suppressed":false},"p99_us":207051,"windows":3,"clean_windows":3},{"conc":4,"rps":{"value":14,"certified":true,"suppressed":false},"p99_us":472507,"windows":3,"clean_windows":3},{"conc":8,"rps":{"value":13,"certified":true,"suppressed":false},"p99_us":1932212,"windows":3,"clean_windows":3},{"conc":16,"rps":{"value":20,"certified":true,"suppressed":false},"p99_us":2031584,"windows":3,"clean_windows":3},{"conc":32,"rps":{"value":17,"certified":true,"suppressed":false},"p99_us":5383629,"windows":3,"clean_windows":3},{"conc":64,"rps":{"value":13,"certified":true,"suppressed":false},"p99_us":5749022,"windows":3,"clean_windows":3},{"conc":128,"rps":{"value":5,"certified":true,"suppressed":false},"p99_us":5620095,"windows":3,"clean_windows":3},{"conc":256,"rps":{"value":0.3332552221972279,"certified":true,"suppressed":false},"p99_us":2543405,"windows":3,"clean_windows":2},{"conc":512,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"no window at c=512 was clean: 0 of 3 failed requests, the rest carried no usable rate or failure count"},"p99_us":null,"windows":3,"clean_windows":0}],"reverify_note":"openai-responses>openai-responses is a same-dialect cell: there is no translation to prove, so a request-shape check upstream cannot distinguish a translating gateway from a forwarding one","c1_note":"the c=1 percentiles are taken over 30 successful gateway round trip(s) and 268348 direct-to-mock round trip(s), each leg a single clean window with no failures","gateway_c1_samples":30,"direct_c1_samples":268348},"stream":{"stream_served":"untestable","stream_error":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","reason":"untestable","stream_c1_note":null,"added_ttft_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"added_ttft_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"streams_sustained_fps":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"streams_sustained":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"}},"memory":{"protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","served":true,"serve_error":"","load_recipe":null,"idle_rss_mib":{"value":611.9609375,"certified":true,"suppressed":false},"steady_state_rss_mib":{"value":1019.71484375,"certified":true,"suppressed":false},"recovered_rss_mib":{"value":1019.88671875,"certified":true,"suppressed":false},"peak_rss_mib":{"value":1019.96875,"certified":true,"suppressed":false},"peak_rss_hwm_mib":{"value":1019.88671875,"certified":true,"suppressed":false},"plateaued":true,"time_to_plateau_s":{"value":66,"certified":true,"suppressed":false},"growth_rate_mib_per_min":{"value":-0.19858581951462687,"certified":true,"suppressed":false},"load_s":{"value":301,"certified":true,"suppressed":false},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"idle_static":{"value":1,"certified":true,"suppressed":false},"idle_growth_rate_mib_per_min":{"value":0.04586307382763456,"certified":true,"suppressed":false},"rss_series":[{"t_s":0,"rss_mib":612.47265625},{"t_s":2,"rss_mib":1016.42578125},{"t_s":2,"rss_mib":1016.4375},{"t_s":5,"rss_mib":1016.66796875},{"t_s":5,"rss_mib":1016.66796875},{"t_s":8,"rss_mib":1017.16796875},{"t_s":8,"rss_mib":1017.171875},{"t_s":11,"rss_mib":1017.328125},{"t_s":12,"rss_mib":1017.33203125},{"t_s":14,"rss_mib":1017.7578125},{"t_s":15,"rss_mib":1017.76953125},{"t_s":17,"rss_mib":1017.828125},{"t_s":18,"rss_mib":1017.828125},{"t_s":20,"rss_mib":1018.00390625},{"t_s":21,"rss_mib":1018.00390625},{"t_s":23,"rss_mib":1018.140625},{"t_s":25,"rss_mib":1018.1328125},{"t_s":26,"rss_mib":1018.6796875},{"t_s":27,"rss_mib":1018.6796875},{"t_s":30,"rss_mib":1018.83203125},{"t_s":31,"rss_mib":1018.84765625},{"t_s":32,"rss_mib":1018.8046875},{"t_s":33,"rss_mib":1018.8046875},{"t_s":35,"rss_mib":1019.265625},{"t_s":36,"rss_mib":1019.07421875},{"t_s":38,"rss_mib":1019.109375},{"t_s":39,"rss_mib":1019.11328125},{"t_s":41,"rss_mib":1019.30078125},{"t_s":42,"rss_mib":1019.33203125},{"t_s":44,"rss_mib":1019.38671875},{"t_s":46,"rss_mib":1019.390625},{"t_s":47,"rss_mib":1019.29296875},{"t_s":48,"rss_mib":1019.296875},{"t_s":48,"rss_mib":1019.3046875},{"t_s":53,"rss_mib":1019.31640625},{"t_s":53,"rss_mib":1019.23828125},{"t_s":55,"rss_mib":1019.25390625},{"t_s":55,"rss_mib":1019.19921875},{"t_s":58,"rss_mib":1019.23828125},{"t_s":59,"rss_mib":1019.1875},{"t_s":60,"rss_mib":1019.2109375},{"t_s":62,"rss_mib":1019.23046875},{"t_s":63,"rss_mib":1019.23828125},{"t_s":63,"rss_mib":1019.203125},{"t_s":66,"rss_mib":1019.21484375},{"t_s":69,"rss_mib":1019.234375},{"t_s":69,"rss_mib":1019.234375},{"t_s":72,"rss_mib":1019.296875},{"t_s":72,"rss_mib":1019.296875},{"t_s":74,"rss_mib":1019.3359375},{"t_s":75,"rss_mib":1019.3359375},{"t_s":77,"rss_mib":1019.35546875},{"t_s":78,"rss_mib":1019.35546875},{"t_s":79,"rss_mib":1019.34375},{"t_s":81,"rss_mib":1019.34765625},{"t_s":84,"rss_mib":1019.36328125},{"t_s":84,"rss_mib":1019.36328125},{"t_s":86,"rss_mib":1019.37109375},{"t_s":87,"rss_mib":1019.37109375},{"t_s":88,"rss_mib":1019.375},{"t_s":90,"rss_mib":1019.375},{"t_s":93,"rss_mib":1019.2734375},{"t_s":93,"rss_mib":1019.33203125},{"t_s":96,"rss_mib":1019.46875},{"t_s":96,"rss_mib":1019.47265625},{"t_s":97,"rss_mib":1019.4140625},{"t_s":99,"rss_mib":1019.39453125},{"t_s":101,"rss_mib":1019.2265625},{"t_s":102,"rss_mib":1019.25390625},{"t_s":105,"rss_mib":1019.37109375},{"t_s":105,"rss_mib":1019.37109375},{"t_s":106,"rss_mib":1019.2421875},{"t_s":108,"rss_mib":1019.2578125},{"t_s":110,"rss_mib":1019.22265625},{"t_s":111,"rss_mib":1019.22265625},{"t_s":113,"rss_mib":1019.2578125},{"t_s":114,"rss_mib":1019.2578125},{"t_s":117,"rss_mib":1019.31640625},{"t_s":117,"rss_mib":1019.31640625},{"t_s":119,"rss_mib":1019.328125},{"t_s":120,"rss_mib":1019.328125},{"t_s":121,"rss_mib":1019.25390625},{"t_s":123,"rss_mib":1019.28515625},{"t_s":126,"rss_mib":1019.328125},{"t_s":127,"rss_mib":1019.33203125},{"t_s":128,"rss_mib":1019.3125},{"t_s":129,"rss_mib":1019.3125},{"t_s":131,"rss_mib":1019.31640625},{"t_s":132,"rss_mib":1019.31640625},{"t_s":133,"rss_mib":1019.28125},{"t_s":135,"rss_mib":1019.31640625},{"t_s":138,"rss_mib":1019.37890625},{"t_s":138,"rss_mib":1019.37890625},{"t_s":140,"rss_mib":1019.5},{"t_s":142,"rss_mib":1019.52734375},{"t_s":143,"rss_mib":1019.48828125},{"t_s":144,"rss_mib":1019.48828125},{"t_s":146,"rss_mib":1019.51171875},{"t_s":147,"rss_mib":1019.51171875},{"t_s":149,"rss_mib":1019.5234375},{"t_s":150,"rss_mib":1019.5234375},{"t_s":153,"rss_mib":1019.28125},{"t_s":153,"rss_mib":1019.29296875},{"t_s":156,"rss_mib":1019.328125},{"t_s":156,"rss_mib":1019.328125},{"t_s":158,"rss_mib":1019.33203125},{"t_s":159,"rss_mib":1019.33203125},{"t_s":162,"rss_mib":1019.64453125},{"t_s":162,"rss_mib":1019.64453125},{"t_s":165,"rss_mib":1019.703125},{"t_s":165,"rss_mib":1019.703125},{"t_s":168,"rss_mib":1019.75390625},{"t_s":168,"rss_mib":1019.75390625},{"t_s":170,"rss_mib":1019.77734375},{"t_s":173,"rss_mib":1019.7734375},{"t_s":173,"rss_mib":1019.79296875},{"t_s":174,"rss_mib":1019.79296875},{"t_s":176,"rss_mib":1019.8125},{"t_s":177,"rss_mib":1019.8125},{"t_s":180,"rss_mib":1019.828125},{"t_s":180,"rss_mib":1019.828125},{"t_s":183,"rss_mib":1019.84765625},{"t_s":183,"rss_mib":1019.84765625},{"t_s":186,"rss_mib":1019.70703125},{"t_s":186,"rss_mib":1019.70703125},{"t_s":187,"rss_mib":1019.71484375},{"t_s":189,"rss_mib":1019.71484375},{"t_s":192,"rss_mib":1019.71484375},{"t_s":195,"rss_mib":1019.484375},{"t_s":196,"rss_mib":1019.484375},{"t_s":198,"rss_mib":1019.54296875},{"t_s":199,"rss_mib":1019.54296875},{"t_s":199,"rss_mib":1019.38671875},{"t_s":202,"rss_mib":1019.453125},{"t_s":203,"rss_mib":1019.47265625},{"t_s":204,"rss_mib":1019.47265625},{"t_s":205,"rss_mib":1019.4765625},{"t_s":208,"rss_mib":1019.48828125},{"t_s":211,"rss_mib":1019.48828125},{"t_s":214,"rss_mib":1019.48828125},{"t_s":214,"rss_mib":1019.42578125},{"t_s":217,"rss_mib":1019.453125},{"t_s":219,"rss_mib":1019.52734375},{"t_s":220,"rss_mib":1019.52734375},{"t_s":222,"rss_mib":1019.71484375},{"t_s":224,"rss_mib":1019.74609375},{"t_s":225,"rss_mib":1019.69921875},{"t_s":226,"rss_mib":1019.71484375},{"t_s":228,"rss_mib":1019.74609375},{"t_s":229,"rss_mib":1019.74609375},{"t_s":229,"rss_mib":1019.75390625},{"t_s":232,"rss_mib":1019.75390625},{"t_s":235,"rss_mib":1019.75390625},{"t_s":236,"rss_mib":1019.8359375},{"t_s":238,"rss_mib":1019.77734375},{"t_s":241,"rss_mib":1019.8671875},{"t_s":241,"rss_mib":1019.8671875},{"t_s":242,"rss_mib":1019.88671875},{"t_s":244,"rss_mib":1019.88671875},{"t_s":246,"rss_mib":1019.91015625},{"t_s":248,"rss_mib":1019.890625},{"t_s":250,"rss_mib":1019.9296875},{"t_s":250,"rss_mib":1019.9296875},{"t_s":251,"rss_mib":1019.9375},{"t_s":253,"rss_mib":1019.9375},{"t_s":255,"rss_mib":1019.95703125},{"t_s":256,"rss_mib":1019.95703125},{"t_s":258,"rss_mib":1019.96875},{"t_s":259,"rss_mib":1019.96875},{"t_s":262,"rss_mib":1019.80078125},{"t_s":262,"rss_mib":1019.80078125},{"t_s":265,"rss_mib":1019.80078125},{"t_s":266,"rss_mib":1019.6796875},{"t_s":268,"rss_mib":1019.6796875},{"t_s":271,"rss_mib":1019.6953125},{"t_s":271,"rss_mib":1019.703125},{"t_s":272,"rss_mib":1019.6796875},{"t_s":274,"rss_mib":1019.6953125},{"t_s":274,"rss_mib":1019.5546875},{"t_s":277,"rss_mib":1019.578125},{"t_s":280,"rss_mib":1019.61328125},{"t_s":280,"rss_mib":1019.61328125},{"t_s":283,"rss_mib":1019.640625},{"t_s":283,"rss_mib":1019.640625},{"t_s":284,"rss_mib":1019.66015625},{"t_s":286,"rss_mib":1019.66015625},{"t_s":289,"rss_mib":1019.75},{"t_s":289,"rss_mib":1019.75},{"t_s":291,"rss_mib":1019.78515625},{"t_s":292,"rss_mib":1019.78515625},{"t_s":294,"rss_mib":1019.81640625},{"t_s":295,"rss_mib":1019.81640625},{"t_s":298,"rss_mib":1019.88671875},{"t_s":300,"rss_mib":1019.91015625},{"t_s":301,"rss_mib":1019.8828125},{"t_s":301,"rss_mib":1019.88671875},{"t_s":304,"rss_mib":1019.88671875},{"t_s":307,"rss_mib":1019.88671875},{"t_s":310,"rss_mib":1019.88671875},{"t_s":313,"rss_mib":1019.88671875},{"t_s":316,"rss_mib":1019.88671875},{"t_s":319,"rss_mib":1019.88671875},{"t_s":322,"rss_mib":1019.88671875},{"t_s":325,"rss_mib":1019.88671875},{"t_s":328,"rss_mib":1019.88671875},{"t_s":331,"rss_mib":1019.88671875},{"t_s":334,"rss_mib":1019.88671875},{"t_s":337,"rss_mib":1019.88671875},{"t_s":340,"rss_mib":1019.88671875},{"t_s":343,"rss_mib":1019.88671875},{"t_s":346,"rss_mib":1019.88671875},{"t_s":349,"rss_mib":1019.88671875},{"t_s":352,"rss_mib":1019.88671875},{"t_s":355,"rss_mib":1019.88671875},{"t_s":358,"rss_mib":1019.88671875},{"t_s":361,"rss_mib":1019.88671875}],"idle_rss_series":[{"t_s":0,"rss_mib":611.88671875},{"t_s":0,"rss_mib":611.88671875},{"t_s":0,"rss_mib":611.88671875},{"t_s":1,"rss_mib":611.88671875},{"t_s":1,"rss_mib":611.88671875},{"t_s":2,"rss_mib":611.88671875},{"t_s":2,"rss_mib":611.88671875},{"t_s":3,"rss_mib":611.88671875},{"t_s":3,"rss_mib":611.88671875},{"t_s":4,"rss_mib":611.88671875},{"t_s":4,"rss_mib":611.88671875},{"t_s":5,"rss_mib":611.88671875},{"t_s":5,"rss_mib":611.88671875},{"t_s":6,"rss_mib":611.88671875},{"t_s":6,"rss_mib":611.9609375},{"t_s":6,"rss_mib":611.9609375},{"t_s":7,"rss_mib":611.9609375},{"t_s":7,"rss_mib":611.9609375},{"t_s":8,"rss_mib":611.9609375},{"t_s":9,"rss_mib":611.9609375},{"t_s":9,"rss_mib":611.9609375},{"t_s":9,"rss_mib":611.9609375},{"t_s":10,"rss_mib":611.9609375},{"t_s":10,"rss_mib":611.9609375},{"t_s":11,"rss_mib":611.9609375},{"t_s":11,"rss_mib":611.9609375},{"t_s":12,"rss_mib":611.9609375},{"t_s":13,"rss_mib":611.9609375},{"t_s":13,"rss_mib":611.9609375},{"t_s":13,"rss_mib":611.9609375},{"t_s":14,"rss_mib":611.9609375},{"t_s":14,"rss_mib":611.9609375},{"t_s":15,"rss_mib":611.9609375},{"t_s":15,"rss_mib":611.9609375},{"t_s":16,"rss_mib":611.9609375},{"t_s":16,"rss_mib":611.9609375},{"t_s":17,"rss_mib":611.9609375},{"t_s":18,"rss_mib":611.9609375},{"t_s":18,"rss_mib":611.9609375},{"t_s":18,"rss_mib":611.9609375},{"t_s":19,"rss_mib":611.9609375},{"t_s":19,"rss_mib":611.9609375},{"t_s":20,"rss_mib":611.9609375},{"t_s":20,"rss_mib":611.9609375},{"t_s":21,"rss_mib":611.9609375},{"t_s":22,"rss_mib":611.9609375},{"t_s":22,"rss_mib":611.9609375},{"t_s":23,"rss_mib":611.9609375},{"t_s":23,"rss_mib":611.9609375},{"t_s":23,"rss_mib":611.9609375},{"t_s":24,"rss_mib":611.9609375},{"t_s":24,"rss_mib":611.9609375},{"t_s":25,"rss_mib":611.9609375},{"t_s":26,"rss_mib":611.9609375},{"t_s":26,"rss_mib":611.9609375},{"t_s":27,"rss_mib":611.9609375},{"t_s":27,"rss_mib":611.9609375},{"t_s":27,"rss_mib":611.9609375},{"t_s":28,"rss_mib":611.9609375},{"t_s":28,"rss_mib":611.9609375},{"t_s":29,"rss_mib":611.9609375},{"t_s":30,"rss_mib":611.9609375},{"t_s":30,"rss_mib":611.9609375},{"t_s":31,"rss_mib":611.9609375},{"t_s":31,"rss_mib":611.9609375},{"t_s":32,"rss_mib":611.9609375},{"t_s":32,"rss_mib":611.9609375},{"t_s":32,"rss_mib":611.9609375},{"t_s":33,"rss_mib":611.9609375},{"t_s":33,"rss_mib":611.9609375},{"t_s":34,"rss_mib":611.9609375},{"t_s":35,"rss_mib":611.9609375},{"t_s":35,"rss_mib":611.9609375},{"t_s":36,"rss_mib":611.9609375},{"t_s":36,"rss_mib":611.9609375},{"t_s":36,"rss_mib":611.9609375},{"t_s":37,"rss_mib":611.9609375},{"t_s":37,"rss_mib":611.9609375},{"t_s":38,"rss_mib":611.9609375},{"t_s":39,"rss_mib":611.9609375},{"t_s":39,"rss_mib":611.9609375},{"t_s":40,"rss_mib":611.9609375},{"t_s":40,"rss_mib":611.9609375},{"t_s":41,"rss_mib":611.9609375},{"t_s":41,"rss_mib":611.9609375},{"t_s":41,"rss_mib":611.9609375},{"t_s":42,"rss_mib":611.9609375},{"t_s":43,"rss_mib":611.9609375},{"t_s":43,"rss_mib":611.9609375},{"t_s":44,"rss_mib":611.9609375},{"t_s":44,"rss_mib":611.9609375},{"t_s":45,"rss_mib":611.9609375},{"t_s":45,"rss_mib":611.9609375},{"t_s":46,"rss_mib":611.9609375},{"t_s":46,"rss_mib":611.9609375},{"t_s":46,"rss_mib":611.9609375},{"t_s":47,"rss_mib":611.9609375},{"t_s":48,"rss_mib":611.9609375},{"t_s":48,"rss_mib":611.9609375},{"t_s":49,"rss_mib":611.9609375},{"t_s":49,"rss_mib":611.9609375},{"t_s":50,"rss_mib":611.9609375},{"t_s":50,"rss_mib":611.9609375},{"t_s":50,"rss_mib":611.9609375},{"t_s":51,"rss_mib":611.9609375},{"t_s":52,"rss_mib":611.9609375},{"t_s":52,"rss_mib":611.9609375},{"t_s":53,"rss_mib":611.9609375},{"t_s":53,"rss_mib":611.9609375},{"t_s":54,"rss_mib":611.9609375},{"t_s":54,"rss_mib":611.96484375},{"t_s":54,"rss_mib":611.96484375},{"t_s":55,"rss_mib":611.96484375},{"t_s":55,"rss_mib":611.96484375},{"t_s":56,"rss_mib":611.96484375},{"t_s":56,"rss_mib":611.96484375},{"t_s":57,"rss_mib":611.96484375},{"t_s":57,"rss_mib":611.96484375},{"t_s":58,"rss_mib":611.96484375},{"t_s":58,"rss_mib":611.96484375},{"t_s":59,"rss_mib":611.96484375},{"t_s":59,"rss_mib":611.96484375},{"t_s":59,"rss_mib":611.96484375}],"idle_window_s":60,"recovery_window_s":30},"timings_s":{"added_latency":12.026580054,"cost":6.414223945,"memory":427.066480404,"streaming":0.000001756,"streams_sustained":0.000002106,"throughput":276.479346955},"upstream_transport":"http","absences":{"memory.idle_shape":{"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"memory.shape":{"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"perf.frontier.100ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.sweep.c256.w3.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w2.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w3.p99_us":{"reason":"not_measured"},"stream.added_gap_p50_us":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_gap_p99_us":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_ttft_p50_us":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.added_ttft_p99_us":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.gap_direct_samples":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.gap_gw_samples":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_fps":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_headroom":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.streams_sustained_mock_ceiling":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.ttft_direct_samples":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"},"stream.ttft_gw_samples":{"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here"}}},"cohere":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v2/chat","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"bedrock":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/model/openai/gpt-4o-mini/converse","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}}}},"gemini":{"configurable":true,"served":false,"egress_config":null,"serve_error":"","cells":{"cohere":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v2/chat","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"openai":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/chat/completions","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"openai-responses":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/responses","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"anthropic":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/messages","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"gemini":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1beta/models/gemini/gemini-1.5-pro:generateContent","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"bedrock":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/model/gemini/gemini-1.5-pro/converse","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}}}},"cohere":{"configurable":false,"served":false,"egress_config":null,"serve_error":"","cells":{"openai-responses":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/responses","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"cohere":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v2/chat","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"openai":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/chat/completions","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"gemini":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1beta/models/gpt-4o-mini:generateContent","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"anthropic":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/messages","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"bedrock":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/model/gpt-4o-mini/converse","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}}}},"openai":{"configurable":true,"served":true,"egress_config":null,"serve_error":"","cells":{"openai":{"served":true,"reason":null,"status":"","path":"/v1/chat/completions","verdict_note":"","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":{"added_latency_p50_us":{"value":198988,"certified":true,"suppressed":false},"added_latency_p99_us":{"value":205966,"certified":true,"suppressed":false},"gateway_c1_p99_us":{"value":205993,"certified":true,"suppressed":false},"direct_c1_p99_us":{"value":27,"certified":true,"suppressed":false},"cpu_us_per_request":{"value":182230.76923076922,"certified":true,"suppressed":false},"rps_per_cpu_second":{"value":5.487547488391726,"certified":true,"suppressed":false},"cost_window_conc":{"value":8,"certified":true,"suppressed":false},"cost_core_utilisation":{"value":0.9645138811621244,"certified":true,"suppressed":false},"cost_window_ok":{"value":130,"certified":true,"suppressed":false},"cost_window_rps":{"value":21,"certified":true,"suppressed":false},"cost_threads":{"value":68,"certified":true,"suppressed":false},"cost_nonvol_ctxt_per_request":{"value":6.276923076923077,"certified":true,"suppressed":false},"cost_majflt":{"value":0,"certified":true,"suppressed":false},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":19,"certified":true,"suppressed":false},"concurrency":8,"p99_us":788018,"first_disqualified_conc":512,"lower_bound":false,"samples":118}],"sweep":[{"conc":1,"ok":28,"rps":4,"p99_us":222019,"fail":0},{"conc":1,"ok":27,"rps":4,"p99_us":226987,"fail":0},{"conc":1,"ok":27,"rps":4,"p99_us":226040,"fail":0},{"conc":2,"ok":54,"rps":8,"p99_us":226976,"fail":0},{"conc":2,"ok":54,"rps":8,"p99_us":232019,"fail":0},{"conc":2,"ok":54,"rps":8,"p99_us":226037,"fail":0},{"conc":4,"ok":103,"rps":17,"p99_us":381484,"fail":0},{"conc":4,"ok":104,"rps":17,"p99_us":243028,"fail":0},{"conc":4,"ok":104,"rps":17,"p99_us":249980,"fail":0},{"conc":8,"ok":116,"rps":19,"p99_us":835542,"fail":0},{"conc":8,"ok":119,"rps":19,"p99_us":894372,"fail":0},{"conc":8,"ok":118,"rps":19,"p99_us":788018,"fail":0},{"conc":16,"ok":106,"rps":17,"p99_us":2709689,"fail":0},{"conc":16,"ok":105,"rps":17,"p99_us":1735658,"fail":0},{"conc":16,"ok":108,"rps":17,"p99_us":3187551,"fail":0},{"conc":32,"ok":92,"rps":14,"p99_us":4352830,"fail":0},{"conc":32,"ok":93,"rps":15,"p99_us":5329620,"fail":0},{"conc":32,"ok":92,"rps":14,"p99_us":5323515,"fail":0},{"conc":64,"ok":75,"rps":12,"p99_us":5366599,"fail":0},{"conc":64,"ok":69,"rps":11,"p99_us":5616397,"fail":0},{"conc":64,"ok":76,"rps":12,"p99_us":5804402,"fail":0},{"conc":128,"ok":17,"rps":2,"p99_us":5168419,"fail":0},{"conc":128,"ok":30,"rps":4,"p99_us":5829489,"fail":0},{"conc":128,"ok":28,"rps":4,"p99_us":5315007,"fail":0},{"conc":256,"ok":12,"rps":1,"p99_us":4553055,"fail":0},{"conc":256,"ok":11,"rps":1,"p99_us":5897693,"fail":0},{"conc":256,"ok":15,"rps":2,"p99_us":5811545,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0}],"rungs":[{"conc":1,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":226040,"windows":3,"clean_windows":3},{"conc":2,"rps":{"value":8,"certified":true,"suppressed":false},"p99_us":226976,"windows":3,"clean_windows":3},{"conc":4,"rps":{"value":17,"certified":true,"suppressed":false},"p99_us":249980,"windows":3,"clean_windows":3},{"conc":8,"rps":{"value":19,"certified":true,"suppressed":false},"p99_us":835542,"windows":3,"clean_windows":3},{"conc":16,"rps":{"value":17,"certified":true,"suppressed":false},"p99_us":2709689,"windows":3,"clean_windows":3},{"conc":32,"rps":{"value":14,"certified":true,"suppressed":false},"p99_us":5323515,"windows":3,"clean_windows":3},{"conc":64,"rps":{"value":12,"certified":true,"suppressed":false},"p99_us":5616397,"windows":3,"clean_windows":3},{"conc":128,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":5315007,"windows":3,"clean_windows":3},{"conc":256,"rps":{"value":1,"certified":true,"suppressed":false},"p99_us":5811545,"windows":3,"clean_windows":3},{"conc":512,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"no window at c=512 was clean: 0 of 3 failed requests, the rest carried no usable rate or failure count"},"p99_us":null,"windows":3,"clean_windows":0}],"reverify_note":"openai>openai is a same-dialect cell: there is no translation to prove, so a request-shape check upstream cannot distinguish a translating gateway from a forwarding one","c1_note":"the c=1 percentiles are taken over 30 successful gateway round trip(s) and 266566 direct-to-mock round trip(s), each leg a single clean window with no failures","gateway_c1_samples":30,"direct_c1_samples":266566},"stream":{"stream_served":true,"stream_error":null,"reason":null,"stream_c1_note":"the c=1 streaming legs read 64 frame(s) through the gateway and 64 direct to the mock, out of a 64 frame budget. The added-GAP figures are percentiles over the intervals inside those two streams. The added-TTFT figures are percentiles over separate probes - 100 through the gateway and 100 direct, out of 100 attempted per leg - so they carry that weight and no more","added_ttft_p50_us":{"value":158773,"certified":true,"suppressed":false},"added_ttft_p99_us":{"value":170494,"certified":true,"suppressed":false},"added_gap_p50_us":{"value":1,"certified":true,"suppressed":false},"added_gap_p99_us":{"value":38,"certified":true,"suppressed":false},"streams_sustained_fps":{"value":669.7194949393278,"certified":true,"suppressed":false,"headroom":0.4546587088488971,"rig_ceiling":1473.015873015873},"streams_sustained":{"value":29,"certified":true,"suppressed":false,"headroom":0.4546587088488971,"rig_ceiling":1473.015873015873},"ttft_gw_samples":100,"ttft_direct_samples":100,"gap_gw_samples":63,"gap_direct_samples":63},"memory":{"protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","served":true,"serve_error":"","load_recipe":null,"idle_rss_mib":{"value":617.203125,"certified":true,"suppressed":false},"steady_state_rss_mib":{"value":971.84765625,"certified":true,"suppressed":false},"recovered_rss_mib":{"value":972.3203125,"certified":true,"suppressed":false},"peak_rss_mib":{"value":972.4453125,"certified":true,"suppressed":false},"peak_rss_hwm_mib":{"value":972.31640625,"certified":true,"suppressed":false},"plateaued":true,"time_to_plateau_s":{"value":61,"certified":true,"suppressed":false},"growth_rate_mib_per_min":{"value":0.12924042130805258,"certified":true,"suppressed":false},"load_s":{"value":305,"certified":true,"suppressed":false},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"idle_static":{"value":1,"certified":true,"suppressed":false},"idle_growth_rate_mib_per_min":{"value":0.052286481252150616,"certified":true,"suppressed":false},"rss_series":[{"t_s":0,"rss_mib":617.7109375},{"t_s":2,"rss_mib":968.26171875},{"t_s":2,"rss_mib":968.2890625},{"t_s":5,"rss_mib":968.59375},{"t_s":5,"rss_mib":968.60546875},{"t_s":8,"rss_mib":969.23828125},{"t_s":9,"rss_mib":969.25390625},{"t_s":11,"rss_mib":969.45703125},{"t_s":12,"rss_mib":969.45703125},{"t_s":15,"rss_mib":969.63671875},{"t_s":15,"rss_mib":969.63671875},{"t_s":17,"rss_mib":969.73046875},{"t_s":19,"rss_mib":969.71875},{"t_s":20,"rss_mib":969.96484375},{"t_s":21,"rss_mib":969.97265625},{"t_s":24,"rss_mib":970.12109375},{"t_s":24,"rss_mib":970.10546875},{"t_s":27,"rss_mib":970.12890625},{"t_s":27,"rss_mib":970.1484375},{"t_s":30,"rss_mib":970.3828125},{"t_s":30,"rss_mib":970.3828125},{"t_s":32,"rss_mib":970.44921875},{"t_s":33,"rss_mib":970.45703125},{"t_s":36,"rss_mib":970.62890625},{"t_s":36,"rss_mib":970.62890625},{"t_s":39,"rss_mib":970.72265625},{"t_s":40,"rss_mib":970.7421875},{"t_s":41,"rss_mib":970.58984375},{"t_s":42,"rss_mib":970.69140625},{"t_s":45,"rss_mib":970.80078125},{"t_s":45,"rss_mib":970.80078125},{"t_s":48,"rss_mib":970.8671875},{"t_s":48,"rss_mib":970.8671875},{"t_s":51,"rss_mib":970.88671875},{"t_s":51,"rss_mib":970.88671875},{"t_s":53,"rss_mib":970.8984375},{"t_s":54,"rss_mib":970.8984375},{"t_s":57,"rss_mib":971.00390625},{"t_s":57,"rss_mib":971.00390625},{"t_s":58,"rss_mib":970.88671875},{"t_s":60,"rss_mib":970.9375},{"t_s":63,"rss_mib":971.21875},{"t_s":63,"rss_mib":971.21875},{"t_s":66,"rss_mib":971.29296875},{"t_s":67,"rss_mib":971.30078125},{"t_s":68,"rss_mib":971.15234375},{"t_s":70,"rss_mib":971.15625},{"t_s":72,"rss_mib":971.1953125},{"t_s":73,"rss_mib":971.1953125},{"t_s":75,"rss_mib":971.25},{"t_s":77,"rss_mib":971.26171875},{"t_s":77,"rss_mib":971.23828125},{"t_s":80,"rss_mib":971.265625},{"t_s":81,"rss_mib":971.2421875},{"t_s":82,"rss_mib":971.2578125},{"t_s":84,"rss_mib":971.28515625},{"t_s":85,"rss_mib":971.28515625},{"t_s":87,"rss_mib":971.30859375},{"t_s":88,"rss_mib":971.30859375},{"t_s":91,"rss_mib":971.40234375},{"t_s":91,"rss_mib":971.4140625},{"t_s":93,"rss_mib":971.59375},{"t_s":94,"rss_mib":971.53125},{"t_s":97,"rss_mib":971.71875},{"t_s":98,"rss_mib":971.76953125},{"t_s":99,"rss_mib":971.703125},{"t_s":101,"rss_mib":971.6875},{"t_s":102,"rss_mib":971.83984375},{"t_s":103,"rss_mib":971.83984375},{"t_s":105,"rss_mib":971.87890625},{"t_s":106,"rss_mib":971.8671875},{"t_s":109,"rss_mib":971.9296875},{"t_s":109,"rss_mib":971.93359375},{"t_s":112,"rss_mib":972.01953125},{"t_s":112,"rss_mib":972.02734375},{"t_s":115,"rss_mib":972.078125},{"t_s":115,"rss_mib":972.078125},{"t_s":118,"rss_mib":972.12109375},{"t_s":118,"rss_mib":972.12109375},{"t_s":121,"rss_mib":972.1015625},{"t_s":123,"rss_mib":972.109375},{"t_s":124,"rss_mib":972.01953125},{"t_s":127,"rss_mib":972.03515625},{"t_s":127,"rss_mib":971.91796875},{"t_s":128,"rss_mib":971.953125},{"t_s":129,"rss_mib":971.6953125},{"t_s":133,"rss_mib":971.7109375},{"t_s":133,"rss_mib":971.60546875},{"t_s":133,"rss_mib":971.60546875},{"t_s":135,"rss_mib":971.5},{"t_s":137,"rss_mib":971.5546875},{"t_s":138,"rss_mib":971.56640625},{"t_s":141,"rss_mib":971.5703125},{"t_s":142,"rss_mib":971.34765625},{"t_s":143,"rss_mib":971.359375},{"t_s":146,"rss_mib":971.40234375},{"t_s":146,"rss_mib":971.40234375},{"t_s":147,"rss_mib":971.421875},{"t_s":149,"rss_mib":971.421875},{"t_s":152,"rss_mib":971.48046875},{"t_s":152,"rss_mib":971.48046875},{"t_s":154,"rss_mib":971.50390625},{"t_s":155,"rss_mib":971.50390625},{"t_s":158,"rss_mib":971.57421875},{"t_s":158,"rss_mib":971.57421875},{"t_s":159,"rss_mib":971.59765625},{"t_s":161,"rss_mib":971.57421875},{"t_s":163,"rss_mib":971.60546875},{"t_s":165,"rss_mib":971.66796875},{"t_s":165,"rss_mib":971.54296875},{"t_s":167,"rss_mib":971.62890625},{"t_s":170,"rss_mib":971.69140625},{"t_s":171,"rss_mib":971.703125},{"t_s":172,"rss_mib":971.62109375},{"t_s":173,"rss_mib":971.625},{"t_s":176,"rss_mib":971.6796875},{"t_s":176,"rss_mib":971.70703125},{"t_s":179,"rss_mib":971.73828125},{"t_s":179,"rss_mib":971.73828125},{"t_s":181,"rss_mib":971.74609375},{"t_s":182,"rss_mib":971.74609375},{"t_s":185,"rss_mib":971.81640625},{"t_s":185,"rss_mib":971.81640625},{"t_s":187,"rss_mib":971.84375},{"t_s":188,"rss_mib":971.84375},{"t_s":191,"rss_mib":971.85546875},{"t_s":191,"rss_mib":971.85546875},{"t_s":192,"rss_mib":971.73046875},{"t_s":196,"rss_mib":971.73828125},{"t_s":197,"rss_mib":971.72265625},{"t_s":197,"rss_mib":971.734375},{"t_s":200,"rss_mib":971.75},{"t_s":200,"rss_mib":971.75},{"t_s":202,"rss_mib":971.6015625},{"t_s":204,"rss_mib":971.640625},{"t_s":206,"rss_mib":971.6796875},{"t_s":207,"rss_mib":971.6796875},{"t_s":208,"rss_mib":971.71875},{"t_s":210,"rss_mib":971.66015625},{"t_s":211,"rss_mib":971.8984375},{"t_s":214,"rss_mib":971.8828125},{"t_s":214,"rss_mib":971.74609375},{"t_s":216,"rss_mib":971.7578125},{"t_s":217,"rss_mib":971.65625},{"t_s":219,"rss_mib":971.6640625},{"t_s":221,"rss_mib":971.71484375},{"t_s":223,"rss_mib":971.6875},{"t_s":224,"rss_mib":971.74609375},{"t_s":225,"rss_mib":971.75390625},{"t_s":227,"rss_mib":971.7890625},{"t_s":228,"rss_mib":971.796875},{"t_s":230,"rss_mib":971.84375},{"t_s":231,"rss_mib":971.84375},{"t_s":231,"rss_mib":971.84765625},{"t_s":234,"rss_mib":971.84765625},{"t_s":236,"rss_mib":971.8515625},{"t_s":237,"rss_mib":971.8515625},{"t_s":240,"rss_mib":971.95703125},{"t_s":241,"rss_mib":971.9765625},{"t_s":242,"rss_mib":971.9140625},{"t_s":244,"rss_mib":971.89453125},{"t_s":246,"rss_mib":972.01171875},{"t_s":246,"rss_mib":972.015625},{"t_s":247,"rss_mib":972.02734375},{"t_s":249,"rss_mib":972.02734375},{"t_s":251,"rss_mib":972.05859375},{"t_s":252,"rss_mib":972.0625},{"t_s":254,"rss_mib":972.10546875},{"t_s":255,"rss_mib":972.10546875},{"t_s":258,"rss_mib":972.234375},{"t_s":258,"rss_mib":972.234375},{"t_s":261,"rss_mib":972.41796875},{"t_s":261,"rss_mib":972.421875},{"t_s":263,"rss_mib":972.43359375},{"t_s":264,"rss_mib":972.43359375},{"t_s":267,"rss_mib":972.4453125},{"t_s":267,"rss_mib":972.4453125},{"t_s":270,"rss_mib":972.3828125},{"t_s":273,"rss_mib":972.40234375},{"t_s":273,"rss_mib":972.36328125},{"t_s":274,"rss_mib":972.36328125},{"t_s":276,"rss_mib":972.37109375},{"t_s":278,"rss_mib":972.39453125},{"t_s":279,"rss_mib":972.21875},{"t_s":280,"rss_mib":972.21875},{"t_s":281,"rss_mib":972.09375},{"t_s":283,"rss_mib":972.09375},{"t_s":285,"rss_mib":972.23046875},{"t_s":286,"rss_mib":972.2421875},{"t_s":286,"rss_mib":972.1796875},{"t_s":289,"rss_mib":972.1953125},{"t_s":291,"rss_mib":972.2109375},{"t_s":292,"rss_mib":972.2109375},{"t_s":295,"rss_mib":972.23828125},{"t_s":295,"rss_mib":972.23828125},{"t_s":297,"rss_mib":972.2734375},{"t_s":298,"rss_mib":972.26171875},{"t_s":300,"rss_mib":972.27734375},{"t_s":301,"rss_mib":972.27734375},{"t_s":304,"rss_mib":972.31640625},{"t_s":304,"rss_mib":972.31640625},{"t_s":307,"rss_mib":972.31640625},{"t_s":310,"rss_mib":972.31640625},{"t_s":313,"rss_mib":972.31640625},{"t_s":316,"rss_mib":972.31640625},{"t_s":319,"rss_mib":972.31640625},{"t_s":322,"rss_mib":972.31640625},{"t_s":325,"rss_mib":972.31640625},{"t_s":328,"rss_mib":972.31640625},{"t_s":331,"rss_mib":972.31640625},{"t_s":333,"rss_mib":972.3203125},{"t_s":334,"rss_mib":972.3203125},{"t_s":337,"rss_mib":972.3203125},{"t_s":340,"rss_mib":972.3203125},{"t_s":343,"rss_mib":972.3203125},{"t_s":347,"rss_mib":972.3203125},{"t_s":350,"rss_mib":972.3203125},{"t_s":353,"rss_mib":972.3203125},{"t_s":356,"rss_mib":972.3203125},{"t_s":359,"rss_mib":972.3203125},{"t_s":362,"rss_mib":972.3203125},{"t_s":365,"rss_mib":972.3203125}],"idle_rss_series":[{"t_s":0,"rss_mib":617.12109375},{"t_s":0,"rss_mib":617.12109375},{"t_s":0,"rss_mib":617.12109375},{"t_s":1,"rss_mib":617.12109375},{"t_s":1,"rss_mib":617.12109375},{"t_s":2,"rss_mib":617.12109375},{"t_s":2,"rss_mib":617.12109375},{"t_s":3,"rss_mib":617.12109375},{"t_s":3,"rss_mib":617.12109375},{"t_s":4,"rss_mib":617.12109375},{"t_s":4,"rss_mib":617.12109375},{"t_s":5,"rss_mib":617.12109375},{"t_s":5,"rss_mib":617.12109375},{"t_s":6,"rss_mib":617.12109375},{"t_s":6,"rss_mib":617.19921875},{"t_s":6,"rss_mib":617.19921875},{"t_s":7,"rss_mib":617.19921875},{"t_s":7,"rss_mib":617.19921875},{"t_s":8,"rss_mib":617.19921875},{"t_s":8,"rss_mib":617.19921875},{"t_s":9,"rss_mib":617.19921875},{"t_s":10,"rss_mib":617.19921875},{"t_s":10,"rss_mib":617.19921875},{"t_s":10,"rss_mib":617.19921875},{"t_s":11,"rss_mib":617.19921875},{"t_s":11,"rss_mib":617.19921875},{"t_s":12,"rss_mib":617.19921875},{"t_s":13,"rss_mib":617.19921875},{"t_s":13,"rss_mib":617.19921875},{"t_s":13,"rss_mib":617.19921875},{"t_s":14,"rss_mib":617.19921875},{"t_s":14,"rss_mib":617.19921875},{"t_s":15,"rss_mib":617.19921875},{"t_s":16,"rss_mib":617.19921875},{"t_s":16,"rss_mib":617.19921875},{"t_s":16,"rss_mib":617.19921875},{"t_s":17,"rss_mib":617.19921875},{"t_s":17,"rss_mib":617.19921875},{"t_s":18,"rss_mib":617.19921875},{"t_s":18,"rss_mib":617.19921875},{"t_s":19,"rss_mib":617.19921875},{"t_s":20,"rss_mib":617.19921875},{"t_s":20,"rss_mib":617.19921875},{"t_s":20,"rss_mib":617.19921875},{"t_s":21,"rss_mib":617.19921875},{"t_s":21,"rss_mib":617.19921875},{"t_s":22,"rss_mib":617.19921875},{"t_s":23,"rss_mib":617.19921875},{"t_s":23,"rss_mib":617.19921875},{"t_s":23,"rss_mib":617.19921875},{"t_s":24,"rss_mib":617.19921875},{"t_s":24,"rss_mib":617.19921875},{"t_s":25,"rss_mib":617.19921875},{"t_s":26,"rss_mib":617.19921875},{"t_s":26,"rss_mib":617.19921875},{"t_s":26,"rss_mib":617.19921875},{"t_s":27,"rss_mib":617.19921875},{"t_s":27,"rss_mib":617.19921875},{"t_s":28,"rss_mib":617.19921875},{"t_s":28,"rss_mib":617.203125},{"t_s":29,"rss_mib":617.203125},{"t_s":29,"rss_mib":617.203125},{"t_s":30,"rss_mib":617.203125},{"t_s":30,"rss_mib":617.203125},{"t_s":30,"rss_mib":617.203125},{"t_s":31,"rss_mib":617.203125},{"t_s":32,"rss_mib":617.203125},{"t_s":32,"rss_mib":617.203125},{"t_s":33,"rss_mib":617.203125},{"t_s":33,"rss_mib":617.203125},{"t_s":33,"rss_mib":617.203125},{"t_s":34,"rss_mib":617.203125},{"t_s":34,"rss_mib":617.203125},{"t_s":35,"rss_mib":617.203125},{"t_s":36,"rss_mib":617.203125},{"t_s":36,"rss_mib":617.203125},{"t_s":36,"rss_mib":617.203125},{"t_s":37,"rss_mib":617.203125},{"t_s":37,"rss_mib":617.203125},{"t_s":38,"rss_mib":617.203125},{"t_s":39,"rss_mib":617.203125},{"t_s":39,"rss_mib":617.203125},{"t_s":40,"rss_mib":617.203125},{"t_s":40,"rss_mib":617.203125},{"t_s":40,"rss_mib":617.203125},{"t_s":41,"rss_mib":617.203125},{"t_s":42,"rss_mib":617.203125},{"t_s":42,"rss_mib":617.203125},{"t_s":43,"rss_mib":617.203125},{"t_s":43,"rss_mib":617.203125},{"t_s":43,"rss_mib":617.203125},{"t_s":44,"rss_mib":617.203125},{"t_s":45,"rss_mib":617.203125},{"t_s":45,"rss_mib":617.203125},{"t_s":46,"rss_mib":617.203125},{"t_s":46,"rss_mib":617.203125},{"t_s":46,"rss_mib":617.203125},{"t_s":47,"rss_mib":617.203125},{"t_s":48,"rss_mib":617.203125},{"t_s":48,"rss_mib":617.203125},{"t_s":49,"rss_mib":617.203125},{"t_s":49,"rss_mib":617.203125},{"t_s":49,"rss_mib":617.203125},{"t_s":50,"rss_mib":617.203125},{"t_s":50,"rss_mib":617.203125},{"t_s":51,"rss_mib":617.203125},{"t_s":52,"rss_mib":617.203125},{"t_s":52,"rss_mib":617.203125},{"t_s":53,"rss_mib":617.203125},{"t_s":53,"rss_mib":617.203125},{"t_s":53,"rss_mib":617.203125},{"t_s":54,"rss_mib":617.203125},{"t_s":55,"rss_mib":617.203125},{"t_s":55,"rss_mib":617.203125},{"t_s":56,"rss_mib":617.203125},{"t_s":56,"rss_mib":617.203125},{"t_s":56,"rss_mib":617.203125},{"t_s":57,"rss_mib":617.203125},{"t_s":58,"rss_mib":617.203125},{"t_s":58,"rss_mib":617.203125},{"t_s":59,"rss_mib":617.203125},{"t_s":59,"rss_mib":617.203125},{"t_s":59,"rss_mib":617.203125}],"idle_window_s":60,"recovery_window_s":30},"timings_s":{"added_latency":12.16606242,"cost":6.154093472,"memory":430.757881696,"streaming":18.735070203,"streams_sustained":27.704758873,"throughput":288.496988089},"upstream_transport":"http","absences":{"memory.idle_shape":{"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"memory.shape":{"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"perf.frontier.100ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.sweep.c512.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w2.p99_us":{"reason":"not_measured"},"perf.sweep.c512.w3.p99_us":{"reason":"not_measured"}}},"openai-responses":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1/responses","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"bedrock":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/model/openai/gpt-4o-mini/converse","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"anthropic":{"served":true,"reason":null,"status":"","path":"/v1/messages","verdict_note":"","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":{"added_latency_p50_us":{"value":195998,"certified":true,"suppressed":false},"added_latency_p99_us":{"value":198984,"certified":true,"suppressed":false},"gateway_c1_p99_us":{"value":199012,"certified":true,"suppressed":false},"direct_c1_p99_us":{"value":28,"certified":true,"suppressed":false},"cpu_us_per_request":{"value":178977.27272727274,"certified":true,"suppressed":false},"rps_per_cpu_second":{"value":5.587301587301587,"certified":true,"suppressed":false},"cost_window_conc":{"value":8,"certified":true,"suppressed":false},"cost_core_utilisation":{"value":0.647250235848493,"certified":true,"suppressed":false},"cost_window_ok":{"value":88,"certified":true,"suppressed":false},"cost_window_rps":{"value":14,"certified":true,"suppressed":false},"cost_threads":{"value":84,"certified":true,"suppressed":false},"cost_nonvol_ctxt_per_request":{"value":5.840909090909091,"certified":true,"suppressed":false},"cost_majflt":{"value":0,"certified":true,"suppressed":false},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false},"concurrency":8,"p99_us":1051244,"first_disqualified_conc":256,"lower_bound":false,"samples":128}],"sweep":[{"conc":1,"ok":30,"rps":4,"p99_us":204989,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":205980,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":209006,"fail":0},{"conc":2,"ok":58,"rps":9,"p99_us":207005,"fail":0},{"conc":2,"ok":58,"rps":9,"p99_us":211868,"fail":0},{"conc":2,"ok":58,"rps":9,"p99_us":210027,"fail":0},{"conc":4,"ok":112,"rps":18,"p99_us":231037,"fail":0},{"conc":4,"ok":108,"rps":17,"p99_us":377527,"fail":0},{"conc":4,"ok":111,"rps":18,"p99_us":229015,"fail":0},{"conc":8,"ok":129,"rps":21,"p99_us":862107,"fail":0},{"conc":8,"ok":129,"rps":21,"p99_us":693129,"fail":0},{"conc":8,"ok":128,"rps":21,"p99_us":1051244,"fail":0},{"conc":16,"ok":123,"rps":20,"p99_us":1949874,"fail":0},{"conc":16,"ok":120,"rps":19,"p99_us":1701780,"fail":0},{"conc":16,"ok":124,"rps":20,"p99_us":1696764,"fail":0},{"conc":32,"ok":105,"rps":17,"p99_us":3363798,"fail":0},{"conc":32,"ok":102,"rps":16,"p99_us":4699209,"fail":0},{"conc":32,"ok":106,"rps":17,"p99_us":3708317,"fail":0},{"conc":64,"ok":86,"rps":14,"p99_us":5619121,"fail":0},{"conc":64,"ok":90,"rps":14,"p99_us":5873112,"fail":0},{"conc":64,"ok":84,"rps":13,"p99_us":5791176,"fail":0},{"conc":128,"ok":26,"rps":4,"p99_us":5697032,"fail":0},{"conc":128,"ok":23,"rps":3,"p99_us":5559463,"fail":0},{"conc":128,"ok":14,"rps":2,"p99_us":5776960,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0}],"rungs":[{"conc":1,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":205980,"windows":3,"clean_windows":3},{"conc":2,"rps":{"value":9,"certified":true,"suppressed":false},"p99_us":210027,"windows":3,"clean_windows":3},{"conc":4,"rps":{"value":18,"certified":true,"suppressed":false},"p99_us":231037,"windows":3,"clean_windows":3},{"conc":8,"rps":{"value":21,"certified":true,"suppressed":false},"p99_us":862107,"windows":3,"clean_windows":3},{"conc":16,"rps":{"value":20,"certified":true,"suppressed":false},"p99_us":1701780,"windows":3,"clean_windows":3},{"conc":32,"rps":{"value":17,"certified":true,"suppressed":false},"p99_us":3708317,"windows":3,"clean_windows":3},{"conc":64,"rps":{"value":14,"certified":true,"suppressed":false},"p99_us":5791176,"windows":3,"clean_windows":3},{"conc":128,"rps":{"value":3,"certified":true,"suppressed":false},"p99_us":5697032,"windows":3,"clean_windows":3},{"conc":256,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"no window at c=256 was clean: 0 of 3 failed requests, the rest carried no usable rate or failure count"},"p99_us":null,"windows":3,"clean_windows":0}],"egress_reverified":true,"c1_note":"the c=1 percentiles are taken over 30 successful gateway round trip(s) and 261879 direct-to-mock round trip(s), each leg a single clean window with no failures","gateway_c1_samples":30,"direct_c1_samples":261879},"stream":{"stream_served":true,"stream_error":null,"reason":null,"stream_c1_note":"the c=1 streaming legs read 64 frame(s) through the gateway and 64 direct to the mock, out of a 64 frame budget. The added-GAP figures are percentiles over the intervals inside those two streams. The added-TTFT figures are percentiles over separate probes - 100 through the gateway and 100 direct, out of 100 attempted per leg - so they carry that weight and no more","added_ttft_p50_us":{"value":156909,"certified":true,"suppressed":false},"added_ttft_p99_us":{"value":168479,"certified":true,"suppressed":false},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21072us) came in under the mock's (21073us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing"},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21139us) came in under the mock's (21149us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing"},"streams_sustained_fps":{"value":787.6218019669257,"certified":true,"suppressed":false,"headroom":0.329921366515401,"rig_ceiling":2387.3015873015875},"streams_sustained":{"value":47,"certified":true,"suppressed":false,"headroom":0.329921366515401,"rig_ceiling":2387.3015873015875},"ttft_gw_samples":100,"ttft_direct_samples":100,"gap_gw_samples":63,"gap_direct_samples":63},"memory":{"protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","served":true,"serve_error":"","load_recipe":null,"idle_rss_mib":{"value":605.86328125,"certified":true,"suppressed":false},"steady_state_rss_mib":{"value":961.5234375,"certified":true,"suppressed":false},"recovered_rss_mib":{"value":961.328125,"certified":true,"suppressed":false},"peak_rss_mib":{"value":961.90625,"certified":true,"suppressed":false},"peak_rss_hwm_mib":{"value":961.73046875,"certified":true,"suppressed":false},"plateaued":true,"time_to_plateau_s":{"value":61,"certified":true,"suppressed":false},"growth_rate_mib_per_min":{"value":0.20581317972839427,"certified":true,"suppressed":false},"load_s":{"value":304,"certified":true,"suppressed":false},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"idle_static":{"value":1,"certified":true,"suppressed":false},"idle_growth_rate_mib_per_min":{"value":0.17242880842301658,"certified":true,"suppressed":false},"rss_series":[{"t_s":0,"rss_mib":608.41015625},{"t_s":2,"rss_mib":957.85546875},{"t_s":2,"rss_mib":957.85546875},{"t_s":5,"rss_mib":958.31640625},{"t_s":5,"rss_mib":958.31640625},{"t_s":8,"rss_mib":958.953125},{"t_s":9,"rss_mib":958.98828125},{"t_s":11,"rss_mib":959.1484375},{"t_s":12,"rss_mib":959.1484375},{"t_s":14,"rss_mib":959.31640625},{"t_s":15,"rss_mib":959.31640625},{"t_s":17,"rss_mib":959.52734375},{"t_s":18,"rss_mib":959.53125},{"t_s":20,"rss_mib":959.71875},{"t_s":21,"rss_mib":959.71875},{"t_s":24,"rss_mib":959.796875},{"t_s":24,"rss_mib":959.796875},{"t_s":27,"rss_mib":959.93359375},{"t_s":29,"rss_mib":959.95703125},{"t_s":29,"rss_mib":959.83203125},{"t_s":30,"rss_mib":959.83984375},{"t_s":33,"rss_mib":959.859375},{"t_s":33,"rss_mib":959.80859375},{"t_s":36,"rss_mib":959.890625},{"t_s":36,"rss_mib":959.890625},{"t_s":38,"rss_mib":959.96484375},{"t_s":41,"rss_mib":959.9296875},{"t_s":41,"rss_mib":959.83984375},{"t_s":42,"rss_mib":959.8515625},{"t_s":45,"rss_mib":960.1328125},{"t_s":47,"rss_mib":960.01171875},{"t_s":48,"rss_mib":960.2109375},{"t_s":48,"rss_mib":960.2109375},{"t_s":51,"rss_mib":960.30859375},{"t_s":51,"rss_mib":960.30859375},{"t_s":54,"rss_mib":960.328125},{"t_s":54,"rss_mib":960.328125},{"t_s":56,"rss_mib":960.375},{"t_s":57,"rss_mib":960.375},{"t_s":60,"rss_mib":960.40625},{"t_s":60,"rss_mib":960.40625},{"t_s":63,"rss_mib":960.56640625},{"t_s":65,"rss_mib":960.65625},{"t_s":66,"rss_mib":960.5234375},{"t_s":67,"rss_mib":960.46484375},{"t_s":69,"rss_mib":960.58984375},{"t_s":69,"rss_mib":960.58984375},{"t_s":71,"rss_mib":960.6328125},{"t_s":73,"rss_mib":960.4453125},{"t_s":75,"rss_mib":960.8671875},{"t_s":76,"rss_mib":960.87109375},{"t_s":78,"rss_mib":960.93359375},{"t_s":79,"rss_mib":960.93359375},{"t_s":81,"rss_mib":961.05078125},{"t_s":82,"rss_mib":961.05078125},{"t_s":84,"rss_mib":961.08984375},{"t_s":85,"rss_mib":961.09765625},{"t_s":87,"rss_mib":960.765625},{"t_s":88,"rss_mib":960.765625},{"t_s":90,"rss_mib":960.8046875},{"t_s":91,"rss_mib":960.8046875},{"t_s":91,"rss_mib":960.81640625},{"t_s":94,"rss_mib":960.81640625},{"t_s":96,"rss_mib":960.64453125},{"t_s":97,"rss_mib":960.64453125},{"t_s":97,"rss_mib":960.63671875},{"t_s":100,"rss_mib":960.640625},{"t_s":103,"rss_mib":960.65234375},{"t_s":103,"rss_mib":960.65234375},{"t_s":106,"rss_mib":960.6796875},{"t_s":106,"rss_mib":960.6796875},{"t_s":109,"rss_mib":960.78125},{"t_s":109,"rss_mib":960.78515625},{"t_s":112,"rss_mib":960.87109375},{"t_s":112,"rss_mib":960.87109375},{"t_s":115,"rss_mib":960.8984375},{"t_s":115,"rss_mib":960.8984375},{"t_s":117,"rss_mib":960.87890625},{"t_s":121,"rss_mib":960.890625},{"t_s":121,"rss_mib":960.7421875},{"t_s":122,"rss_mib":960.68359375},{"t_s":124,"rss_mib":960.83984375},{"t_s":124,"rss_mib":960.796875},{"t_s":126,"rss_mib":960.765625},{"t_s":128,"rss_mib":960.73046875},{"t_s":130,"rss_mib":961.02734375},{"t_s":131,"rss_mib":961.05859375},{"t_s":132,"rss_mib":960.99609375},{"t_s":133,"rss_mib":961.046875},{"t_s":135,"rss_mib":961.0625},{"t_s":139,"rss_mib":961.05859375},{"t_s":139,"rss_mib":960.96484375},{"t_s":139,"rss_mib":960.96875},{"t_s":142,"rss_mib":960.9921875},{"t_s":143,"rss_mib":960.9921875},{"t_s":145,"rss_mib":961.05078125},{"t_s":146,"rss_mib":961.05859375},{"t_s":148,"rss_mib":961.15234375},{"t_s":149,"rss_mib":961.15234375},{"t_s":151,"rss_mib":961.1796875},{"t_s":152,"rss_mib":961.1875},{"t_s":153,"rss_mib":961.08984375},{"t_s":155,"rss_mib":961.09375},{"t_s":158,"rss_mib":961.30859375},{"t_s":158,"rss_mib":961.31640625},{"t_s":160,"rss_mib":961.32421875},{"t_s":161,"rss_mib":961.32421875},{"t_s":162,"rss_mib":961.33984375},{"t_s":164,"rss_mib":961.33984375},{"t_s":166,"rss_mib":961.359375},{"t_s":167,"rss_mib":961.359375},{"t_s":170,"rss_mib":961.640625},{"t_s":170,"rss_mib":961.640625},{"t_s":173,"rss_mib":961.671875},{"t_s":173,"rss_mib":961.671875},{"t_s":175,"rss_mib":961.7109375},{"t_s":176,"rss_mib":961.6640625},{"t_s":178,"rss_mib":961.71875},{"t_s":179,"rss_mib":961.72265625},{"t_s":182,"rss_mib":961.5703125},{"t_s":182,"rss_mib":961.5703125},{"t_s":183,"rss_mib":961.59765625},{"t_s":185,"rss_mib":961.578125},{"t_s":187,"rss_mib":961.58984375},{"t_s":188,"rss_mib":961.58984375},{"t_s":189,"rss_mib":961.59765625},{"t_s":191,"rss_mib":961.59765625},{"t_s":192,"rss_mib":961.60546875},{"t_s":194,"rss_mib":961.60546875},{"t_s":196,"rss_mib":961.4296875},{"t_s":197,"rss_mib":961.44140625},{"t_s":199,"rss_mib":961.4296875},{"t_s":200,"rss_mib":961.44140625},{"t_s":203,"rss_mib":961.49609375},{"t_s":203,"rss_mib":961.49609375},{"t_s":206,"rss_mib":961.50390625},{"t_s":206,"rss_mib":961.50390625},{"t_s":209,"rss_mib":961.671875},{"t_s":209,"rss_mib":961.671875},{"t_s":211,"rss_mib":961.6953125},{"t_s":213,"rss_mib":961.6953125},{"t_s":215,"rss_mib":961.3984375},{"t_s":217,"rss_mib":961.40625},{"t_s":218,"rss_mib":961.37109375},{"t_s":219,"rss_mib":961.2578125},{"t_s":221,"rss_mib":961.296875},{"t_s":222,"rss_mib":961.296875},{"t_s":225,"rss_mib":961.43359375},{"t_s":225,"rss_mib":961.43359375},{"t_s":226,"rss_mib":961.4609375},{"t_s":228,"rss_mib":961.46875},{"t_s":231,"rss_mib":961.31640625},{"t_s":231,"rss_mib":961.3203125},{"t_s":233,"rss_mib":961.3359375},{"t_s":234,"rss_mib":961.3359375},{"t_s":237,"rss_mib":961.3515625},{"t_s":237,"rss_mib":961.3515625},{"t_s":240,"rss_mib":961.3515625},{"t_s":241,"rss_mib":961.25},{"t_s":243,"rss_mib":961.2734375},{"t_s":245,"rss_mib":961.23828125},{"t_s":246,"rss_mib":961.23828125},{"t_s":249,"rss_mib":961.3359375},{"t_s":249,"rss_mib":961.3359375},{"t_s":252,"rss_mib":961.54296875},{"t_s":252,"rss_mib":961.54296875},{"t_s":255,"rss_mib":961.62109375},{"t_s":255,"rss_mib":961.65234375},{"t_s":257,"rss_mib":961.46484375},{"t_s":258,"rss_mib":961.46875},{"t_s":261,"rss_mib":961.52734375},{"t_s":261,"rss_mib":961.52734375},{"t_s":263,"rss_mib":961.84765625},{"t_s":264,"rss_mib":961.84765625},{"t_s":266,"rss_mib":961.90625},{"t_s":267,"rss_mib":961.90625},{"t_s":270,"rss_mib":961.66796875},{"t_s":271,"rss_mib":961.67578125},{"t_s":273,"rss_mib":961.66015625},{"t_s":273,"rss_mib":961.66015625},{"t_s":273,"rss_mib":961.5234375},{"t_s":276,"rss_mib":961.5390625},{"t_s":279,"rss_mib":961.90234375},{"t_s":279,"rss_mib":961.7890625},{"t_s":282,"rss_mib":961.88671875},{"t_s":283,"rss_mib":961.88671875},{"t_s":285,"rss_mib":961.90234375},{"t_s":286,"rss_mib":961.90234375},{"t_s":287,"rss_mib":961.859375},{"t_s":289,"rss_mib":961.86328125},{"t_s":291,"rss_mib":961.87890625},{"t_s":292,"rss_mib":961.87890625},{"t_s":294,"rss_mib":961.7578125},{"t_s":295,"rss_mib":961.7578125},{"t_s":295,"rss_mib":961.41796875},{"t_s":298,"rss_mib":961.4375},{"t_s":301,"rss_mib":961.44921875},{"t_s":303,"rss_mib":961.44140625},{"t_s":304,"rss_mib":961.4453125},{"t_s":304,"rss_mib":961.3203125},{"t_s":307,"rss_mib":961.32421875},{"t_s":310,"rss_mib":961.32421875},{"t_s":313,"rss_mib":961.32421875},{"t_s":316,"rss_mib":961.32421875},{"t_s":319,"rss_mib":961.32421875},{"t_s":322,"rss_mib":961.32421875},{"t_s":324,"rss_mib":961.328125},{"t_s":325,"rss_mib":961.328125},{"t_s":328,"rss_mib":961.328125},{"t_s":331,"rss_mib":961.328125},{"t_s":334,"rss_mib":961.328125},{"t_s":337,"rss_mib":961.328125},{"t_s":340,"rss_mib":961.328125},{"t_s":343,"rss_mib":961.328125},{"t_s":346,"rss_mib":961.328125},{"t_s":349,"rss_mib":961.328125},{"t_s":352,"rss_mib":961.328125},{"t_s":355,"rss_mib":961.328125},{"t_s":358,"rss_mib":961.328125},{"t_s":361,"rss_mib":961.328125},{"t_s":364,"rss_mib":961.328125}],"idle_rss_series":[{"t_s":0,"rss_mib":605.6953125},{"t_s":0,"rss_mib":605.6953125},{"t_s":0,"rss_mib":605.6953125},{"t_s":1,"rss_mib":605.6953125},{"t_s":1,"rss_mib":605.6953125},{"t_s":2,"rss_mib":605.6953125},{"t_s":2,"rss_mib":605.6953125},{"t_s":3,"rss_mib":605.6953125},{"t_s":3,"rss_mib":605.69921875},{"t_s":4,"rss_mib":605.69921875},{"t_s":4,"rss_mib":605.69921875},{"t_s":4,"rss_mib":605.69921875},{"t_s":5,"rss_mib":605.69921875},{"t_s":5,"rss_mib":605.69921875},{"t_s":6,"rss_mib":605.69921875},{"t_s":6,"rss_mib":605.765625},{"t_s":6,"rss_mib":605.765625},{"t_s":7,"rss_mib":605.765625},{"t_s":8,"rss_mib":605.765625},{"t_s":8,"rss_mib":605.765625},{"t_s":8,"rss_mib":605.765625},{"t_s":9,"rss_mib":605.765625},{"t_s":9,"rss_mib":605.765625},{"t_s":10,"rss_mib":605.765625},{"t_s":10,"rss_mib":605.76953125},{"t_s":10,"rss_mib":605.76953125},{"t_s":11,"rss_mib":605.76953125},{"t_s":11,"rss_mib":605.7734375},{"t_s":12,"rss_mib":605.7734375},{"t_s":12,"rss_mib":605.7734375},{"t_s":12,"rss_mib":605.77734375},{"t_s":12,"rss_mib":605.77734375},{"t_s":13,"rss_mib":605.77734375},{"t_s":13,"rss_mib":605.78125},{"t_s":13,"rss_mib":605.78125},{"t_s":14,"rss_mib":605.7890625},{"t_s":14,"rss_mib":605.7890625},{"t_s":14,"rss_mib":605.7890625},{"t_s":15,"rss_mib":605.7890625},{"t_s":15,"rss_mib":605.79296875},{"t_s":16,"rss_mib":605.79296875},{"t_s":16,"rss_mib":605.79296875},{"t_s":16,"rss_mib":605.796875},{"t_s":16,"rss_mib":605.796875},{"t_s":17,"rss_mib":605.796875},{"t_s":17,"rss_mib":605.8046875},{"t_s":17,"rss_mib":605.8046875},{"t_s":18,"rss_mib":605.8046875},{"t_s":18,"rss_mib":605.8046875},{"t_s":19,"rss_mib":605.80859375},{"t_s":19,"rss_mib":605.80859375},{"t_s":19,"rss_mib":605.8125},{"t_s":20,"rss_mib":605.8125},{"t_s":20,"rss_mib":605.8125},{"t_s":20,"rss_mib":605.81640625},{"t_s":20,"rss_mib":605.81640625},{"t_s":21,"rss_mib":605.81640625},{"t_s":21,"rss_mib":605.82421875},{"t_s":21,"rss_mib":605.82421875},{"t_s":22,"rss_mib":605.82421875},{"t_s":23,"rss_mib":605.82421875},{"t_s":23,"rss_mib":605.828125},{"t_s":23,"rss_mib":605.828125},{"t_s":23,"rss_mib":605.83203125},{"t_s":24,"rss_mib":605.83203125},{"t_s":24,"rss_mib":605.83203125},{"t_s":24,"rss_mib":605.8359375},{"t_s":24,"rss_mib":605.8359375},{"t_s":25,"rss_mib":605.8359375},{"t_s":25,"rss_mib":605.84765625},{"t_s":25,"rss_mib":605.84765625},{"t_s":26,"rss_mib":605.84765625},{"t_s":27,"rss_mib":605.84765625},{"t_s":27,"rss_mib":605.8515625},{"t_s":27,"rss_mib":605.8515625},{"t_s":27,"rss_mib":605.85546875},{"t_s":28,"rss_mib":605.85546875},{"t_s":28,"rss_mib":605.85546875},{"t_s":28,"rss_mib":605.859375},{"t_s":28,"rss_mib":605.859375},{"t_s":29,"rss_mib":605.859375},{"t_s":29,"rss_mib":605.86328125},{"t_s":29,"rss_mib":605.86328125},{"t_s":30,"rss_mib":605.86328125},{"t_s":31,"rss_mib":605.86328125},{"t_s":31,"rss_mib":605.86328125},{"t_s":32,"rss_mib":605.86328125},{"t_s":32,"rss_mib":605.86328125},{"t_s":32,"rss_mib":605.86328125},{"t_s":33,"rss_mib":605.86328125},{"t_s":33,"rss_mib":605.8671875},{"t_s":33,"rss_mib":605.8671875},{"t_s":34,"rss_mib":605.8671875},{"t_s":35,"rss_mib":605.8671875},{"t_s":35,"rss_mib":605.8671875},{"t_s":36,"rss_mib":605.8671875},{"t_s":36,"rss_mib":605.8671875},{"t_s":36,"rss_mib":605.8671875},{"t_s":37,"rss_mib":605.8671875},{"t_s":37,"rss_mib":605.8671875},{"t_s":38,"rss_mib":605.8671875},{"t_s":39,"rss_mib":605.8671875},{"t_s":39,"rss_mib":605.8671875},{"t_s":40,"rss_mib":605.8671875},{"t_s":40,"rss_mib":605.8671875},{"t_s":40,"rss_mib":605.8671875},{"t_s":41,"rss_mib":605.8671875},{"t_s":41,"rss_mib":605.8671875},{"t_s":42,"rss_mib":605.8671875},{"t_s":43,"rss_mib":605.8671875},{"t_s":43,"rss_mib":605.8671875},{"t_s":44,"rss_mib":605.8671875},{"t_s":44,"rss_mib":605.8671875},{"t_s":44,"rss_mib":605.8671875},{"t_s":45,"rss_mib":605.8671875},{"t_s":45,"rss_mib":605.8671875},{"t_s":46,"rss_mib":605.8671875},{"t_s":47,"rss_mib":605.8671875},{"t_s":47,"rss_mib":605.8671875},{"t_s":48,"rss_mib":605.8671875},{"t_s":48,"rss_mib":605.8671875},{"t_s":48,"rss_mib":605.8671875},{"t_s":49,"rss_mib":605.8671875},{"t_s":49,"rss_mib":605.8671875},{"t_s":50,"rss_mib":605.8671875},{"t_s":51,"rss_mib":605.8671875},{"t_s":51,"rss_mib":605.8671875},{"t_s":52,"rss_mib":605.8671875},{"t_s":52,"rss_mib":605.8671875},{"t_s":52,"rss_mib":605.8671875},{"t_s":53,"rss_mib":605.8671875},{"t_s":54,"rss_mib":605.8671875},{"t_s":54,"rss_mib":605.8671875},{"t_s":55,"rss_mib":605.8671875},{"t_s":55,"rss_mib":605.8671875},{"t_s":56,"rss_mib":605.8671875},{"t_s":56,"rss_mib":605.8671875},{"t_s":56,"rss_mib":605.8671875},{"t_s":57,"rss_mib":605.8671875},{"t_s":58,"rss_mib":605.8671875},{"t_s":58,"rss_mib":605.8671875},{"t_s":59,"rss_mib":605.8671875},{"t_s":59,"rss_mib":605.8671875},{"t_s":59,"rss_mib":605.8671875}],"idle_window_s":60,"recovery_window_s":30},"timings_s":{"added_latency":12.069305536,"cost":6.097078105,"memory":430.468900989,"streaming":18.470591674,"streams_sustained":41.722933667,"throughput":197.425610602},"upstream_transport":"http","absences":{"memory.idle_shape":{"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe"},"memory.shape":{"reason":"not_measured","detail":"a settled window has no unsettled shape to describe"},"perf.frontier.100ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.100ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.10ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.1ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.50ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.concurrency":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.p99_us":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.rps":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.frontier.5ms.samples":{"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"perf.sweep.c256.w1.p99_us":{"reason":"not_measured"},"perf.sweep.c256.w2.p99_us":{"reason":"not_measured"},"perf.sweep.c256.w3.p99_us":{"reason":"not_measured"},"stream.added_gap_p50_us":{"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21072us) came in under the mock's (21073us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing"},"stream.added_gap_p99_us":{"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21139us) came in under the mock's (21149us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing"}}},"cohere":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v2/chat","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}},"gemini":{"served":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","status":"","path":"/v1beta/models/openai/gpt-4o-mini:generateContent","verdict_note":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","body_snippet":"","probe_note":null,"perf_dropped":null,"perf":null,"stream":null,"memory":null,"timings_s":null,"upstream_transport":null,"absences":{}}}}},"model":null,"upstream_endpoint":null,"ootb_config":null,"arch":"arm64","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","rig":{"arch":"arm64","release_url":"file:///home/ubuntu/benchmarking/rig","engine":{"commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","dirty":false},"mock":{"origin":"release","sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","asset_updated_at":null},"ugen":null,"box_qualify":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"somaxconn":65535,"tcp_max_syn_backlog":65535},"measured_at":"2026-11-10T17:40:07Z","started_at":null,"finished_at":null,"duration_s":null,"phase_s":null,"build_env":null},"matrix_from_snapshot":true,"snapshot_file":"result_plano_2026-11-10T17-40-07Z.json","ootb_config":"# Plano, configured as an LLM gateway pointed at the harness mock.\n#\n# `type: model` is the LLM listener; `type: agent` is the orchestration listener the project's README\n# leads with, and it is NOT what this benchmark measures - an agent listener would put Plano's router\n# and its agent hop inside a number the rest of the field takes without one.\n#\n# The listener port is 12000, not 10000. Plano always renders a prompt-gateway listener on 10000\n# (utils.py convert_legacy_listeners), so an LLM listener on 10000 double-binds and envoy exits at\n# boot with \"'egress_traffic' has duplicate address '0.0.0.0:10000'\". 12000 is Plano's own default\n# for this listener.\n#\n# NO provider_interface key here, deliberately. When the model prefix is one Plano already knows -\n# openai, anthropic and gemini all are - setting provider_interface as well is rejected by\n# config_generator.py:445, which then exits and takes the container down with it. The prefix selects\n# the interface on its own. (The error text reads \"Please provide provider interface as part of model\n# name\", which is the reverse of what the check does; the condition is `provider in\n# SUPPORTED_PROVIDERS and provider_interface is not None`.)\n#\n# base_url is what makes Plano testable at all: several entrants pin the vendor host and their\n# upstream cells can only be recorded untestable. Plano's model_providers take base_url, so the mock\n# stands in for every provider and the measured number is Plano's own cost.\n#\n# Provider prefixes select the released adapters. Capability declarations are source-backed in\n# definition.json; correct ingress and upstream wire shapes are checked separately.\nversion: v0.3.0\n\nlisteners:\n  - name: llm\n    type: model\n    port: 12000\n\nmodel_providers:\n  - model: openai/gpt-4o-mini\n    base_url: 'http://127.0.0.1:8000'\n    access_key: dummy\n    default: true\n\n  - model: anthropic/claude-3-5-sonnet\n    base_url: 'http://127.0.0.1:8000'\n    access_key: dummy\n\n  - model: gemini/gemini-1.5-pro\n    base_url: 'http://127.0.0.1:8000'\n    access_key: dummy\n\n  - model: amazon_bedrock/anthropic.claude-3-sonnet-20240229-v1:0\n    base_url: 'http://127.0.0.1:8000'\n    access_key: dummy\n","best_cell":{"path":{"ingress":"openai","egress":"openai","dialect":"openai"},"source":{"kind":"matrix","sweep":"6x6-diagonal","build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","measured_at":"2026-11-10T17:40:07Z"},"added_latency_p50_us":{"value":198988,"certified":true,"suppressed":false},"added_latency_p99_us":{"value":205966,"certified":true,"suppressed":false},"gateway_c1_p99_us":{"value":205993,"certified":true,"suppressed":false},"direct_c1_p99_us":{"value":27,"certified":true,"suppressed":false},"cpu_us_per_request":{"value":182230.76923076922,"certified":true,"suppressed":false},"rps_per_cpu_second":{"value":5.487547488391726,"certified":true,"suppressed":false},"cost_window_conc":{"value":8,"certified":true,"suppressed":false},"cost_core_utilisation":{"value":0.9645138811621244,"certified":true,"suppressed":false},"cost_window_ok":{"value":130,"certified":true,"suppressed":false},"cost_window_rps":{"value":21,"certified":true,"suppressed":false},"cost_threads":{"value":68,"certified":true,"suppressed":false},"cost_nonvol_ctxt_per_request":{"value":6.276923076923077,"certified":true,"suppressed":false},"cost_majflt":{"value":0,"certified":true,"suppressed":false},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":19,"certified":true,"suppressed":false},"concurrency":8,"p99_us":788018,"first_disqualified_conc":512,"lower_bound":false,"samples":118}],"sweep":[{"conc":1,"ok":28,"rps":4,"p99_us":222019,"fail":0},{"conc":1,"ok":27,"rps":4,"p99_us":226987,"fail":0},{"conc":1,"ok":27,"rps":4,"p99_us":226040,"fail":0},{"conc":2,"ok":54,"rps":8,"p99_us":226976,"fail":0},{"conc":2,"ok":54,"rps":8,"p99_us":232019,"fail":0},{"conc":2,"ok":54,"rps":8,"p99_us":226037,"fail":0},{"conc":4,"ok":103,"rps":17,"p99_us":381484,"fail":0},{"conc":4,"ok":104,"rps":17,"p99_us":243028,"fail":0},{"conc":4,"ok":104,"rps":17,"p99_us":249980,"fail":0},{"conc":8,"ok":116,"rps":19,"p99_us":835542,"fail":0},{"conc":8,"ok":119,"rps":19,"p99_us":894372,"fail":0},{"conc":8,"ok":118,"rps":19,"p99_us":788018,"fail":0},{"conc":16,"ok":106,"rps":17,"p99_us":2709689,"fail":0},{"conc":16,"ok":105,"rps":17,"p99_us":1735658,"fail":0},{"conc":16,"ok":108,"rps":17,"p99_us":3187551,"fail":0},{"conc":32,"ok":92,"rps":14,"p99_us":4352830,"fail":0},{"conc":32,"ok":93,"rps":15,"p99_us":5329620,"fail":0},{"conc":32,"ok":92,"rps":14,"p99_us":5323515,"fail":0},{"conc":64,"ok":75,"rps":12,"p99_us":5366599,"fail":0},{"conc":64,"ok":69,"rps":11,"p99_us":5616397,"fail":0},{"conc":64,"ok":76,"rps":12,"p99_us":5804402,"fail":0},{"conc":128,"ok":17,"rps":2,"p99_us":5168419,"fail":0},{"conc":128,"ok":30,"rps":4,"p99_us":5829489,"fail":0},{"conc":128,"ok":28,"rps":4,"p99_us":5315007,"fail":0},{"conc":256,"ok":12,"rps":1,"p99_us":4553055,"fail":0},{"conc":256,"ok":11,"rps":1,"p99_us":5897693,"fail":0},{"conc":256,"ok":15,"rps":2,"p99_us":5811545,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":512,"ok":0,"rps":0,"p99_us":null,"fail":0}],"rungs":[{"conc":1,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":226040,"windows":3,"clean_windows":3},{"conc":2,"rps":{"value":8,"certified":true,"suppressed":false},"p99_us":226976,"windows":3,"clean_windows":3},{"conc":4,"rps":{"value":17,"certified":true,"suppressed":false},"p99_us":249980,"windows":3,"clean_windows":3},{"conc":8,"rps":{"value":19,"certified":true,"suppressed":false},"p99_us":835542,"windows":3,"clean_windows":3},{"conc":16,"rps":{"value":17,"certified":true,"suppressed":false},"p99_us":2709689,"windows":3,"clean_windows":3},{"conc":32,"rps":{"value":14,"certified":true,"suppressed":false},"p99_us":5323515,"windows":3,"clean_windows":3},{"conc":64,"rps":{"value":12,"certified":true,"suppressed":false},"p99_us":5616397,"windows":3,"clean_windows":3},{"conc":128,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":5315007,"windows":3,"clean_windows":3},{"conc":256,"rps":{"value":1,"certified":true,"suppressed":false},"p99_us":5811545,"windows":3,"clean_windows":3},{"conc":512,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"no window at c=512 was clean: 0 of 3 failed requests, the rest carried no usable rate or failure count"},"p99_us":null,"windows":3,"clean_windows":0}],"reverify_note":"openai>openai is a same-dialect cell: there is no translation to prove, so a request-shape check upstream cannot distinguish a translating gateway from a forwarding one","c1_note":"the c=1 percentiles are taken over 30 successful gateway round trip(s) and 266566 direct-to-mock round trip(s), each leg a single clean window with no failures","gateway_c1_samples":30,"direct_c1_samples":266566,"rps_per_dollar":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"cost_per_million_usd":{"value":null,"certified":false,"suppressed":false,"reason":"not_applicable","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound - so cost per request at the 10 ms bound is undefined, not $0"},"priced_at_bound_ms":10,"gateway_hourly_usd":0.1632},"translation_cell":{"path":{"ingress":"openai","egress":"bedrock"},"source":{"kind":"matrix","sweep":"6x6-translation","build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","measured_at":"2026-11-10T17:40:07Z"},"added_latency_p50_us":{"value":205998,"certified":true,"suppressed":false},"added_latency_p99_us":{"value":212984,"certified":true,"suppressed":false},"gateway_c1_p99_us":{"value":213012,"certified":true,"suppressed":false},"direct_c1_p99_us":{"value":28,"certified":true,"suppressed":false},"cpu_us_per_request":{"value":189176.47058823527,"certified":true,"suppressed":false},"rps_per_cpu_second":{"value":5.286069651741294,"certified":true,"suppressed":false},"cost_window_conc":{"value":8,"certified":true,"suppressed":false},"cost_core_utilisation":{"value":0.6169920805069831,"certified":true,"suppressed":false},"cost_window_ok":{"value":85,"certified":true,"suppressed":false},"cost_window_rps":{"value":14,"certified":true,"suppressed":false},"cost_threads":{"value":68,"certified":true,"suppressed":false},"cost_nonvol_ctxt_per_request":{"value":5.141176470588236,"certified":true,"suppressed":false},"cost_majflt":{"value":0,"certified":true,"suppressed":false},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false},"concurrency":8,"p99_us":831737,"first_disqualified_conc":256,"lower_bound":false,"samples":127}],"sweep":[{"conc":1,"ok":29,"rps":4,"p99_us":208994,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":201000,"fail":0},{"conc":1,"ok":30,"rps":4,"p99_us":210011,"fail":0},{"conc":2,"ok":32,"rps":5,"p99_us":378986,"fail":0},{"conc":2,"ok":32,"rps":5,"p99_us":384977,"fail":0},{"conc":2,"ok":32,"rps":5,"p99_us":378725,"fail":0},{"conc":4,"ok":89,"rps":14,"p99_us":391015,"fail":0},{"conc":4,"ok":84,"rps":13,"p99_us":392647,"fail":0},{"conc":4,"ok":88,"rps":14,"p99_us":388017,"fail":0},{"conc":8,"ok":126,"rps":20,"p99_us":727628,"fail":0},{"conc":8,"ok":126,"rps":20,"p99_us":724829,"fail":0},{"conc":8,"ok":127,"rps":21,"p99_us":831737,"fail":0},{"conc":16,"ok":113,"rps":18,"p99_us":2128828,"fail":0},{"conc":16,"ok":115,"rps":19,"p99_us":3168838,"fail":0},{"conc":16,"ok":114,"rps":18,"p99_us":2209817,"fail":0},{"conc":32,"ok":101,"rps":16,"p99_us":3094514,"fail":0},{"conc":32,"ok":102,"rps":16,"p99_us":3335594,"fail":0},{"conc":32,"ok":92,"rps":14,"p99_us":5131938,"fail":0},{"conc":64,"ok":72,"rps":11,"p99_us":5716273,"fail":0},{"conc":64,"ok":76,"rps":12,"p99_us":5912282,"fail":0},{"conc":64,"ok":79,"rps":13,"p99_us":5476791,"fail":0},{"conc":128,"ok":13,"rps":2,"p99_us":5800221,"fail":0},{"conc":128,"ok":41,"rps":6,"p99_us":5913884,"fail":0},{"conc":128,"ok":26,"rps":4,"p99_us":5066908,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0},{"conc":256,"ok":0,"rps":0,"p99_us":null,"fail":0}],"rungs":[{"conc":1,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":208994,"windows":3,"clean_windows":3},{"conc":2,"rps":{"value":5,"certified":true,"suppressed":false},"p99_us":378986,"windows":3,"clean_windows":3},{"conc":4,"rps":{"value":14,"certified":true,"suppressed":false},"p99_us":391015,"windows":3,"clean_windows":3},{"conc":8,"rps":{"value":20,"certified":true,"suppressed":false},"p99_us":727628,"windows":3,"clean_windows":3},{"conc":16,"rps":{"value":18,"certified":true,"suppressed":false},"p99_us":2209817,"windows":3,"clean_windows":3},{"conc":32,"rps":{"value":16,"certified":true,"suppressed":false},"p99_us":3335594,"windows":3,"clean_windows":3},{"conc":64,"rps":{"value":12,"certified":true,"suppressed":false},"p99_us":5716273,"windows":3,"clean_windows":3},{"conc":128,"rps":{"value":4,"certified":true,"suppressed":false},"p99_us":5800221,"windows":3,"clean_windows":3},{"conc":256,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"no window at c=256 was clean: 0 of 3 failed requests, the rest carried no usable rate or failure count"},"p99_us":null,"windows":3,"clean_windows":0}],"egress_reverified":true,"c1_note":"the c=1 percentiles are taken over 29 successful gateway round trip(s) and 262765 direct-to-mock round trip(s), each leg a single clean window with no failures","gateway_c1_samples":29,"direct_c1_samples":262765},"streaming":{"path":{"dialect":"openai"},"source":{"kind":"matrix","sweep":"6x6-stream-diagonal","build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","measured_at":"2026-11-10T17:40:07Z"},"stream_served":true,"added_ttft_p50_us":{"value":158773,"certified":true,"suppressed":false},"added_ttft_p99_us":{"value":170494,"certified":true,"suppressed":false},"added_gap_p50_us":{"value":1,"certified":true,"suppressed":false},"added_gap_p99_us":{"value":38,"certified":true,"suppressed":false},"streams_sustained_fps":{"value":669.7194949393278,"certified":true,"suppressed":false,"headroom":0.4546587088488971,"rig_ceiling":1473.015873015873},"streams_sustained":{"value":29,"certified":true,"suppressed":false,"headroom":0.4546587088488971,"rig_ceiling":1473.015873015873},"ttft_gw_samples":100,"ttft_direct_samples":100,"gap_gw_samples":63,"gap_direct_samples":63},"measured_at":"2026-11-10T17:40:07.000Z","lane_measured_at":{"perf":"2026-11-10T17:40:07Z","xlate":"2026-11-10T17:40:07Z","stream":"2026-11-10T17:40:07Z","memory":"2026-11-10T17:40:07Z"},"rig":{"arch":"arm64","release_url":"file:///home/ubuntu/benchmarking/rig","engine":{"commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","dirty":false},"mock":{"origin":"release","sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","asset_updated_at":null},"ugen":null,"box_qualify":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"somaxconn":65535,"tcp_max_syn_backlog":65535},"contributed_by":[],"stale":false,"engine":{"sha":"d240badd966933fa19eec0606b2d1f3945f18ad2","short":"d240bad","current":true},"history_family":"plano","history_trends":{}},"current_metadata":{"stars":7117,"stars_as_of":"2026-11-14","first_commit":"2024-07-09"},"metadata_scope":"gateway.stars and stars_as_of are legacy aliases of current_metadata, a dated repository snapshot, not stars at measurement time. Run statistics were not recorded.","measurements":[{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai:bedrock","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"served","raw_state":true,"reason":null,"detail":null,"evidence_scope":"Recorded run evidence","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai","upstream_protocol":"bedrock","upstream_transport":"http","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","memory_concurrency":null,"memory_load_s":306,"cost_concurrency":8,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{"added_latency_p50_us":{"value":205998,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"added_latency_p99_us":{"value":212984,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"gateway_c1_p99_us":{"value":213012,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"direct_c1_p99_us":{"value":28,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"cpu_us_per_request":{"value":189176.47058823527,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"rps_per_cpu_second":{"value":5.286069651741294,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_conc":{"value":8,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_core_utilisation":{"value":0.6169920805069831,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_ok":{"value":85,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_rps":{"value":14,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_threads":{"value":68,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_nonvol_ctxt_per_request":{"value":5.141176470588236,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_majflt":{"value":0,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"added_ttft_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_ttft_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"streams_sustained_fps":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"streams_sustained":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"idle_rss_mib":{"value":598.80078125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"steady_state_rss_mib":{"value":1006.28515625,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"recovered_rss_mib":{"value":1006.22265625,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_mib":{"value":1006.6875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_hwm_mib":{"value":1006.46875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"time_to_plateau_s":{"value":61,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"growth_rate_mib_per_min":{"value":-0.329296963138252,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"load_s":{"value":306,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_static":{"value":1,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_growth_rate_mib_per_min":{"value":0.046660991313913644,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."}},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false,"state":"valid","reason":null},"concurrency":8,"p99_us":831737,"first_disqualified_conc":256,"lower_bound":false,"samples":127}],"sample_counts":{"gateway_c1_samples":29,"direct_c1_samples":262765},"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:cohere:bedrock","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"cohere","upstream_protocol":"bedrock","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:gemini:bedrock","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"gemini","upstream_protocol":"bedrock","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai-responses:bedrock","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"served","raw_state":true,"reason":null,"detail":null,"evidence_scope":"Recorded run evidence","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai-responses","upstream_protocol":"bedrock","upstream_transport":"http","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","memory_concurrency":null,"memory_load_s":305,"cost_concurrency":8,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{"added_latency_p50_us":{"value":200013,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"added_latency_p99_us":{"value":205956,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"gateway_c1_p99_us":{"value":205984,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"direct_c1_p99_us":{"value":28,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"cpu_us_per_request":{"value":182500,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"rps_per_cpu_second":{"value":5.47945205479452,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_conc":{"value":8,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_core_utilisation":{"value":0.8586890105703885,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_ok":{"value":116,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_rps":{"value":19,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_threads":{"value":68,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_nonvol_ctxt_per_request":{"value":4.620689655172414,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_majflt":{"value":0,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"added_ttft_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_ttft_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"streams_sustained_fps":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"streams_sustained":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"idle_rss_mib":{"value":621.60546875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"steady_state_rss_mib":{"value":1055.50390625,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"recovered_rss_mib":{"value":1055.875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_mib":{"value":1055.9375,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_hwm_mib":{"value":1055.87109375,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"time_to_plateau_s":{"value":66,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"growth_rate_mib_per_min":{"value":0.07183335358262208,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"load_s":{"value":305,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_static":{"value":1,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_growth_rate_mib_per_min":{"value":0.04844942521841008,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."}},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":20,"certified":true,"suppressed":false,"state":"valid","reason":null},"concurrency":16,"p99_us":1943615,"first_disqualified_conc":512,"lower_bound":false,"samples":121}],"sample_counts":{"gateway_c1_samples":30,"direct_c1_samples":265071},"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:anthropic:bedrock","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"served","raw_state":true,"reason":null,"detail":null,"evidence_scope":"Recorded run evidence","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"anthropic","upstream_protocol":"bedrock","upstream_transport":"http","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","memory_concurrency":null,"memory_load_s":302,"cost_concurrency":8,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{"added_latency_p50_us":{"value":193978,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"added_latency_p99_us":{"value":197949,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"gateway_c1_p99_us":{"value":197977,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"direct_c1_p99_us":{"value":28,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"cpu_us_per_request":{"value":175360,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"rps_per_cpu_second":{"value":5.702554744525547,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_conc":{"value":8,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_core_utilisation":{"value":0.8601191828446305,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_ok":{"value":125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_rps":{"value":20,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_threads":{"value":68,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_nonvol_ctxt_per_request":{"value":5.32,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_majflt":{"value":0,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"added_ttft_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_ttft_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"streams_sustained_fps":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"streams_sustained":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer bedrock with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"idle_rss_mib":{"value":612.45703125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"steady_state_rss_mib":{"value":967.6796875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"recovered_rss_mib":{"value":967.421875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_mib":{"value":967.99609375,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_hwm_mib":{"value":967.70703125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"time_to_plateau_s":{"value":60,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"growth_rate_mib_per_min":{"value":0.25204829296188547,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"load_s":{"value":302,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_static":{"value":1,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_growth_rate_mib_per_min":{"value":0.05193333183537614,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."}},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false,"state":"valid","reason":null},"concurrency":16,"p99_us":1585939,"first_disqualified_conc":1024,"lower_bound":false,"samples":127}],"sample_counts":{"gateway_c1_samples":31,"direct_c1_samples":259772},"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:bedrock:bedrock","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"bedrock","upstream_protocol":"bedrock","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai:anthropic","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai","upstream_protocol":"anthropic","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai-responses:anthropic","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai-responses","upstream_protocol":"anthropic","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:anthropic:anthropic","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"served","raw_state":true,"reason":null,"detail":null,"evidence_scope":"Recorded run evidence","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"anthropic","upstream_protocol":"anthropic","upstream_transport":"http","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","memory_concurrency":null,"memory_load_s":303,"cost_concurrency":8,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{"added_latency_p50_us":{"value":193933,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"added_latency_p99_us":{"value":195022,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"gateway_c1_p99_us":{"value":195049,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"direct_c1_p99_us":{"value":27,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"cpu_us_per_request":{"value":181353.38345864663,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"rps_per_cpu_second":{"value":5.514096185737976,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_conc":{"value":8,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_core_utilisation":{"value":0.9610214676333437,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_ok":{"value":133,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_rps":{"value":22,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_threads":{"value":69,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_nonvol_ctxt_per_request":{"value":5.879699248120301,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_majflt":{"value":0,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"added_ttft_p50_us":{"value":153935,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_ttft_p99_us":{"value":165859,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21070us) came in under the mock's (21073us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing","state":"below_resolution","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21167us) came in under the mock's (21758us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing","state":"below_resolution","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"streams_sustained_fps":{"value":919.9861683706454,"certified":true,"suppressed":false,"headroom":0.2786496567661089,"rig_ceiling":3301.5873015873017,"state":"valid","reason":null,"section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"streams_sustained":{"value":65,"certified":true,"suppressed":false,"headroom":0.2786496567661089,"rig_ceiling":3301.5873015873017,"state":"valid","reason":null,"section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"idle_rss_mib":{"value":593.06640625,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"steady_state_rss_mib":{"value":948.5078125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"recovered_rss_mib":{"value":948.43359375,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_mib":{"value":949.0078125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_hwm_mib":{"value":948.77734375,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"time_to_plateau_s":{"value":67,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"growth_rate_mib_per_min":{"value":-0.30135980491154135,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"load_s":{"value":303,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_static":{"value":1,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_growth_rate_mib_per_min":{"value":0.05169704844231903,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."}},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false,"state":"valid","reason":null},"concurrency":8,"p99_us":559997,"first_disqualified_conc":512,"lower_bound":false,"samples":128}],"sample_counts":{"gateway_c1_samples":31,"direct_c1_samples":264589,"ttft_gw_samples":100,"ttft_direct_samples":100,"gap_gw_samples":63,"gap_direct_samples":63},"stream_rung_diagnostics":[{"conc":1,"http_status_counts":{"200":1},"stream_errors_no_response":0},{"conc":2,"http_status_counts":{"200":2},"stream_errors_no_response":0},{"conc":4,"http_status_counts":{"200":4},"stream_errors_no_response":0},{"conc":8,"http_status_counts":{"200":8},"stream_errors_no_response":0},{"conc":16,"http_status_counts":{"200":16},"stream_errors_no_response":0},{"conc":32,"http_status_counts":{"200":32},"stream_errors_no_response":0},{"conc":64,"http_status_counts":{"200":64},"stream_errors_no_response":0},{"conc":128,"http_status_counts":{"200":128},"stream_errors_no_response":0},{"conc":96,"http_status_counts":{"200":96},"stream_errors_no_response":0},{"conc":80,"http_status_counts":{"200":80},"stream_errors_no_response":0},{"conc":72,"http_status_counts":{"200":72},"stream_errors_no_response":0},{"conc":68,"http_status_counts":{"200":68},"stream_errors_no_response":0},{"conc":66,"http_status_counts":{"200":66},"stream_errors_no_response":0},{"conc":65,"http_status_counts":{"200":65},"stream_errors_no_response":0},{"conc":65,"http_status_counts":{"200":65},"stream_errors_no_response":0},{"conc":65,"http_status_counts":{"200":65},"stream_errors_no_response":0}],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:cohere:anthropic","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"cohere","upstream_protocol":"anthropic","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:gemini:anthropic","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"gemini","upstream_protocol":"anthropic","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:bedrock:anthropic","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"bedrock","upstream_protocol":"anthropic","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:anthropic:openai-responses","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"anthropic","upstream_protocol":"openai-responses","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:gemini:openai-responses","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"gemini","upstream_protocol":"openai-responses","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai:openai-responses","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai","upstream_protocol":"openai-responses","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai-responses:openai-responses","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"served","raw_state":true,"reason":null,"detail":null,"evidence_scope":"Recorded run evidence","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai-responses","upstream_protocol":"openai-responses","upstream_transport":"http","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","memory_concurrency":null,"memory_load_s":301,"cost_concurrency":8,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{"added_latency_p50_us":{"value":194984,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"added_latency_p99_us":{"value":198964,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"gateway_c1_p99_us":{"value":198991,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"direct_c1_p99_us":{"value":27,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"cpu_us_per_request":{"value":177760,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"rps_per_cpu_second":{"value":5.625562556255626,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_conc":{"value":8,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_core_utilisation":{"value":0.8678710026382068,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_ok":{"value":125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_rps":{"value":20,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_threads":{"value":68,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_nonvol_ctxt_per_request":{"value":4.712,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_majflt":{"value":0,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"added_ttft_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_ttft_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"streams_sustained_fps":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"streams_sustained":{"value":null,"certified":false,"suppressed":false,"reason":"untestable","detail":"the mock does not answer openai-responses with a native event stream, so the rig cannot pose the streaming question here","state":"untestable","section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"idle_rss_mib":{"value":611.9609375,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"steady_state_rss_mib":{"value":1019.71484375,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"recovered_rss_mib":{"value":1019.88671875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_mib":{"value":1019.96875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_hwm_mib":{"value":1019.88671875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"time_to_plateau_s":{"value":66,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"growth_rate_mib_per_min":{"value":-0.19858581951462687,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"load_s":{"value":301,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_static":{"value":1,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_growth_rate_mib_per_min":{"value":0.04586307382763456,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."}},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false,"state":"valid","reason":null},"concurrency":16,"p99_us":1695035,"first_disqualified_conc":512,"lower_bound":false,"samples":127}],"sample_counts":{"gateway_c1_samples":30,"direct_c1_samples":268348},"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:cohere:openai-responses","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"cohere","upstream_protocol":"openai-responses","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:bedrock:openai-responses","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"bedrock","upstream_protocol":"openai-responses","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:cohere:gemini","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"cohere","upstream_protocol":"gemini","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai:gemini","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai","upstream_protocol":"gemini","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai-responses:gemini","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai-responses","upstream_protocol":"gemini","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:anthropic:gemini","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"anthropic","upstream_protocol":"gemini","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:gemini:gemini","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"gemini","upstream_protocol":"gemini","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:bedrock:gemini","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"bedrock","upstream_protocol":"gemini","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai-responses:cohere","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai-responses","upstream_protocol":"cohere","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:cohere:cohere","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"cohere","upstream_protocol":"cohere","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai:cohere","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai","upstream_protocol":"cohere","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:gemini:cohere","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"gemini","upstream_protocol":"cohere","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:anthropic:cohere","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"anthropic","upstream_protocol":"cohere","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:bedrock:cohere","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"bedrock","upstream_protocol":"cohere","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai:openai","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"served","raw_state":true,"reason":null,"detail":null,"evidence_scope":"Recorded run evidence","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai","upstream_protocol":"openai","upstream_transport":"http","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","memory_concurrency":null,"memory_load_s":305,"cost_concurrency":8,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{"added_latency_p50_us":{"value":198988,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"added_latency_p99_us":{"value":205966,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"gateway_c1_p99_us":{"value":205993,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"direct_c1_p99_us":{"value":27,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"cpu_us_per_request":{"value":182230.76923076922,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"rps_per_cpu_second":{"value":5.487547488391726,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_conc":{"value":8,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_core_utilisation":{"value":0.9645138811621244,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_ok":{"value":130,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_rps":{"value":21,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_threads":{"value":68,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_nonvol_ctxt_per_request":{"value":6.276923076923077,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_majflt":{"value":0,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"added_ttft_p50_us":{"value":158773,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_ttft_p99_us":{"value":170494,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p50_us":{"value":1,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p99_us":{"value":38,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"streams_sustained_fps":{"value":669.7194949393278,"certified":true,"suppressed":false,"headroom":0.4546587088488971,"rig_ceiling":1473.015873015873,"state":"valid","reason":null,"section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"streams_sustained":{"value":29,"certified":true,"suppressed":false,"headroom":0.4546587088488971,"rig_ceiling":1473.015873015873,"state":"valid","reason":null,"section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"idle_rss_mib":{"value":617.203125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"steady_state_rss_mib":{"value":971.84765625,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"recovered_rss_mib":{"value":972.3203125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_mib":{"value":972.4453125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_hwm_mib":{"value":972.31640625,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"time_to_plateau_s":{"value":61,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"growth_rate_mib_per_min":{"value":0.12924042130805258,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"load_s":{"value":305,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_static":{"value":1,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_growth_rate_mib_per_min":{"value":0.052286481252150616,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."}},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":19,"certified":true,"suppressed":false,"state":"valid","reason":null},"concurrency":8,"p99_us":788018,"first_disqualified_conc":512,"lower_bound":false,"samples":118}],"sample_counts":{"gateway_c1_samples":30,"direct_c1_samples":266566,"ttft_gw_samples":100,"ttft_direct_samples":100,"gap_gw_samples":63,"gap_direct_samples":63},"stream_rung_diagnostics":[{"conc":1,"http_status_counts":{"200":1},"stream_errors_no_response":0},{"conc":2,"http_status_counts":{"200":2},"stream_errors_no_response":0},{"conc":4,"http_status_counts":{"200":4},"stream_errors_no_response":0},{"conc":8,"http_status_counts":{"200":8},"stream_errors_no_response":0},{"conc":16,"http_status_counts":{"200":16},"stream_errors_no_response":0},{"conc":32,"http_status_counts":{"200":32},"stream_errors_no_response":0},{"conc":24,"http_status_counts":{"200":24},"stream_errors_no_response":0},{"conc":28,"http_status_counts":{"200":28},"stream_errors_no_response":0},{"conc":30,"http_status_counts":{"200":30},"stream_errors_no_response":0},{"conc":29,"http_status_counts":{"200":29},"stream_errors_no_response":0},{"conc":29,"http_status_counts":{"200":29},"stream_errors_no_response":0},{"conc":29,"http_status_counts":{"200":29},"stream_errors_no_response":0}],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:openai-responses:openai","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"openai-responses","upstream_protocol":"openai","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:bedrock:openai","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"bedrock","upstream_protocol":"openai","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:anthropic:openai","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"served","raw_state":true,"reason":null,"detail":null,"evidence_scope":"Recorded run evidence","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"anthropic","upstream_protocol":"openai","upstream_transport":"http","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":"cold restart, 60s idle read at rest, then load at c=32 for 300s, then 60s with the load removed. `plateaued` is a verdict over the trailing 60s, taken at the END of the load: steady means drift under 1% and range under 2% of the mean. The verdict does not end the load - every cell is loaded for the full duration.","memory_concurrency":null,"memory_load_s":304,"cost_concurrency":8,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{"added_latency_p50_us":{"value":195998,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"added_latency_p99_us":{"value":198984,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"gateway_c1_p99_us":{"value":199012,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"direct_c1_p99_us":{"value":28,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole."},"cpu_us_per_request":{"value":178977.27272727274,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"rps_per_cpu_second":{"value":5.587301587301587,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_conc":{"value":8,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_core_utilisation":{"value":0.647250235848493,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_ok":{"value":88,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_window_rps":{"value":14,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_threads":{"value":84,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_nonvol_ctxt_per_request":{"value":5.840909090909091,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"cost_majflt":{"value":0,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"perf","definition":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else."},"added_ttft_p50_us":{"value":156909,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_ttft_p99_us":{"value":168479,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p50_us":{"value":null,"certified":false,"suppressed":false,"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21072us) came in under the mock's (21073us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing","state":"below_resolution","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"added_gap_p99_us":{"value":null,"certified":false,"suppressed":false,"reason":"below_resolution","detail":"the gateway's own inter-frame gap at this percentile (21139us) came in under the mock's (21149us), which a proxy cannot really do - the added gap here is below what this rig can resolve against the mock's 20ms pacing","state":"below_resolution","section":"stream","definition":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added."},"streams_sustained_fps":{"value":787.6218019669257,"certified":true,"suppressed":false,"headroom":0.329921366515401,"rig_ceiling":2387.3015873015875,"state":"valid","reason":null,"section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"streams_sustained":{"value":47,"certified":true,"suppressed":false,"headroom":0.329921366515401,"rig_ceiling":2387.3015873015875,"state":"valid","reason":null,"section":"stream","definition":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"idle_rss_mib":{"value":605.86328125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"steady_state_rss_mib":{"value":961.5234375,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"recovered_rss_mib":{"value":961.328125,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_mib":{"value":961.90625,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"peak_rss_hwm_mib":{"value":961.73046875,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"time_to_plateau_s":{"value":61,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"growth_rate_mib_per_min":{"value":0.20581317972839427,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"load_s":{"value":304,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_shape":{"value":null,"certified":false,"suppressed":false,"reason":"not_measured","detail":"a settled idle window has no unsettled shape to describe","state":"not_measured","section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_static":{"value":1,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."},"idle_growth_rate_mib_per_min":{"value":0.17242880842301658,"certified":true,"suppressed":false,"state":"valid","reason":null,"section":"memory","definition":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran."}},"frontier":[{"bound_ms":1,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 1ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":5,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 5ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":10,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 10ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":50,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 50ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":100,"rps":{"value":null,"certified":false,"suppressed":false,"reason":"bound_not_met","detail":"every cleanly-served rung that reported a tail had it at or above 100ms, so this gateway carried no measurable throughput under that bound","state":"bound_not_met"},"concurrency":null,"p99_us":null,"first_disqualified_conc":null,"lower_bound":false},{"bound_ms":null,"rps":{"value":21,"certified":true,"suppressed":false,"state":"valid","reason":null},"concurrency":8,"p99_us":1051244,"first_disqualified_conc":256,"lower_bound":false,"samples":128}],"sample_counts":{"gateway_c1_samples":30,"direct_c1_samples":261879,"ttft_gw_samples":100,"ttft_direct_samples":100,"gap_gw_samples":63,"gap_direct_samples":63},"stream_rung_diagnostics":[{"conc":1,"http_status_counts":{"200":1},"stream_errors_no_response":0},{"conc":2,"http_status_counts":{"200":2},"stream_errors_no_response":0},{"conc":4,"http_status_counts":{"200":4},"stream_errors_no_response":0},{"conc":8,"http_status_counts":{"200":8},"stream_errors_no_response":0},{"conc":16,"http_status_counts":{"200":16},"stream_errors_no_response":0},{"conc":32,"http_status_counts":{"200":32},"stream_errors_no_response":0},{"conc":64,"http_status_counts":{"200":64},"stream_errors_no_response":0},{"conc":48,"http_status_counts":{"200":48},"stream_errors_no_response":0},{"conc":40,"http_status_counts":{"200":40},"stream_errors_no_response":0},{"conc":44,"http_status_counts":{"200":44},"stream_errors_no_response":0},{"conc":46,"http_status_counts":{"200":46},"stream_errors_no_response":0},{"conc":47,"http_status_counts":{"200":47},"stream_errors_no_response":0},{"conc":47,"http_status_counts":{"200":47},"stream_errors_no_response":0},{"conc":47,"http_status_counts":{"200":47},"stream_errors_no_response":0}],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:cohere:openai","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"cohere","upstream_protocol":"openai","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"},{"schema_version":"1.0","measurement_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e:gemini:openai","gateway_id":"plano","gateway_build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","run_id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","measured_at":"2026-11-10T17:40:07Z","status":{"state":"not_declared","raw_state":"not_configurable","reason":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","detail":"Pinned 0.4.39 source b13ddd632bde1fea7678386c345665ea5fa671af: hermesllm/src/clients/endpoints.rs accepts Chat, Responses and Messages ingress, with no Gemini, Cohere or Bedrock client API. providers/id.rs::compatible_api_for_client selects native Responses only for Responses ingress to OpenAI, Chat for Messages-to-OpenAI, native Messages for Messages-to-Anthropic, and Converse for all three ingress APIs to amazon_bedrock. Anthropic Chat/Responses ingress and Gemini provider use OpenAI-compatible upstream wire; they are not native Anthropic/Gemini translations. The normal provider mapping is retained rather than substituting a different provider for the OpenAI column. Seven supported pairs are enabled, including the documented Bedrock upstream.","evidence_scope":"Historical capability research, not a fresh probe of the tested build. Referenced versions may differ from gateway_build; do not infer current capability.","probe_http_status":null,"response_excerpt":null},"test":{"ingress_protocol":"gemini","upstream_protocol":"openai","hardware":"AWS m7g.4xlarge (Graviton3, 16 cores / 64 GB). Gateway-under-test pinned to 4 cores (the comparable basis); mock and load generator on 6 cores each so the mock never bottlenecks the streaming sweep. Ubuntu 24.04. One dedicated box per gateway.","architecture":"arm64","harness_commit":"d240badd966933fa19eec0606b2d1f3945f18ad2","harness_dirty":false,"mock_sha256":"99d01f709d8d9c1f49055aa265d5eb7475264d6b513911fe317aee74a71190f8","load_generator_sha256":null,"qualification":{"band_pct":20,"baseline_rps":96199,"baseline_samples":1,"concurrency":32,"drift_pct":4.480296052973523,"observed_absent_detail":null,"observed_absent_reason":null,"observed_rps":100509,"outcome":"pass"},"definitions":{"memory":"See `matrix.memory.protocol` and each cell's `memory.protocol`, which state the durations and both plateau thresholds formatted from the constants that ran.","perf.added_latency":"WHAT THE GATEWAY ADDS, at concurrency 1. The gateway leg's percentile minus the same request taken straight to the mock, one at a time, both legs in the same window. No search and no threshold: there is nothing to stop early and nothing to decide. A difference at or below what the rig can resolve publishes `below_resolution` - the best result the comparison can express - and every surface renders that apart from a never-measured hole.","perf.cost":"WHAT A REQUEST COST, in microseconds of gateway CPU. User plus system time, summed across the gateway's whole PROCESS TREE (a gateway that forks workers keeps its CPU in the children, and a parent-only reading would report a busy gateway as idle), sampled as the DIFFERENCE across one load window and divided by the requests that window actually completed. WHY IT EXISTS BESIDE THROUGHPUT. Peak rps is a SATURATION number: once a gateway fills the cores it is pinned to, the ladder stops describing the gateway and starts describing the box, and two gateways at that wall read the same however different they are. Cost per request has no such ceiling - at saturation both serve the same rate by definition, and the one doing less work per request still reads lower. It is also the figure that maps to money, since half the CPU serves the same traffic on half the instance. MEASURED AT ONE CONCURRENCY, c=8, HELD IDENTICAL FOR EVERY GATEWAY and published as `cost_window_conc`. No single concurrency is below saturation for a field spanning double-digit to five-figure rps, so matched LOAD is impossible and matched CONCURRENCY is the honest substitute - and it is stated rather than assumed. REFUSED, NOT ESTIMATED, IN TWO CASES. A window with ANY failure publishes no cost at all: CPU spent refusing requests is real, but dividing it by only the successes would describe the failures rather than the work. And a window with major page faults means the box was SWAPPING, so what was timed is the disk - those numbers publish with `cost_majflt` non-zero and the cost itself marked a harness fault, so a reader sees why the row looks wrong instead of finding a hole. `cost_core_utilisation` is the fraction of the PINNED cores busy across that same window. It is what makes a peak interpretable: near 1.0 the gateway had filled the cores it was given and its throughput number is a real ceiling; well below it, the limit is somewhere else and the peak means something else.","perf.frontier":"THROUGHPUT AT A TAIL LATENCY YOU ACCEPT. For each declared bound, the most requests/sec this cell carried while 99% of requests finished under that bound AND it failed none it accepted. Bounds: 1ms, 5ms, 10ms, 50ms, 100ms plus one reading with no latency bound at all (failures only). ONE MEASUREMENT, READ SIX WAYS: a single concurrency sweep, published as `sweep_max_proxy`, so every reading is re-derivable from the rungs rather than taken on trust. Monotone non-decreasing across the bounds BY CONSTRUCTION - relaxing a bound only adds rungs to the set a maximum is taken over - so a reading cannot exceed a looser one. ZERO FAILURES, not a tolerance: the load generator counts connections the RIG could not open separately (`rig_refused`, and those windows are discarded), so a failure reaching a reading is the gateway losing a request it had accepted. TERMINATION: the sweep climbs a doubling ladder from the floor and stops at the first concurrency where no window served cleanly, because more concurrency cannot un-fail those requests. Each reading names `first_disqualified_conc`, the lowest concurrency above it that stopped qualifying - that pair is the proof it is a boundary. When nothing above it disqualified, the sweep ran out of range instead of finding a limit, and the reading sets `lower_bound: true`: the rate is real, it is simply a floor rather than a ceiling. A window in which the gateway completed no request at all is a failed rung like any other. Only a RIG stop (a thread or connection this host could not make, or a load generator with no readable result) interrupts the sweep; its frontier is then read from the rungs below the stop, every reading sets `lower_bound: true`, and the absences name the rung and the cause. A bound no rung met publishes `bound_not_met`. The `p99_us` on a reading is the tail the winning rung ACTUALLY produced, never the bound - 4ms under a 100ms bound is not the same finding as 99ms - and `samples` is the number of completed requests it was taken over.","stream.added_ttft_and_gap":"WHAT THE GATEWAY ADDS TO A STREAM, at concurrency 1: time to the first event, and the gaps between frames inside one stream, each as the gateway leg minus the same stream taken straight to the mock. Time-to-first-EVENT rather than first token, deliberately and by the same definition on both legs: a frame budget of one is satisfied by a dialect's opening scaffolding (openai sends a role delta, anthropic a `message_start`), so the quantity is the same on both sides and the difference still isolates what the gateway added.","stream.streams_sustained":"THE MOST CONCURRENT SSE STREAMS THIS CELL CARRIES CLEANLY, and the frames/sec at that point. A concurrency holds the gate when every expected content frame arrives (ratio 1.0, i.e. no tolerance - a proxy that drops a frame has dropped a user's token), no inter-frame gap exceeds 10x the mock's own pacing interval, and under 0.1% of streams error. TERMINATION: the gate is monotone in concurrency, so the ceiling is a boundary found by bisection - a pass proven at n and a failure measured above it. `sweep_streams` carries every rung probed. A range whose top still passed publishes an absence rather than a ceiling, because the top of the range is our choice and not the gateway's answer."},"sweep_duration_s":null,"sweep_ttft_ms":null,"memory_protocol":null,"memory_concurrency":null,"memory_load_s":null,"cost_concurrency":null,"somaxconn":65535,"tcp_max_syn_backlog":65535},"metrics":{},"frontier":[],"provenance":{"source_url":"https://onthebench.ai/gateways/plano","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json","run_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","methodology_url":"https://onthebench.ai/gateways/method","raw_sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e"},"disclosure":{"operator":"Busbar team","operator_is_entrant":true},"published_at":"2026-11-14T11:09:23.855Z","generated_at":"2026-11-14T11:09:24.858Z","age_days":3,"age_as_of":"2026-11-14T11:09:24.858Z","age":"3 days old at collection generation"}],"history":[{"id":"run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","sha256":"0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","gateway_id":"plano","measured_at":"2026-11-10T17:40:07Z","build":"katanemo/plano:0.4.39@sha256:35a84cb873ee5f16cded33eeda72736f90798962b7489d58650c0db7b546e9ac","gateway_family":"plano","engine":"d240badd966933fa19eec0606b2d1f3945f18ad2","projector":"historical-matrix-v1-e1440c114a2bba3bde4a01bfa138bc6160e327576b1d93bd2dced418d56805ae","configuration_sha256":"ea8a13dfcb85d79f00d23dbb3558bce4ecbc378eb8a403f78fcfe5d943b83413","disposition":"recorded","evidence_available":true,"available_metrics":["added_gap_p50_us","added_gap_p99_us","added_latency_p50_us","added_latency_p99_us","added_ttft_p50_us","added_ttft_p99_us","cost_core_utilisation","cost_majflt","cost_nonvol_ctxt_per_request","cost_threads","cost_window_conc","cost_window_ok","cost_window_rps","cpu_us_per_request","direct_c1_p99_us","gateway_c1_p99_us","growth_rate_mib_per_min","idle_growth_rate_mib_per_min","idle_rss_mib","idle_shape","idle_static","load_s","peak_rss_hwm_mib","peak_rss_mib","recovered_rss_mib","rps_per_cpu_second","shape","steady_state_rss_mib","streams_sustained","streams_sustained_fps","time_to_plateau_s"],"measurements_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/measurements","source_url":"https://onthebench.ai/gateways/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-0a4ce97da36f11e7c407eef9280f69688b7ea1f007616709f0b914993cb8ba8e/raw.json"},{"id":"run-plano-5f9e8f61383353dae54dc52a3eece8e1db6e6b024d94a55a3687a3d96386130e","sha256":"5f9e8f61383353dae54dc52a3eece8e1db6e6b024d94a55a3687a3d96386130e","gateway_id":"plano","measured_at":"2026-08-26T19:08:45Z","build":"katanemo/plano:0.4.36","gateway_family":"plano","engine":"f3adbb1315b26129f5e317af5279decefb1cea8f","projector":"historical-matrix-v1-e1440c114a2bba3bde4a01bfa138bc6160e327576b1d93bd2dced418d56805ae","configuration_sha256":"52825b1f6024a3749ebee4767099cacd9b2e16bf66b33828036cd5f986b6fe92","disposition":"recorded","evidence_available":true,"available_metrics":["added_gap_p50_us","added_gap_p99_us","added_latency_p50_us","added_latency_p99_us","added_ttft_p50_us","added_ttft_p99_us","cost_core_utilisation","cost_majflt","cost_nonvol_ctxt_per_request","cost_threads","cost_window_conc","cost_window_ok","cost_window_rps","cpu_us_per_request","direct_c1_p99_us","gateway_c1_p99_us","growth_rate_mib_per_min","idle_growth_rate_mib_per_min","idle_rss_mib","idle_shape","idle_static","load_s","peak_rss_hwm_mib","peak_rss_mib","recovered_rss_mib","rps_per_cpu_second","shape","steady_state_rss_mib","streams_sustained","streams_sustained_fps","time_to_plateau_s"],"measurements_url":"https://onthebench.ai/api/v1/runs/run-plano-5f9e8f61383353dae54dc52a3eece8e1db6e6b024d94a55a3687a3d96386130e/measurements","source_url":"https://onthebench.ai/gateways/runs/run-plano-5f9e8f61383353dae54dc52a3eece8e1db6e6b024d94a55a3687a3d96386130e","raw_result_url":"https://onthebench.ai/api/v1/runs/run-plano-5f9e8f61383353dae54dc52a3eece8e1db6e6b024d94a55a3687a3d96386130e/raw.json"}],"generated_at":"2026-11-14T11:09:24.858Z","disclosure":{"operator":"Busbar team","operator_is_entrant":true}}
