There are obviously MANY variables here and only 1 specific benchmark.
Running local is hard because of the # of hardware and software variables that come into play.
For example all my speeds with vLLM TP would be doubled if I was running on PCIe 5.0 except maybe the concurrency parallelism. My board is 4.0, but the usage of risers to make the cards fit at all has me dropping down to PCIe 3.0 due to signal degradation. For pipeline parallelism, this has very little impact, but it's brutal on the TP.
I would also see a jump in perf if I was using a higher memory fraction. I need space on my display GPU for now. Eventually, i'd like to build a dedicated AI server, then I can run these closer to something like 0.95 gpu mem.
I also am not certain what is causing the 5 task delta between my DSV4F T2.1 score and official scores. I've seen it validated by 3rd parties to be 61.8% vs my 56% finding. Potentially it's the DSV4F vLLM implementation, maybe MTP=2, or maybe my harness? who knows.
This is why you always need to actually test based on YOUR hardware and YOUR software to know for sure. This also makes me highly suspicious of any cloud API provider. Many share their precision, but you have NO clue whats the KV cache? What's MPT/speculative decoding? Every variable matters and I suspect there's likely a decent amount of variance in bench perf from each provider on openrouter. Someone should probably look into that :)
it's too easy to see a model, see tok/sec, and go with that provider. Waaaaaaay more questions you should be asking!