Repository navigation
Stream embedding exports and accelerate lossless XOR packing - #10
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Embedding export previously materialized a whole-table CPU copy and Python bytes object, while native XOR prediction looped over every byte in Python. Stage weights in bounded row slices with incremental SHA-256, and compute each block's identical XOR residual through C-backed Python integer operations. Format, source IDs/dtype, compression candidates and C queries are unchanged.
Validation:
Exact baseline/code commits, commands, source/library/data/artifact hashes, all timing samples and limitations are retained in
docs/export_evidence_20261021/and summarized indocs/streaming_export_20261021.md. No new data download or retraining. CPU only; no trained Engram, GPU, task-quality or query-speed claim.