generic cpu compilation and fallback

[shaleenji]

Pull Request

Summary

This PR removes the need to be extremely rigid in the way compiation for different CPU capabilities is done. AVX2 AVX512 etc. A good way to do things is to be able to compile the code in a generic fashion and enable higher capabilities based on the CPU we are running on currently.

Type of Change

• New feature

[github-actions]

VectorDB Benchmark - Ready To Run

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