Electrs using 170% of my CPU

Support and Troubleshooting
1

Hi,

I have had umbrel running for a few months now. All the sudden I have noticed the electrs process is using a lot of CPU. I understand this is the indexing of electrum, but the node has been running for weeks and the blockchain has been fully syncronized

this is what I see on the log files

[2022-05-12T10:05:11.863Z INFO electrs::chain] chain updated: tip=00000000000000000001ce5467247a5788dfff880e5cf64ff96ca2cca34b640d, height=736046
electrs | [2022-05-12T10:34:39.137Z INFO electrs::index] indexing 1 blocks: [736047…736047]
electrs | [2022-05-12T10:34:39.322Z INFO electrs::chain] chain updated: tip=00000000000000000007dd1decbec734f5230eb1f38ee4e41ab3dfff4c8559b2, height=736047
electrs | [2022-05-12T10:35:39.079Z INFO electrs::electrum] your wallet uses less efficient method of querying electrs, consider contacting the developer of your wallet. Reason: blockchain.scripthash.get_history called for unsubscribed scripthash: b1c43c684d0c53f1c40cdd0a2a00303c0e8fa5751d3afde1717bd6436b6a79b8
electrs | [2022-05-12T11:20:01.288Z INFO electrs::electrum] your wallet uses less efficient method of querying electrs, consider contacting the developer of your wallet. Reason: blockchain.scripthash.get_balance called for unsubscribed scripthash: b1c43c684d0c53f1c40cdd0a2a00303c0e8fa5751d3afde1717bd6436b6a79b8
electrs | [2022-05-12T12:02:45.782Z INFO electrs::electrum] your wallet uses less efficient method of querying electrs, consider contacting the developer of your wallet. Reason: blockchain.scripthash.get_history called for unsubscribed scripthash: b1c43c684d0c53f1c40cdd0a2a00303c0e8fa5751d3afde1717bd6436b6a79b8

2

LOL 170%?!
That would be the amazing invention of the century, how to use 170% power from what you have.
Just restart your node, wait to sync and catch up and all will be just fine.
Sometimes when LND is taking a lot of memory and resources, electrs is getting struggled to catch up.
A restart of the entire machine (and better a shut down, wait 10 seconds to clear up and then a start) will fix a lot of issues with resources, in special if you have a weak machine like a RPi.

3

LOL
sorry what I meant was 170% CPU as reported from the top command. I believe the top command reports CPU usage in relation to the power of 1 core.

Restarted and seems to be fine.
Thanks

1 Like