MattJackson opened a new issue, #13740:
URL: https://github.com/apache/apisix/issues/13740

   Hi, I run [onthebench.ai](https://onthebench.ai), an open benchmark that 
measures LLM-gateway overhead (latency, throughput, memory, streaming, protocol 
translation) on neutral hardware. **APISIX** is one of the gateways on the 
board, and I want to make sure I'm testing it fairly.
   
   How it works, so there are no surprises:
   - Every gateway runs on the **same rig, same mock upstream, same load, same 
CPU pinning**, no per-gateway special-casing.
   - Each gateway is defined by a single file, 
[`gateways/apisix/gateway.sh`](https://github.com/GetBusbar/benchmarking/blob/main/gateways/apisix/gateway.sh),
 which declares how to build, launch, and probe it. That file is the whole 
story of how I configured yours.
   - Every number regenerates from committed JSON; the [method is documented 
here](https://onthebench.ai/gateways/method) and the whole thing is open source 
and re-runnable.
   
   My guiding rule is that **a failure is my bug until proven the gateway's**. 
If a cell shows red or a number looks off, I'd rather find out I configured 
**APISIX** wrong than publish something unfair. So two asks, both optional:
   1. **Look at your results** ([your 
page](https://onthebench.ai/gateways?gw=apisix)) and your `gateway.sh`. If I've 
mis-set a flag, a version, an endpoint, or declared a capability you don't 
claim, tell me or open a PR, you're welcome to own your own `gateway.sh`.
   2. If the setup looks fair, a thumbs-up is genuinely useful too.
   
   Full disclosure: this is built and operated by the Busbar team, and busbar 
is also one of the entrants. Same harness for everyone, fully open, so you can 
verify exactly what I'm running.
   
   Thanks for building **APISIX**.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to