<p>I have the same set up and getinfo for me takes about 10-20s initially but then takes ~5s there after. (I need to restart the daemon periodically as it crashes for some reason). I'm running 0.11.1 and haven't made any special tweaks. gettxoutsetinfo takes around 12 minutes. CPU, RAM and Swap comparable with what you have as well. </p>

<p>Hardware is probably the most obvious limitation. You could overclock the Pi CPU but I doubt it will drastically reduce the response time though.</p>

CC BY-SA 3.0
2017-02-13T08:57:45.190Z
I've had the same problem with crashes when using version 0.11.x. I recommend updating to v0.13.x and daemon won't crash anymore.
grajsek
CC BY-SA 3.0
2016-01-20T00:16:33.453Z
2016-01-20T00:16:33.453Z
cloudnthings
<p>Running Bitcoin 0.11 on Raspberry Pi 2 (Quad core 900MHz 1GB RAM, 128GB Flash Drive for blockchain, 8GB SD Card for OS and software).</p>

<p>Blockchain is fully synced, 13 connections.
In htop, I see I'm around 700/862MB RAM, 1/99MB Swap. 1 processor is up around 90% but the other 3 are down in the &lt;5% range.</p>

<p>I SSH into the pi (running bitcoind, no GUI) and some commands take forever to get a response. Sometimes <code>getinfo</code> or <code>getpeerinfo</code> will take 30-60 seconds to print out. <code>gettxoutsetinfo</code> takes way longer: almost ten minutes!! I don't see any resources being maxed out in htop during this time.</p>

<p>I know this is a low-power machine, maybe the UTXO set hash in the <code>gettxoutsetingo</code> command is what's specifically taking so long in that case. </p>

<p>Can I adjust any settings either in the RPi OS or bitcoin.conf to get snappier performance? Ideally I would like to run a few python scripts that use RPC, triggered by bitcoin's <code>blocknotify=...</code> </p>

CC BY-SA 3.0
2016-01-07T05:07:55.777Z
I'm guessing it is hardware, however `gettxoutsetinfo` is supposed to take a while. I switched my node over to a spare PC (3ghz 4gb ram)as my node, it responds much quicker to the `getinfo` `getmininginfo` and other RPC calls, less than 1 second.
m1xolyd1an
CC BY-SA 3.0
2016-01-07T07:17:37.857Z
1 GB of RAM seems low for bitcoind, and 99 MB of swap doesn't help much.  `top` should show a state for the `bitcoind` process.  If it's in state R most of the time, then CPU is probably the bottleneck.  If state D, then it may be I/O (including swapping / paging).
Nate Eldredge
CC BY-SA 3.0
2016-01-07T07:21:33.257Z
There's about 15 "bitcoind" threads and most are in state S. One is in state D.
pinhead
CC BY-SA 4.0
2021-01-04T09:21:10.817Z
If you are using an auth cookie instead of explicitly setting the `rpcuser` and `rpcpassword` in your `bitcoin.conf` - then it is slower I have noticed.
tread
<json-rpc><raspberry-pi><bitcoin-cli>
bitcoin-cli very slow to respond to RPC calls (Raspberry Pi)
pinhead
# bitcoin-cli very slow to respond to RPC calls (Raspberry Pi)

(Asked by: username_0 on 2016-01-06)

Running Bitcoin 0.11 on Raspberry Pi 2 (Quad core 900MHz 1GB RAM, 128GB Flash Drive for blockchain, 8GB SD Card for OS and software).

Blockchain is fully synced, 13 connections.
In htop, I see I'm around 700/862MB RAM, 1/99MB Swap. 1 processor is up around 90% but the other 3 are down in the <5% range.

I SSH into the pi (running bitcoind, no GUI) and some commands take forever to get a response. Sometimes `getinfo` or `getpeerinfo` will take 30-60 seconds to print out. `gettxoutsetinfo` takes way longer: almost ten minutes!! I don't see any resources being maxed out in htop during this time.

I know this is a low-power machine, maybe the UTXO set hash in the `gettxoutsetingo` command is what's specifically taking so long in that case.

Can I adjust any settings either in the RPi OS or bitcoin.conf to get snappier performance? Ideally I would like to run a few python scripts that use RPC, triggered by bitcoin's `blocknotify=...`

**Tags:** json-rpc, raspberry-pi, bitcoin-cli

> **Comments:**
> **username_1**: I'm guessing it is hardware, however `gettxoutsetinfo` is supposed to take a while. I switched my node over to a spare PC (3ghz 4gb ram)as my node, it responds much quicker to the `getinfo` `getmininginfo` and other RPC calls, less than 1 second.  
> **username_2**: 1 GB of RAM seems low for bitcoind, and 99 MB of swap doesn't help much.  `top` should show a state for the `bitcoind` process.  If it's in state R most of the time, then CPU is probably the bottleneck.  If state D, then it may be I/O (including swapping / paging).  
> **username_0**: There's about 15 "bitcoind" threads and most are in state S. One is in state D.  
> **username_3**: If you are using an auth cookie instead of explicitly setting the `rpcuser` and `rpcpassword` in your `bitcoin.conf` - then it is slower I have noticed.  

---

## 1 answers

### Answer by username_4 on 2016-01-20. Score: 1

I have the same set up and getinfo for me takes about 10-20s initially but then takes ~5s there after. (I need to restart the daemon periodically as it crashes for some reason). I'm running 0.11.1 and haven't made any special tweaks. gettxoutsetinfo takes around 12 minutes. CPU, RAM and Swap comparable with what you have as well.

Hardware is probably the most obvious limitation. You could overclock the Pi CPU but I doubt it will drastically reduce the response time though.

> **Comments:**
> **username_5**: I've had the same problem with crashes when using version 0.11.x. I recommend updating to v0.13.x and daemon won't crash anymore.  

---

