正在加载视频...

视频加载失败

I can search a database with 32 million records in less than 50 milliseconds. ​ This speed is insane! ​ There's no reason your search is slow. There's no reason you aren't using this library when building applications with a lot of data. ​ Take a look at typesense...

160,154 次观看 • 2 年前 •via X (Twitter)

10 条评论

AkivaSk 的头像
AkivaSk2 年前

@typesense I guess Windows have never heard about them.

Santiago 的头像
Santiago2 年前

@typesense Apple hasn't either.

adrien 的头像
adrien2 年前

@typesense Thanks for sharing @svpino What if my data is long form content such as a lot of transcripts of 3 hours videos? Do you still recommend using this? Also your description said it’s vector search but your demo seems to be keyword search? Thanks.

Santiago 的头像
Santiago2 年前

@typesense It supports vector search.

Darko Medin 的头像
Darko Medin2 年前

@typesense Really impressive example @svpino. Speed is essential in many business applications today.

Marcin Wojnarski 的头像
Marcin Wojnarski2 年前

@typesense In-memory database, so its scalability and resilience is limited compared to ElasticSearch which can be distributed. Comparing apples to oranges. 32M records is nothing if you only search across several metadata fields without full-text content.

Muratcan Koylan 的头像
Muratcan Koylan2 年前

@typesense This seems like keyword search tho

Santiago 的头像
Santiago2 年前

@typesense The demo is a keyword search with tolerance for typos. Check their features:

Lionel Ngendakuriyo 的头像
Lionel Ngendakuriyo2 年前

@typesense What is the box specs ?

Santiago 的头像
Santiago2 年前

@typesense I didn't find the box specs for this specific example, but I did find specs for similar examples:

相关视频

99% of AI applications are cool-looking demos. Impressive, but don't get fooled by the hype. It takes a lot to build enterprise-grade products that deliver real value. I have at least three weekly conversations with companies that want to use a Large Language Model with their data. The demand is huge! Here is one idea about what you can do to help. The use cases that most of these companies want to solve are similar: They have an extensive knowledge base and want to build a simple application that uses that information to answer questions. In other words, they need help building Retrieval Augmented Generation (RAG) applications they can use in many different scenarios: 1. To train new employees 2. To help their support team 3. To search old meetings and documents 4. To help with their research However, building these systems is not straightforward. Yes, there's a lot of information online, but there aren't enough people who know how to create solutions that work. Here is the idea: Today, you can build an enterprise-grade RAG application without writing code. A couple of MIT PhDs with 10+ years of experience building AI applications created . It's a no-code platform for building applications using Large Language Models. They are partnering with me on this post. You can use Stack AI to create, test, and deploy an end-to-end production-ready AI system. It's SOC-2, HIPAA, and GDPR compliant and offers SSO, role management, access control, and on-premise deployments. Of course, you can use the platform with any LLM on the market now. It's the whole nine yards for building AI applications. Check them out here: 2023 was about models. 2024 is about the tools using these models to build production-ready applications. That's where I'd start.

Santiago

197,702 次观看 • 2 年前

Traditional data pipelines don't work for RAG applications. There are 3 issues with them: ​ 1. Traditional data engineering solutions are optimized to handle structured data. RAG applications rely primarily on unstructured data. ​ 2. The connector ecosystem to load data from unstructured data sources is very immature. ​ 3. Traditional solutions do not offer any way to transform unstructured data into an optimized vector search index. ​ The goal of a RAG Pipeline is to solve these problems. ​ The number one objective is to create a reliable vector search index using factual knowledge and relevant context. This sounds easy, but it's one of the biggest challenges we face when building RAG applications. ​ At a high level, there are four different stages in the architecture of a RAG pipeline: ​ 1. Ingestion: Here is where the pipeline loads the information from the data source. ​ 2. Extraction: Where the pipeline processes the input data and decides how to retrieve the text contained inside them. ​ 3. Transform: Where the pipeline chunks the data and generates document embeddings. ​ 4. Load: Where the pipeline creates a search index in a vector database and loads the document embeddings. ​ There are different rabbit holes at each one of these stages. Here are three of them: ​ 1. Ingesting data once is simple. The hard part is refreshing the vector database whenever the original data source changes. ​ 2. Extracting the content of a plain text document is simple. The hard part is to extract content from complex documents containing tables, images, or cross-references. ​ 3. A simple continual chunking strategy with an overlap is simple. The hard part is to find the optimal strategy for your specific knowledge base and the way you are planning to query it. ​ In the attached video, I'll show you how you can build an enterprise-grade RAG Pipeline that solves every one of the above problems. ​ I'll use Vectorize. They partnered with me on this post. You can use them to build RAG pipelines optimized for accurate context retrieval. ​ ​ If you have a few documents lying around, set up a free account and give it a try.

Santiago

40,625 次观看 • 1 年前