I'll keep it haha
1 karma · joined March 8, 2023
I'll keep it haha
Minutes, not days. Very big data sets might take 30+ minutes (or even a couple of hours), but usefulness starts in the first few minutes (because of the priority algorithm)
I'm testing this on a large knowledge base.
some rust code that compiles to WASM loads LLM from memory, and uses custom transformer.py like rust alternative we wrote.
Let the best product be remembered for the name.
But also have paid features that managers would like to use.
But yeah
And most first posts don’t get the intended traction for various reasons (too long, bad wording, unclear).
reposting and changing the post is totally allowed :)
Slack, teams, confluence or notion? airtable? jira?
hundred of millis is what I experienced.
Which under the hood is based of a t5 encoder
Haystack runs entirely client sided in the browser, so it has a unique tech-stack:
Storage
using IndexDB, haystack stores user indexes locally, + a compressed 90mb NLP model (t5-small) is stored.
Indexing
Locally in the browser, using a t5-small bi-encoder, and some parsing of documents happens in wasm.
Search
Query converted to embedding, then searched over index, atlast results are reranked with a t5-small based cross encoder, and top results go through a seq-to-seq transformer to produce a nice consise textual answer.
I would argue that every known noun are the first domains to get registered. My goal is to associate workplace search engines with haystack.
It's self-hostable, doesn't store your data, more focused on developers and bottom up motions, I want you to be up and running within 10 seconds.