add concurrency explanation, update Zep (#766)

This commit is contained in:
Daniel Chalef 2025-07-24 11:36:06 -07:00 committed by GitHub
parent 21b63faec5
commit 9ceeb54186
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -54,9 +54,9 @@ nodes ("Kendra", "Adidas shoes"), and their relationship, or edge ("loves"). Kno
extensively for information retrieval. What makes Graphiti unique is its ability to autonomously build a knowledge graph
while handling changing relationships and maintaining historical context.
## Graphiti and Zep Memory
## Graphiti and Zep's Context Engineering Platform.
Graphiti powers the core of [Zep's memory layer](https://www.getzep.com) for AI Agents.
Graphiti powers the core of [Zep](https://www.getzep.com), a turn-key context engineering platform for AI Agents. Zep offers agent memory, Graph RAG for dynamic data, and context retrieval and assembly.
Using Graphiti, we've demonstrated Zep is
the [State of the Art in Agent Memory](https://blog.getzep.com/state-of-the-art-agent-memory/).
@ -167,6 +167,14 @@ pip install graphiti-core[anthropic,groq,google-genai]
pip install graphiti-core[falkordb,anthropic,google-genai]
```
## Default to Low Concurrency; LLM Provider 429 Rate Limit Errors
Graphiti's ingestion pipelines are designed for high concurrency. By default, concurrency is set low to avoid LLM Provider 429 Rate Limit Errors. If you find Graphiti slow, please increase concurrency as described below.
Concurrency controlled by the `SEMAPHORE_LIMIT` environment variable. By default, `SEMAPHORE_LIMIT` is set to `10` concurrent operations to help prevent `429` rate limit errors from your LLM provider. If you encounter such errors, try lowering this value.
If your LLM provider allows higher throughput, you can increase `SEMAPHORE_LIMIT` to boost episode ingestion performance.
## Quick Start
> [!IMPORTANT]