# Help! Why does my Docker container, configured with 4 CPUs and 8GB of memory, only use up to 35% CPU (1.4) and 43.79% memory (3587)?

**URL:** https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799
**Category:** Support
**Created:** [August 8, 2025, 3:32am UTC](https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799 "2025-08-08T03:32:06Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![hzy12138](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/hzy12138/32/7553_2.png) [@hzy12138](https://forum.weaviate.io/u/hzy12138)
#### Post date: [August 8, 2025, 3:32am UTC](https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799/1 "2025-08-08T03:32:07Z")

</div>

### Description

\<Help! Why does my Docker container, configured with 4 CPUs and 8GB of memory, only use up to 35% CPU (1.4) and 43.79% memory (3587)?!-- Please include as many details as possible about your issue →

### Server Setup Information

- Weaviate Server Version:1.25
- Deployment Method: docker
- Multi Node? Number of Running Nodes: 1
- Client Language and Version:
- Multitenancy?:

### Any additional Information

---

<div class="post-metadata">

### Author: ![Chaitanya\_Kulthe](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/chaitanya_kulthe/32/7546_2.png) [@Chaitanya\_Kulthe](https://forum.weaviate.io/u/Chaitanya_Kulthe)
#### Post date: [August 9, 2025, 6:20am UTC](https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799/2 "2025-08-09T06:20:49Z")

</div>

That’s actually normal, the 4 CPUs and 8 GB you gave the container are just the max it _can_ use, not what it will always use. In `docker stats`, CPU% is per core, so 35% total means it’s really using about 1.4 of your 4 cores. Weaviate will only push higher if you throw a lot of concurrent or heavy queries at it. Same with memory — 3.5 GB just means your current dataset and queries don’t need more right now. If you run bigger imports or stress it with parallel queries, you should see both CPU and RAM usage go up.

---

<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: [August 9, 2025, 6:26am UTC](https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799/3 "2025-08-09T06:26:19Z")

</div>

hi @Chaitanya_Kulthe and @hzy12138 !!

Welcome to our community 🤗

That’s right. You can defined some guardrails as [environment variables](https://weaviate.io/developers/weaviate/config-refs/env-vars) so you can have more control both on allocation and usage of those resources.

For example, if you do a lot of delete operations, you may want to tune the tombstone cleanup cycle (`TOMBSTONE_*`), or tune some memory and cpu variables.

I have created a [Weaviate Resource Calculator](https://github.com/dudanogueira/weaviate-resource-calculator) for memory, [based on this documentation](https://weaviate.io/developers/weaviate/concepts/resources)

You can check it online here: [https://weaviate-resource-calculator.streamlit.app/](https://weaviate-resource-calculator.streamlit.app/)

Let me know if this helps!

---

<div class="post-metadata">

### Author: ![Chaitanya\_Kulthe](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/chaitanya_kulthe/32/7546_2.png) [@Chaitanya\_Kulthe](https://forum.weaviate.io/u/Chaitanya_Kulthe)
#### Post date: [August 10, 2025, 5:54pm UTC](https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799/4 "2025-08-10T17:54:41Z")

</div>

Thanks for jumping in @DudaNogueira That Resource Calculator looks super helpful - exactly what people need for proper capacity planning.

---

<div class="post-metadata">

### Author: ![hzy12138](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/hzy12138/32/7553_2.png) [@hzy12138](https://forum.weaviate.io/u/hzy12138)
#### Post date: [August 11, 2025, 12:39am UTC](https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799/5 "2025-08-11T00:39:25Z")

</div>

All right, I’ll try it first. Thank you very much

---

<div class="post-metadata">

### Author: ![hzy12138](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/hzy12138/32/7553_2.png) [@hzy12138](https://forum.weaviate.io/u/hzy12138)
#### Post date: [August 11, 2025, 12:43am UTC](https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799/6 "2025-08-11T00:43:48Z")

</div>

By the way, I’d like to ask: Is it normal for a query to take more than one second on 100,000 data points with 3,495 dimensions? (4 GPUs, 8G Memory)

---

<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: [August 11, 2025, 3:19am UTC](https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799/7 "2025-08-11T03:19:06Z")

</div>

Hi!

Are you doing the a `nearVector` query or `nearText`?

When using `NearText`, Weaviate will first vectorize the query, and an api call to the inference model that will account for most of the latency.

When performing a `nearVector`, you already provide the vector query, and the latency can now be accounted by networking into to Weaviate and the search itself.

Let me know if this helps!

---

<div class="post-metadata">

### Author: ![hzy12138](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/hzy12138/32/7553_2.png) [@hzy12138](https://forum.weaviate.io/u/hzy12138)
#### Post date: [August 11, 2025, 7:04am UTC](https://forum.weaviate.io/t/help-why-does-my-docker-container-configured-with-4-cpus-and-8gb-of-memory-only-use-up-to-35-cpu-1-4-and-43-79-memory-3587/21799/9 "2025-08-11T07:04:40Z")

</div>

OK，I get it, thanks a lot
