Skip to content

Add Lucene benchmark backend core - #19

Draft
nvzm123 wants to merge 2 commits into
zackm_pylucene_runtime_integrationfrom
zackm_lucene_benchmark_backend
Draft

nvzm123 wants to merge 2 commits into
zackm_pylucene_runtime_integrationfrom
zackm_lucene_benchmark_backend

Conversation

@nvzm123

@nvzm123 nvzm123 commented Oct 6, 2026

Copy link
Copy Markdown
Owner

Note

Draft 3 of 5 in the Lucene backend split. It depends on the generic plugin
contract and PyLucene runtime layers below it.

Summary

  • add the directly importable Lucene cuVS Bench backend and configuration loader;
  • support Lucene CPU HNSW, cuVS-built HNSW, and cuVS CAGRA search;
  • record explicit build/search timing and provenance boundaries;
  • validate algorithm parameters, persisted codecs, vector fields, and CAGRA indexes;
  • keep fallible validation and diagnostics before rollback-safe index publication;
  • cover correctness, scoring, lifecycle, rollback, publication, and result metadata.

This layer deliberately does not register public package entry points yet, so
its behavior can be reviewed and unit-tested before package activation.

Validation

  • backend contract, build/search, lifecycle, result, and inherited runtime tests:
    152 passed;
  • Python compilation and git diff --check: passed.

@nvzm123
nvzm123 force-pushed the zackm_pylucene_runtime_integration branch from 2cf654f to 1f6460d Compare October 6, 2026 21:40
@nvzm123
nvzm123 force-pushed the zackm_lucene_benchmark_backend branch from 38bf707 to 4f7d192 Compare October 6, 2026 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant