# Documentation - Maximum index size, disk paging

**URL:** https://forum.weaviate.io/t/documentation-maximum-index-size-disk-paging/1068
**Category:** Support
**Created:** [December 6, 2023, 11:07am UTC](https://forum.weaviate.io/t/documentation-maximum-index-size-disk-paging/1068 "2023-12-06T11:07:06Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)
#### Post date: [December 6, 2023, 10:54pm UTC](https://forum.weaviate.io/t/documentation-maximum-index-size-disk-paging/1068/4 "2023-12-06T22:54:07Z")

</div>

Hi Greg!

Thanks for those questions and registering your journey 🙂

So yes, by default, Weaviate will keep data in memory. This is because `vectorCacheMaxObjects` is set to trilions.

So if you reduce this setting to a number less then your total ammount of objects, you will have some objects in DISK and in RAM.

For this ammount of data, [Product Quantization](https://weaviate.io/developers/weaviate/concepts/vector-index#hnsw-with-compression) and playing with vectorCacheMaxObjects will help, along of course with having enough disk and memory and finding the balance between speed and memory.

Let me know if this helps. We would love to understand better your usecase.

Feel free to ping us in our slack channels 🙂

Thanks!

---

_[View the full topic](https://forum.weaviate.io/t/documentation-maximum-index-size-disk-paging/1068)._