I'm considering using LangChain, LlamaIndex, etc. but wondering what others' experiences have been with the various approaches. I have a custom corpus of documentation for which I want to create a question-answer chatbot.
Depends on the complexity of the requirements. I have built a couple:
- https://crimson-glade-1527.section.app/ : to talk to www.section.io docs. I used straight up python and Gradio. The chatbot doesn't have memory. Just use a CSV for embeddings. Has limited functionality but does it's job well. https://github.com/manibatra/sectiongpt - consider this toy code which was hacked together in a few hours.
- Also building https://www.everbility.com : Using Langchain, Pinecone. I often found Langchain to be a bit of an overkill with it's so many abstractions if your use case is just sending one off prompts. It is powerful though for document ingestion and Agents (which is something I plan to use it more for). When using Langchain you will often have to debug a bunch of edge cases which is understandable since
A random hack I found for improving the quality of answers by a big factor was creating embeddings for entire documents and also sections of document. Resulted in search on the vector space being very accurate for big picture and granular questions.
I have one question tho, in pinecone, can I make multiple indexes in 1 pod? I was thinking of making a Saas based app for it and give access to others, was just wondering how that worked.
You can only have one index in a pod but you can have multiple namespaces in an index and a vector search is constrained to one namespace at a time : https://docs.pinecone.io/docs/namespaces
- https://crimson-glade-1527.section.app/ : to talk to www.section.io docs. I used straight up python and Gradio. The chatbot doesn't have memory. Just use a CSV for embeddings. Has limited functionality but does it's job well. https://github.com/manibatra/sectiongpt - consider this toy code which was hacked together in a few hours.
- Also building https://www.everbility.com : Using Langchain, Pinecone. I often found Langchain to be a bit of an overkill with it's so many abstractions if your use case is just sending one off prompts. It is powerful though for document ingestion and Agents (which is something I plan to use it more for). When using Langchain you will often have to debug a bunch of edge cases which is understandable since
A random hack I found for improving the quality of answers by a big factor was creating embeddings for entire documents and also sections of document. Resulted in search on the vector space being very accurate for big picture and granular questions.