mirror of
https://github.com/qdrant/qdrant.git
synced 2026-09-29 17:37:58 -05:00
`quantized_size_for` pads its `dim` argument, so passing the already padded `self.padded_dim` applied the x1.5 expansion of `Bits1_5` a second time. Nothing on disk depends on the value for that width: the quantization path sizes its records with `quantized_size_for` from the raw dim, and the Turbo datatype storages, which do use `quantized_size()` as their record size, are fixed at Bits4, where the padding is idempotent. The wrong value only over-reserved the `quantize` output buffer. Compute the packed size from `padded_dim` directly and cover `Bits1_5` in the byte-length test. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>