Latency must be brutal here. This will not be possible for any chat application, I guess.
It depends on how you do retrieval. If you just use dense embeddings for example you can get the latency of one search query down to maybe something like 400ms. In that case multiple sequential look ups would be ok but your embeddings need to be good enough of course
Evaluating modular RAG with reasoning models
11–20 of 32 posts
Re: Evaluating modular RAG with reasoning models
#12This comes at the cost of significantly higher latency and cost. But for us, answer quality is a much higher priority.
Re: Evaluating modular RAG with reasoning models
#13If so, then I would suggest that you run it ahead of time and generate possible questions from the LLM based on the context of the current semantically split chunk.
That way you only need to compare the embeddings at query time and it will already be pre-sorted and ranked.
The trick, of course, is chunking it correctly and generating the right questions. But in both cases I would look to the LLM to do that.
Happy to recommend some tips on semantically splitting documents using the LLM with really low token usage if you're interested.
Re: Evaluating modular RAG with reasoning models
#14We tried something similar and found much better results with o1 pro than o3 mini. RAG seems to require a level of world knowledge that the mini models don’t have. This comes at the cost of significantly higher latency and cost. But for us, answer quality is a much higher priority.
Re: Evaluating modular RAG with reasoning models
#15Is RAG any good for coding tasks?
Re: Evaluating modular RAG with reasoning models
#16Am I correct in reading that the RAG pipeline runs in realtime in response to a user query? If so, then I would suggest that you run it ahead of time and generate possible questions from the LLM based on the context of the current semantically split chunk. That way you only need to compare the embeddings at query time and it will already be pre-sorted and ranked. The trick, of course, is chunking it correctly and gen…
Possible but very compute intensive. Imagine if you have hundreds of thousands of chunks...
Re: Evaluating modular RAG with reasoning models
#17Am I correct in reading that the RAG pipeline runs in realtime in response to a user query? If so, then I would suggest that you run it ahead of time and generate possible questions from the LLM based on the context of the current semantically split chunk. That way you only need to compare the embeddings at query time and it will already be pre-sorted and ranked. The trick, of course, is chunking it correctly and gen…
Go on please :)
Re: Evaluating modular RAG with reasoning models
#18Re: Evaluating modular RAG with reasoning models
#19I wonder whether this would benefit from a fine tuned llm module for that specific step, or even by providing a set of examples in the prompt of when to use what tool?
Re: Evaluating modular RAG with reasoning models
#20We tried something similar and found much better results with o1 pro than o3 mini. RAG seems to require a level of world knowledge that the mini models don’t have. This comes at the cost of significantly higher latency and cost. But for us, answer quality is a much higher priority.
Or, at least it seems to in the limited amount of testing I did in a weekend. I'm an embedded dev without any real AI experience or an actual use case for building a RAG at the moment.