<p>From the documentation: </p>

<pre><code>  "bytes": xxxxx,              (numeric) Sum of all virtual transaction sizes as defined in BIP 141. Differs from actual serialized size because witness data is discounted
  "usage": xxxxx,              (numeric) Total memory usage for the mempool
</code></pre>

<p><code>bytes</code> is the size as calculated as vBytes as would be considered for inclusion in a block, <code>usage</code> is the logical size in actual bytes that are consuming memory. </p>

CC BY-SA 4.0
2020-05-06T04:34:15.037Z
2020-05-06T04:34:15.037Z
Claris
<p><code>getmempoolinfo</code> returns <code>bytes</code> and <code>usage</code>. Currently, the value I have for <code>bytes</code> is <code>1316363</code> and the value I have for <code>usage</code> is <code>4826112</code>.</p>

<p>I'm assuming that <code>bytes</code> is how much space these transactions would require if they were to be included in a block while <code>usage</code> is the size they are currently taking on my computer. That would imply that the transactions get compressed somehow (or some nonessential info gets stripped away) before they're included in a block. Is that correct or am I way off?</p>

<bitcoin-core><mempool>
The difference between mempool "bytes" and "usage"
M.K. Safi
# The difference between mempool "bytes" and "usage"

(Asked by: username_0 on 2020-05-06)

`getmempoolinfo` returns `bytes` and `usage`. Currently, the value I have for `bytes` is `1316363` and the value I have for `usage` is `4826112`.

I'm assuming that `bytes` is how much space these transactions would require if they were to be included in a block while `usage` is the size they are currently taking on my computer. That would imply that the transactions get compressed somehow (or some nonessential info gets stripped away) before they're included in a block. Is that correct or am I way off?

**Tags:** bitcoin-core, mempool


---

## 1 answers

### Answer by username_1 on 2020-05-06. Score: 2

From the documentation: 
  "bytes": xxxxx,              (numeric) Sum of all virtual transaction sizes as defined in BIP 141. Differs from actual serialized size because witness data is discounted
  "usage": xxxxx,              (numeric) Total memory usage for the mempool

bytes is the size as calculated as vBytes as would be considered for inclusion in a block, usage is the logical size in actual bytes that are consuming memory.


---

