# Table\_used\_memory metric information

**URL:** <https://dragonfly.discourse.group/t/table-used-memory-metric-information/325>\
**Category:** Dragonfly Technical\
**Created:** [November 27, 2025, 11:04am UTC](https://dragonfly.discourse.group/t/table-used-memory-metric-information/325 "2025-11-27T11:04:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nunodio](https://yyz2.discourse-cdn.com/flex004/user_avatar/dragonfly.discourse.group/nunodio/32/130_2.png) [@nunodio](https://dragonfly.discourse.group/u/nunodio)\
**Post date:** [November 27, 2025, 11:04am UTC](https://dragonfly.discourse.group/t/table-used-memory-metric-information/325/1 "2025-11-27T11:04:59Z")

</div>

Hello everyone,

I’m running a Dragonfly setup on Kubernetes with a **Master/Replica** configuration. I’ve noticed a significant discrepancy in the memory usage between the two instances.

Specifically, the **`table_used_memory`** metric is different on the Master and the Replica, and I’m unsure of its exact meaning.

I have checked the official documentation and other online sources, but I cannot find a clear definition for **`table_used_memory`**.

Could anyone help clarify **what this metric represents**?

_(I’ve also opened a documentation issue here: [https://github.com/dragonflydb/documentation/issues/490](https://github.com/dragonflydb/documentation/issues/490))_

Thank you!

---

<div class="post-metadata">

**Author:** ![joezhou\_df](https://yyz2.discourse-cdn.com/flex004/user_avatar/dragonfly.discourse.group/joezhou_df/32/82_2.png) [@joezhou\_df](https://dragonfly.discourse.group/u/joezhou_df)\
**Post date:** [November 28, 2025, 5:25pm UTC](https://dragonfly.discourse.group/t/table-used-memory-metric-information/325/2 "2025-11-28T17:25:23Z")

</div>

While I’m not sure about the exact meaning of this specific field, but in code, it is related to snapshotting.

During the initial full sync between a primary and a replica, a snapshot is needed from the primary instance. Replicas don’t need to send snapshots to others. Thus, I’d say that a higher value of `table_used_memory` on the primary instance is expected.

We will update the documentation to reflect this.

---

<div class="post-metadata">

**Author:** ![joezhou\_df](https://yyz2.discourse-cdn.com/flex004/user_avatar/dragonfly.discourse.group/joezhou_df/32/82_2.png) [@joezhou\_df](https://dragonfly.discourse.group/u/joezhou_df)\
**Post date:** [December 2, 2025, 5:50pm UTC](https://dragonfly.discourse.group/t/table-used-memory-metric-information/325/3 "2025-12-02T17:50:33Z")

</div>

Recording @borys’s answer here for visibility:

`table_used_memory` shows total memory usage by internal hash tables. It can be different for the primary instance and replicas, because a replica is created after the primary and has more information regarding needed metadata and hash table size.

In most cases users should ignore this metric, as it was created for developers & maintainers.