Closed tm-kn closed 6 months ago
I don't remember anymore. My bad. This is probably something to do with what @mgax was raising feedback for.
It was about adding a database index to make embedding search faster. It turns out this isn't trivial because the database column doesn't specify a size for the embeddings vector (or something along those lines).
For a bit of context, we were seeing slow (3-4 seconds) search times on Heroku, but it turned out we were fetching all the embeddings into Python and doing the search there. Moving the search in the database reduced query time to ~500ms for ~1300 records (with no index, just doing a table scan) which was good enough.
Ah thank you @mgax - the word 'index' serving double purposes here doesn't do us any favours.
I've written up this issue separately at #49 so we can keep this one closed
Just checking what you mean by this issue @tm-kn ?