dimgigov
8db5cfe7e1
CI / test (push) Has been cancelled
CI / verify (push) Has been cancelled
Clients CI / build-server (push) Has been cancelled
Clients CI / test-python (push) Has been cancelled
Clients CI / test-javascript (push) Has been cancelled
Clients CI / test-nim (push) Has been cancelled
Clients CI / test-rust (push) Has been cancelled
Core storage: hash MemTable, WAL group commit, L0 compaction rebuild, reader-writer lock, and a global StorageGate so HTTP workers and TCP share the LSM safely under multi-thread access. Schema: durable CREATE/ALTER/DROP under _schema:tables:* with full LSM restore on open. Executor types/values/schema split into query/exec/. Wire protocol: switch default MM to ARC — ORC cycle collector segfaulted after ~20 async INSERTs. Fair multi-tier benchmarks (SQLite/HTTP/wire/PG) and honesty docs for mixed-tier comparisons.
824 B
824 B
Legacy mixed-tier comparison
This file used to claim large “speedups” of BaraDB over PostgreSQL by comparing:
- PostgreSQL: client-server (psycopg2, network, SQL)
- BaraDB: in-process LSM (no network, no SQL)
That is not a fair product comparison.
Use the fair suite instead
nim c -d:release -r benchmarks/bench_all.nim # embedded BaraDB
python3 benchmarks/fair_bench.py # SQLite + optional PG/HTTP
# report → benchmarks/FAIR_COMPARISON.md
See:
FAIR_COMPARISON.md— latest multi-tier resultsREADME.md— methodology and env vars
If you regenerate the legacy report
python3 benchmarks/generate_report.py # without --fair
It will rewrite this file with an explicit mixed tiers warning banner.