pull down to refresh

100 sats \ 4 replies \ @SimpleStacker 12 Sep \ parent \ on: Why I'm Against Covenants (Jimmy Song) bitcoin
Thanks. The github discussion I linked above (copied again for convenience) shows that multiple users are experiencing this. My hypothesis was that the UTXO got too large to hold in RAM and so it is using HD, but I could easily be wrong.
https://github.com/raspibolt/raspibolt/issues/1482#issuecomment-3263903647
write
preview
30 sats \ 0 replies \ @optimism 13 Oct
Have charted debug=bench on my RPi4 8GB w/ 2TB Samsung T7 (and txindex=1 per raspibolt recommendation) for the first 240k blocks as a test and to develop some tooling. The x axis is 1k blocks cumulative.
This means that my log parser works so I will now plan an uninterrupted session when I don't have to fly in the middle of the week, to chart it all out completely. When I know what blocks to look at, I can write a custom bench-bitcoin routine so we can trace it on different platforms and see what's what.
reply
0 sats \ 2 replies \ @optimism 12 Sep
Saw your comment on there previously. I haven't tried raspibolt personally and there is some ongoing work w/ core towards this - I must admit I used 27.x, and there are reports of a regression with 29.x: see https://github.com/bitcoin/bitcoin/pull/32043 and https://github.com/bitcoin/bitcoin/issues/32832
Shall I get a 4GB RPi4?
reply
100 sats \ 1 reply \ @SimpleStacker 12 Sep
Interesting about the regression. That's up to you! I currently don't have any new insights, and my node is finally fully synced.
reply
0 sats \ 0 replies \ @optimism 12 Sep
Never mind, I didn't read well and you have an 8GB - I'll try to get that.
Edit: will get it next week.
reply