# Weaviate resource usage

**URL:** <https://forum.weaviate.io/t/weaviate-resource-usage/2486>\
**Category:** Support\
**Created:** [May 26, 2024, 7:50pm UTC](https://forum.weaviate.io/t/weaviate-resource-usage/2486 "2024-05-26T19:50:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![darshilshahquantive](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/darshilshahquantive/32/1588_2.png) [@darshilshahquantive](https://forum.weaviate.io/u/darshilshahquantive)\
**Post date:** [May 26, 2024, 7:50pm UTC](https://forum.weaviate.io/t/weaviate-resource-usage/2486/1 "2024-05-26T19:50:15Z")

</div>

### Description

Weaviate using almost 100% of memory even after setting the LIMIT\_RESOURCES to true

### Server Setup Information

- Weaviate Server Version: 1.23.3
- Deployment Method: k8s
- Multi Node? Number of Running Nodes: no
- Client Language and Version: python

### Any additional Information

We are using Weaviate for indexing objects with the OpenAI model `text-adda-002`, which produces vectors with 1536 dimensions each.

We have multiple classes in our dataset. One of these classes, which is the most resource-intensive, is configured with `vectorCacheMaxObjects` set to 10,000. This class has approximately 1.2 million vector indices, as indicated by the Prometheus `vector_index_size` monitoring metrics. This configuration ensures that it doesn’t consume all available memory, as the maximum cache objects are limited to 10,000. The remaining classes each have around 1 million vector indices and are not configured with `vectorCacheMaxObjects`. The instance has a total of 24 GB of RAM available.

However, when observing the memory usage graph, we see a gradual increase in memory consumption until it reaches 100%, eventually leading to an out-of-memory (OOM) event that causes Weaviate to restart.

i am unable to find any cause for this

also i am adding a screenshot for my vector index size count changes as i doubt delete operations or ingestion operations can increase the resources :

 ![image(1)](https://canada1.discourse-cdn.com/flex027/uploads/weaviate/original/2X/1/1ac322a6f8dd8371cc4531ae9c49c29d14d4fb05.jpeg)

---

<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:** [May 28, 2024, 12:41pm UTC](https://forum.weaviate.io/t/weaviate-resource-usage/2486/2 "2024-05-28T12:41:09Z")

</div>

hi @darshilshahquantive !

Welcome to our community! 🤗

As this was also [asked in slack](https://weaviate.slack.com/archives/C017EG2SL3H/p1716753314982949), here is the recommendations from @antas-marcin 🤗

> Please set `GOMEMLIMIT` to about 90% of your available memory and (let’s say `GOMEMLIMIT=21GiB` ) and maybe set `GOGC` to `50` which should trigger Go GC more frequently

and

> after setting those values, please observe how your setup behaves, maybe those values will work for your setup or maybe they would need further tuning

Thanks!!