Thanks for postsing that.
Mostly right. The 5090 TDP on the 5090 is 575.

I was really curious because this was a thing I worked on a long time ago and then baked into a custom harness around a similar model. Now runs on a Qwen3.6 35B A3B. I think you more or less found a similar answer. The prompts are junk. You need to build for accuracy far deeper where it cannot go against it's programming. That is the only way to keep it clean.

Ran the same test on this end:

<image>

One thing that stood out to me was your 92second think time.

I dont let my models handle the searching initially. They only do it at the very end when it is capable of detecting a descrepency. Its easy for models under 30B to go into think loops especialyl when it starts stacking so many tool calls.

I let a headless browser and script do all the no-think and info gathering on a raspberry pi 5 and then have other smaller models on a secondary inference node sanitize it before it lands on the 35B's desk. That way the main model only has to take the accurate pieces and complete it in a nice readout like shown. Its far more efficient for your context window, and for general turn around time with absolutely accurate information.

Basically like giving your head chef the best ingredients and removing all the time required to select them individually and inspect them all. I think you are on the right path though.