what does your setup look like? docker for mempool? have you tried running mempool with just bitcoind (i.e. without fulcrum)?
nostr:npub18d4r6wanxkyrdfjdrjqzj2ukua5cas669ew2g5w7lf4a8te7awzqey6lt3 is there a reason why I have a very high 100% cpu usage (Thinkpad t530) and a lot of stale situations in the logs?
Connected to own fulcrum on the same node.
Have to restart mempool backend pretty often since 3.0.0
:/
Discussion
Followed this guide https://raspibolt.org/guide/bonus/bitcoin/mempool.html#requirements
No docker. I did not try to run it directly with core. I have 8GB ram on my machine, 13GB swap and 10GB zrm swap
strange part is that the mempool service is behaving normal when restarting it, but in about a day I have again sooo much CPU resources eaten up by it that my fans are running crazy
raspibolt guide looks old. just tested v3.0 with fulcrum according to our documentation for a fully manual install and it's working fine so far.
https://github.com/mempool/mempool/tree/master/backend
https://github.com/mempool/mempool/tree/master/frontend
recommend cross-referencing with our docs to see if you missed anything.
will run and observe for a day or so.
Got it. Will have a look 👀
So I did compare and ended using your configs, modified with my data.
Upgraded the machine to 16GB ram, but still: I have full blown 100% running cpu and hammering the rams just by mempool backend.
and its just updating the unconfirmed TX. Since days.
And it also has problems fetching conversion api credit all the time, no idea why. Pihole is not blocking it
nostr:npub1tv8gmfhalwnxxquxjzeh6gtdsdz6vg7vx0s3rt7s7uuw6aujh32qn77wn2 , hmm. So it’s not just you experiencing cpu hog issues
Oh so there are more?! ;)
High cpu because of this? 
Setting fiat to false did the trick. It’s still eating cpu during updating unconfirmed tx, but by far not that aggressive anymore.
"FIAT_PRICE": {
"ENABLED": false,
"PAID": false,
"API_KEY": "your-api-key-from-freecurrencyapi.com"
}
will not checkout an API key and set it to true again
good looks, did make that change but don't remember it causing high resource usage...just wanted to get rid of the log messages 😁
Kept it running with fiat enabled and a provided API key, but still, that was more cpu hungry than fiat disabled. So I will keep it like this for the sake of my cpu fans ;) for the time being