test(stability): add query benchmarks + a concurrent read/write test

[qiansheng91]

No performance or concurrency coverage existed for the read path.

• Go benchmarks for QueryEntities / QueryTopo and the query executor.
• A 24-reader / 8-writer concurrent test over the memory store (race-checked).
• A non-blocking make bench smoke step in CI.

Verification: benchmarks run; the concurrent test passes under -race.

[Mr-Xzz]

Reviewed the benchmark smoke target and concurrent read/write test. The CI step is non-blocking and the new test exercises the in-memory store locking path without broadening runtime behavior. No blocking findings from my pass.

[qiansheng91]

Issue Evaluation

Category: enhancement | Status: Evaluated

Feasibility: feasible
Scope: query service benchmarks, memory store, CI pipeline
Compatibility: no breaking changes — additive test coverage

This addresses a real gap in performance and concurrency testing. Go benchmarks for QueryEntities/QueryTopo provide baseline metrics, and the 24-reader/8-writer concurrent test with race detection validates thread safety of the memory store. Adding a non-blocking make bench smoke step in CI ensures regressions are caught early without slowing down the pipeline.

Recommendation: Proceed with implementation. Consider:

• Setting baseline thresholds in benchmarks to detect performance regressions
• Documenting the concurrent test parameters (24r/8w) and their rationale
• Ensuring the bench step doesn't block CI on minor regressions initially (warn-only mode)

---

Automated evaluation by github-manager-bot