Skip to content

Add VectorSearchEngine backed by turbovec - #1448

Closed
edwinyyyu wants to merge 1 commit into
MemMachine:mainfrom
edwinyyyu:turbovec_engine
Closed

Add VectorSearchEngine backed by turbovec#1448
edwinyyyu wants to merge 1 commit into
MemMachine:mainfrom
edwinyyyu:turbovec_engine

Conversation

@edwinyyyu

@edwinyyyu edwinyyyu commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Purpose of the change

SQLiteVectorStore + turbovec is smaller and faster than SQLiteVecVectorStore backed by sqlite-vec. Both are linear full scan but turbovec has a much smaller scaling constant, probably because in RAM instead of on disk.

Description

Add a new VectorSearchEngine backed by turbovec.

Known limitation: Because it does not store vectors, functionality to return vectors raises NotImplementedError. This makes it compatible with EventMemory but not the semantic memory.

Type of change

[Please delete options that are not relevant.]

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (does not change functionality, e.g., code style improvements, linting)
  • Documentation update
  • Project Maintenance (updates to build scripts, CI, etc., that do not affect the main project)
  • Security (improves security without changing functionality)

How Has This Been Tested?

  • Unit Test
  • Integration Test
  • End-to-end Test
  • Test Script (please provide)
  • Manual verification (list step-by-step instructions)

Checklist

[Please delete options that are not relevant.]

  • I have signed the commit(s) within this pull request
  • My code follows the style guidelines of this project (See STYLE_GUIDE.md)
  • I have performed a self-review of my own code
  • I have commented my code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added unit tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

Maintainer Checklist

  • Confirmed all checks passed
  • Contributor has signed the commit(s)
  • Reviewed the code
  • Run, Tested, and Verified the change(s) work as expected

Signed-off-by: Edwin Yu <edwinyyyu@gmail.com>
@edwinyyyu

Copy link
Copy Markdown
Contributor Author

Ensure proper implementation considering
#1460

@edwinyyyu

Copy link
Copy Markdown
Contributor Author

Superseded by #1499, which is the same engine branched from #1460 so that save publishes through the shared atomic_index_write helper instead of writing straight to the final path. Closing this one so the engine never exists on a branch with the wrong publication protocol.

@edwinyyyu edwinyyyu closed this Aug 13, 2026
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