Observed Signal · Aug 21, 2026 · Technical Report · Source: DEV Community · Impact: 2/5 · Sentiment: Neutral
Benchmark of Five Managed Graph Databases
A reproducible benchmark comparing CognoDB Cloud, Neo4j AuraDB, Memgraph, FalkorDB and ArangoDB revealed major pitfalls in naive measurement: geographic placement of managed instances skewed raw latency numbers, server-reported execution time (via Bolt drivers) is required for fair engine-to-engine comparison, and CognoDB v0.9.11 exhibited a background-indexing behaviour that caused indexed lookups to return no results while an index was building, silently dropping relationship writes. Concurrency characteristics differed: cloud-hosted databases scaled with client concurrency due to network latency hiding server idle time, while local instances became CPU-bound and slowed. The author published the full harness and raw data on GitHub.
Technical, reproducible benchmarking of graph databases reveals practical measurement pitfalls (network geography, server-reported timings) and a data-consistency/indexing bug in CognoDB; useful to engineers selecting or operating graph stores but not industry-shifting.
Track Neo4j Signals & Market Shifts in Real-Time
Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your Polaris7 workspace to monitor these entities.
Key Takeaways & Evidence Grounding
- Five graph databases were benchmarked: CognoDB Cloud, Neo4j AuraDB, Memgraph, FalkorDB and ArangoDB.
- Geographic placement of managed cloud instances (e.g., CognoDB in Google Cloud us-east4 and Neo4j AuraDB in Google's Singapore range) skewed raw wall-clock latency measurements.
- Using server-reported execution time via Bolt drivers (network excluded) was necessary to fairly compare engines in different regions.
- CognoDB v0.9.11 builds indexes in the background and, while an index is building, indexed lookups returned no results causing relationship writes to be silently dropped until the index finished.
- Concurrency tests showed cloud databases scaled throughput with more clients (latency-bound), while local databases became CPU-bound and degraded under higher concurrency.
Connected Companies & Entities
3 Entities mapped“The other managed database, Neo4j AuraDB, landed in Singapore, about 88 ms from me, which had me worried right away, because now my two clou...”
“The full harness, every number, and all the raw data are on GitHub: github.com/FANZ3R/graph-database-cloud-benchmark”
“CognoDB's free instance provisioned into Google Cloud's us-east4 region, which is Northern Virginia.”
Ontology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Benchmarking Five Graph Databases on 256MB RAM
The author benchmarked five graph databases (CognoDB, Neo4j AuraDB Free, Memgraph, FalkorDB, and ArangoDB) under a tight resource cap (0.5 vCPU / 256MB RAM) using a social-graph SNAP dataset (~18.7k nodes, ~198k edges). Results showed a range of operational and performance issues: Memgraph repeatedly segfaulted at startup across versions and configurations; FalkorDB lost all data after an environment restart due to an incorrect bind mount path and ignored persistence flags; Neo4j AuraDB exhibited a near-constant ~220ms per-query latency floor suggesting a fixed request cost; CognoDB was fastest on most queries but had one query pattern where it performed worst. Full methodology and raw results are available in the linked GitHub repository.
Benchmarking 7 Vector Databases: AionDB Stands Out
A developer tested seven vector/multi-model databases (Pinecone, Weaviate, Qdrant, Milvus, pgvector, SurrealDB and AionDB) over one week on a production-style RAG workload (2M chunks, ~500k entity relationships). The author reports SurrealDB exhibited poor performance and stability on graph-heavy queries, while AionDB — a relatively unknown solo‑founder project — delivered markedly better results: roughly 6x faster across general workloads and up to 200x faster on certain graph-heavy queries. AionDB also speaks the PostgreSQL wire protocol, allowing existing Postgres clients, ORMs and dashboards to work without migration. The article links to the AionDB GitHub repo and details practical tradeoffs observed during benchmarking.
Memory Graphs Don't Scale
A developer argues that using graph databases as long-term 'memory' for LLM-driven agents fails to scale in production because update costs cascade through dense relationship networks. The author recommends hierarchical, versioned storage that returns tightly scoped, deterministic context to models rather than fuzzy graph traversals. To demonstrate, they open-sourced Lithium — a small set of packages implementing hierarchical versioned storage on PostgreSQL ltree with scoped retrieval and Model Context Protocol (MCP) support — and published it on GitHub on May 27, 2026.
Receive all future signals for Neo4j & competitors in your briefing
Never miss material M&A deals, leadership changes, account wins, or product rollouts. Polaris7 monitors 20,000+ primary sources 24/7, delivering verified telemetry directly into your executive briefing.