Journal series · 8 articles
Read the complete sequence or enter at the question most relevant to your architecture.
Database Performance in Context
16,384 records captured offline. 16,512 verified after delivery and reopening. Explore what protected local storage can do for an application that must keep working.
Database Performance in Context
Ownership, time, location and sustained heat in one answer: 10.8 ms for 8DB, 332.5 ms for tuned SurrealDB.
Database Performance in Context
At a 99% recall floor, 8DB reached 8,551 searches per second on real text embeddings. Higher search quality, faster builds and a broader native data model make it a stronger option for applications that need more than a similarity match.
Database Performance in Context
Historical analytical query results beside ClickHouse, DuckDB, StarRocks, Doris and PostgreSQL references, plus the broader opportunity of an omnimodal engine.
Database Performance in Context
218,000 lookups per second for 8DB. A best recorded 3,410 for Neo4j. Both on an M1 laptop. A separate one-hop test also put 8DB ahead, reaching 23,300 queries per second.
Database Performance in Context
Five million readings, ready to query in 2.56 seconds with 8DB versus 5.16 seconds with QuestDB. A recorded bulk-loading comparison on a 16GB M1 laptop, using different clients and buffered completion.
Database Performance in Context
Six million locations, recorded GIS-tool comparisons, competitor timeouts and the broader opportunity of an omnimodal spatial engine.
Database Performance in Context
recorded results on the same server, using different benchmark configurations. Inside the comparison and the 27.6M mixed-workload peak of 8DB, an omnimodal database.