Live data from Hacker News

Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks

github.com

21–24 of 24 posts

Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks

#21

Earlier quoted context omitted.

That's a great question. I'll start with a little context: most of the users of our existing hosted platform are no-code/low-code developers who choose us because we're the simplest solution for building what they want to build (primarily because we have end-to-end workflows like Chat built-in). The improved retrieval performance is a nice-to-have for this group, but usually not the primary reason they choose us. For…

Uh, isn’t there a huge venture backed startup that rhymes with spleen that contradicts this? Not saying you’re wrong but.. one of you is.

I think the difference is that they're building for end users, not developers.

Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks

#22

nice to know but when you say "challenging real-world tasks" any use cases? are you automating the end to end RAG pipeline?

That description is a little vague, so I need to improve that. The use cases we're focused on are ones with 1) dense unstructured text, like legal documents, financial reports, and academic papers; and 2) challenging queries that go beyond simple factoid question answering. Those kinds of use cases are where we see existing RAG systems struggle the most.

Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks

#23
Hi Zach, how do you think this architecture would perform for one longer document i.e. a novel of >50k words <100k? the queries would be about that one long document as opposed to multiple documents. any tips on how to approach my use case? thanks

Re: Show HN: SpRAG – Open-source RAG implementation for challenging real-world tasks

#24

Hi Zach, how do you think this architecture would perform for one longer document i.e. a novel of >50k words <100k? the queries would be about that one long document as opposed to multiple documents. any tips on how to approach my use case? thanks

That should work well with the default parameters, so you shouldn't have to do anything special.
Post reply on HN