Remix.run Logo
bob1029 2 days ago

Simply starting in the right part of the search space is the biggest predictor of success.

The best way to save tokens is to start out the deep research pass with cheap models and then funnel the findings through increasingly powerful models. I've got a pipeline right now that uses all 3 of the gpt-5.6 model variants to address each stage of the process. If you are using models like sol or terra to generate hypotheticals and perform initial exploration, you are leaving money on the table.

5 hypotheticals out of luna will massively outperform 1 hypothetical out of sol, but the cost is the same and so is the runtime if you do it in parallel. The hypothesis generation phase is also a great place to mix and match models from different vendors. The more diversity at this step the better.

The other thing I started looking into is batch pricing which represents 50% off for OAI tokens right now. With some tweaks to the UI/UX of an enterprise chatbot, I think it is possible we could have users get comfortable with the idea that questions to the robot might take a day to come back. The key is that this has to actually work. Users don't mind trading time if their questions come back with high quality results.

xyzsparetimexyz 2 days ago | parent | next [-]

Couldn't someone build an adaptive system, where the llm is frequently judging the difficulty of a task and switching to a more/less powerful model?

iamflimflam1 2 days ago | parent | next [-]

This only works well if you are creating sub agents with clean contexts for each task. If you constantly are switching models part way through some work then the whole session needs to be replayed each switch. You lose all the benefits of the context cache.

xyzsparetimexyz 2 days ago | parent [-]

Well yeah, it'd require the models to be loaded on the same system and the cache to be shared between them somehow

inigyou 2 days ago | parent [-]

Cache sharing is not possible. The numbers in the cache are completely specific to the model.

xyzsparetimexyz 2 days ago | parent [-]

Currently. I'm sure that you could make a system where the cache values are a superset C of e.g. models A and B where C is probably bigger than max(A,B) but smaller than A+B

wonnage a day ago | parent | next [-]

Reddit post so take with a grain of salt but this does seem possible. But unclear whether this is actually a viable architecture https://www.reddit.com/r/LocalLLaMA/comments/1t8s83r/nvidia_...

inigyou 2 days ago | parent | prev [-]

It's equal to A+B. There is literally no sharing possible.

xyzsparetimexyz a day ago | parent [-]

Even when training both models together in a novel way?

bob1029 2 days ago | parent | prev | next [-]

The judgment of task difficulty is a cursed problem. In most domains you really don't know what is down there until you start digging a little bit.

xyzsparetimexyz 2 days ago | parent [-]

Well yeah. You start on as medium model, it does the digging says says 'this task is too easy/hard/just right for me' and go from there.

bkotrys 2 days ago | parent | prev | next [-]

definitely something that will come sooner than later. In my view, adaption of model routing / model orchestration and mixing providers is just natural next step.

zombot a day ago | parent | prev | next [-]

And while you're at it, solve the halting problem.

2 days ago | parent | prev [-]
[deleted]
jscottbee 2 days ago | parent | prev | next [-]

Yeah, I do this as well. Some of the last large tools I built have been started with Gemini (I get it with my Google package), and even one with Copilot.

zombot a day ago | parent | prev | next [-]

So did you find out how to save tokens yet, or are you still spending tokens on the search for the answer?

2 days ago | parent | prev [-]
[deleted]