Sanity Checks for DB

[shaleenji]

No description provided.

[shaleenji]

The following checks are done at startup. Startup fails if any one of these fails:

1. CPU compatibility
2. Data directory read/write permissions
3. minimum Disk space (Minimum 10GB required - settings:MINIMUM_REQUIRED_FS_BYTES)
4. Minimum memory required - Priority:

• current-process cgroup v2 (memory.max - memory.current)
• current-process cgroup v1 (memory.limit_in_bytes - memory.usage_in_bytes)
• Host memory (macOS: host_statistics64, Linux: /proc/meminfo MemAvailable)

5. number of open files limit - ulimit -f (settings::MINIMUM_OPEN_FILES)

Warnings on:

1. if CPU cores is less than settings::DEFAULT_MINIMUM_CPU_CORES

[github-actions]

VectorDB Benchmark - Ready To Run

CI Passed ([lint + unit tests] (https://github.com/endee-io/endee/actions/runs/24024476106)) - 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.