commit9

[omnish-endee]

No description provided.

[omnish-endee]

test karo ab

[github-actions]

VectorDB Benchmark - Ready To Run

CI Passed ([lint + unit tests] (https://github.com/omnish-endee/endee/actions/runs/24553462563)) - benchmark options unlocked.

Post one of the command below. Only members with write access can trigger runs.

---

Available Modes

Mode	Command	What runs
Dense	/correctness_benchmarking dense	HNSW insert throughput · query P50/P95/P99 · recall@10 · concurrent QPS
Hybrid	/correctness_benchmarking hybrid	Dense + sparse BM25 fusion · same suite + fusion latency overhead

---

Infrastructure

Server	Role	Instance
Endee Server	Endee VectorDB — code from this branch	t2.large
Benchmark Server	Benchmark runner	t3a.large

Both servers start on demand and are always terminated after the run — pass or fail.

---

How Correctness Benchmarking Works

1. Post /correctness_benchmarking <mode>
2. Endee Server Create  →  this branch's code deployed  →  Endee starts in chosen mode
3. Benchmark Server Create  →  benchmark suite transferred
4. Benchmark Server runs correctness benchmarking against Endee Server
5. Results posted back here  →  pass/fail + full metrics table
6. Both servers terminated   →  always, even on failure

After a new push, CI must pass again before this menu reappears.

[omnish-endee]

/correctness_benchmarking hybrid

[github-actions]

VectorDB Benchmark — Hybrid — Passed

Triggered by @omnish-endee · Commit dfb01b6

Step	Status
Provision Servers	Up
Deploy Endee Server	Done
Run Benchmark	Passed
Results	See below
Teardown	Done ✓

Benchmark Metrics — Hybrid

Method	P95 Upsert (ms)	P99 Upsert (ms)	Recall@10	NDCG@10	MAP@10
BM25	6000.974	6114.849	0.824	0.697	0.651
Endee BM25	5972.813	6077.419	0.820	0.695	0.649
SPLADE	15650.335	16071.429	0.834	0.703	0.655