# No Observable Difference Between BBQ and Default Configurations in Elasticsearch – Help with Index Size Comparison **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-machine-learning, vector-search\ **Created:** [May 5, 2025, 2:04pm UTC](https://discuss.elastic.co/t/no-observable-difference-between-bbq-and-default-configurations-in-elasticsearch-help-with-index-size-comparison/377817 "2025-05-05T14:04:59Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![yli](https://avatars.discourse-cdn.com/v4/letter/y/bbe5ce/32.png) [@yli](https://discuss.elastic.co/u/yli)\ **Post date:** [June 27, 2025, 8:22am UTC](https://discuss.elastic.co/t/no-observable-difference-between-bbq-and-default-configurations-in-elasticsearch-help-with-index-size-comparison/377817/7 "2025-06-27T08:22:57Z")
Hi @BenTrent , thanks for sharing your insights and sorry for injecting questions/comments here. 1. Keeping raw floating point values around `_source` seems to be inefficient approach, like discussed in [Knn\_vectors field understanding - Elastic Stack / Elasticsearch - Discuss the Elastic Stack](https://discuss.elastic.co/t/knn-vectors-field-understanding/374923/4), right? 2. If we don't keep raw floating point values around `_source`, the values are still persist by underlaying Lucene, right? Would it be fine if we fetch values from Lucene for rescoring purpose? 3. For re-quantizing and segment merging, may I ask whether we indeed need to keep the raw floating point values for any type of quantization? And how the re-quantization works? would be appreciated if you could share any resources. Thanks a lot and looking forward for your reply. Best, Yakun --- _[View the full topic](https://discuss.elastic.co/t/no-observable-difference-between-bbq-and-default-configurations-in-elasticsearch-help-with-index-size-comparison/377817)._