Skip to content
Discussion options

You must be logged in to vote

Fixed in #10550 (tracked in #10543, released in 26.11.1).

What was wrong: when an INT8 or BINARY vector index was larger than the build cache, the graph build kept re-reading vectors from the index pages and converting them to new float arrays. At this scale that kept the heap almost full and the build slowed to a crawl.

What changed: the build now keeps the compact quantized vectors in memory (4x smaller for INT8) and converts them only when needed, without allocating. A build that fits the float cache works as before.

Measured: 1M x 768, 6 GB heap, default settings: 444 s (751 full GCs) -> 196 s (0 full GCs). With a tight heap the difference is larger.

For your setup: the build log now …

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@warframesam
Comment options

Answer selected by warframesam
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants