Interpreting the TOON vs JSON Benchmark Results #195
jmfloreszazo
started this conversation in
Show and tell
Replies: 1 comment
-
|
Hey @jmfloreszazo, I appreciate the thourough analysis! Is there anything we can include in the TOON docs based on your analysis? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
TOON Format: Benchmark & Architecture — what I found when comparing TOON vs JSON (and why the 25% saving actually matters)
Full article: https://medium.com/@jmfloreszazo
Benchmark repo (.NET / C#): https://github.com/jmfloreszazo/dotnet_llm_toon_format_demo
After running real benchmarks with full invoice datasets and reasoning models like o1, I found that TOON doesn’t deliver the 30–60% savings often claimed — but it does deliver a consistent ~25% reduction in input tokens compared to compact JSON, without losing accuracy or increasing latency.
It’s not magic, but it’s real architecture: in MCP pipelines and multi-agent systems, that 25% compounds across thousands of tool-calls and becomes meaningful FinOps impact.
What do you think?
Thanks for your work!
Beta Was this translation helpful? Give feedback.
All reactions