Questions about model options #52
-
|
Hey, I love
[EDIT] I just updated to v0.4.5 and re-indexed (wasn't sure if I needed to), and see that my index is using |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
|
Great question. I've refined the model selection stuff a bit. Default is going to be bge mainly because Jina and Nomic are still very heavyweight for local usage even on a relatively beefy machine (I have an M2 Max w/ 64gb of ram, and my laptop starts to take off when indexing a moderate sized codebase on Nomic) but I assume we'll get there. 0.4.5 had a bug reporting the incorrect model - this has now been fixed, and some nice affordances for switching between models and some safeguards to handle various edge cases when doing so. I think for now bge will remain the most sensible embedding option, but I'm thinking being able to plug in your own choice of remote backend embedding might have to be the way forward (e.g. point at your own openai ada or cohere or hugging face served model), at least until we get a decent tiny embedder that has good code and language coverage. |
Beta Was this translation helpful? Give feedback.
-
|
Specifically answering your questions: |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, @runonthespot! Can I ask what you personally use, and what you would recommend for something like a 64GB M1 Max system? (The large-ish project I'm using it with is a TypeScript-centric monorepo with a good amount of internal documentation on data models, coding and style standards, architecture decision records, etc.) |
Beta Was this translation helpful? Give feedback.
Great question. I've refined the model selection stuff a bit. Default is going to be bge mainly because Jina and Nomic are still very heavyweight for local usage even on a relatively beefy machine (I have an M2 Max w/ 64gb of ram, and my laptop starts to take off when indexing a moderate sized codebase on Nomic) but I assume we'll get there.
0.4.5 had a bug reporting the incorrect model - this has now been fixed, and some nice affordances for switching between models and some safeguards to handle various edge cases when doing so.
I think for now bge will remain the most sensible embedding option, but I'm thinking being able to plug in your own choice of remote backend embedding might have…