<p>Buffers are areas of memory where data waits before it gets processed. So a receive buffer holds some data coming from the network until the process (bitcoind) is ready to actually handle it. The send buffer holds data put there by bitcoind until your operating system is ready to actually dump it on the network wire.</p>

<p>They need to be a decent size not to cripple smooth communication. Too large would just be a waste and not help anything. In 99.9% of the cases the defaults should be fine.</p>

<p>They're not a method of affecting the bandwidth use though.</p>

<p>I'm fairly sure the upcoming version will have options for rudimentary bandwidth throttling. Until then you could try lowering <code>maxconnections</code> (default 125) if you want a lower bandwidth on average (over a month for example). But peak usage will still be high.</p>

<p>Depending on your operating system you could try some QOS scripts/settings or QOS settings on your router.</p>

CC BY-SA 3.0
2017-09-06T04:40:15.750Z
would changes on maxreceivebuffer and maxsendbuffer limit affect json-rpc connection?
eugene
CC BY-SA 3.0
2015-12-17T17:09:44.790Z
2015-12-17T17:09:44.790Z
Jannes
<p>What do Bitcoin Core options "maxreceivebuffer" and "maxsendbuffer" do? Is this a way of controlling the bandwidth Bitcoin Core uses?</p>

<bitcoind><bitcoin-core><network><full-node>
What do Bitcoin Core options "maxreceivebuffer" and "maxsendbuffer" do?
Geremia
# What do Bitcoin Core options "maxreceivebuffer" and "maxsendbuffer" do?

(Asked by: username_0 on 2015-12-17)

What do Bitcoin Core options "maxreceivebuffer" and "maxsendbuffer" do? Is this a way of controlling the bandwidth Bitcoin Core uses?

**Tags:** bitcoind, bitcoin-core, network, full-node


---

## 1 answers

### Answer by username_1 on 2015-12-17. Score: 1 | Accepted answer

Buffers are areas of memory where data waits before it gets processed. So a receive buffer holds some data coming from the network until the process (bitcoind) is ready to actually handle it. The send buffer holds data put there by bitcoind until your operating system is ready to actually dump it on the network wire.

They need to be a decent size not to cripple smooth communication. Too large would just be a waste and not help anything. In 99.9% of the cases the defaults should be fine.

They're not a method of affecting the bandwidth use though.

I'm fairly sure the upcoming version will have options for rudimentary bandwidth throttling. Until then you could try lowering `maxconnections` (default 125) if you want a lower bandwidth on average (over a month for example). But peak usage will still be high.

Depending on your operating system you could try some QOS scripts/settings or QOS settings on your router.

> **Comments:**
> **username_2**: would changes on maxreceivebuffer and maxsendbuffer limit affect json-rpc connection?  

---

