4 ms·
Very useful! I really don't like paying for unnecessary tokens. And works very fast for me. Do you have some standard practices to recommend with respect to the
by imitliagkas 7mo ago
Very useful! I really don't like paying for unnecessary tokens. And works very fast for me. Do you have some standard practices to recommend with respect to the optional hint in the call? It seems to help significantly.
- gskm 7mo agoThanks! Glad it's working well for you. A few practical tips: 1. Pass the user's query directly. In the benchmark, the hint is literally the question. That's the simplest and most effective approach for RAG. 2. Keep it concise (a sentence or two). Natural language works fine. 3. Skip it for summarization. When there's no specific query, omitting the hint lets the optimizer select for overall document coverage, which is probably what you want. 4. Biggest impact at lower budgets. The hint shines most when the optimizer has to be selective, e.g., at 50% budget on Qasper, hint adds nearly 6 F1 points (41.27 vs 35.35).