renaming files for compatibility
sabrinaaquino
@@ -18,7 +18,7 @@ tags:
|
||||
---
|
||||
# How Lyzr Supercharged AI Agent Performance with Qdrant
|
||||
|
||||
|
||||
|
||||
|
||||
## Scaling Intelligent Agents: How Lyzr Supercharged Performance with Qdrant
|
||||
|
||||
@@ -30,7 +30,7 @@ This is how they rethought their stack and adopted Qdrant as the foundation for
|
||||
|
||||
## The Scaling Limits of Early Stack Choices
|
||||
|
||||
|
||||
|
||||
|
||||
Lyzr’s architecture used Weaviate, with additional benchmarking on Pinecone. Initially, this setup was fine for development and controlled testing. The system managed around 1,500 vector entries, with a small number of agents issuing moderate query loads in a steady pattern.
|
||||
|
||||
@@ -97,7 +97,7 @@ One deployment, built for NTT Data, focused on automating IT change request work
|
||||
|
||||
After migrating to Qdrant, the difference was immediate. Retrieval accuracy improved substantially, even for long-tail queries. The system maintained high responsiveness under concurrent loads, and horizontal scaling became simpler—ensuring consistent performance as project demands evolved.
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
@@ -107,7 +107,7 @@ Another example involved NPD, which deployed customer-facing agents across six w
|
||||
|
||||
Qdrant’s vector search enabled accurate, low-latency retrieval across thousands of entries. Even under increasing user traffic, the platform delivered consistent performance, eliminating the latency spikes experienced with previous solutions.
|
||||
|
||||
|
||||
|
||||
|
||||
## Final Thoughts
|
||||
|
||||
|
||||
|
Before Width: | Height: | Size: 1.1 MiB After Width: | Height: | Size: 1.1 MiB |
|
Before Width: | Height: | Size: 556 KiB After Width: | Height: | Size: 556 KiB |
|
Before Width: | Height: | Size: 226 KiB After Width: | Height: | Size: 226 KiB |
|
Before Width: | Height: | Size: 358 KiB After Width: | Height: | Size: 358 KiB |