JudgeHardcase on Nostr: That's interesting. So in addition to making use of more RAM, by increasing the total ...
That's interesting. So in addition to making use of more RAM, by increasing the total memory space (RAM+swap) from ~10 GB to 18 GB, running Bitcoin Core is actually consuming more total memory. It's almost as if Core was (still is?) performing its own memory throttling (making its own decisions about which data to store in memory vs read/writing directly to disk) based on your total memory space. Maybe it does this in an attempt to optimize performance while processing the massive utxo set (if so, it would seem it's just not doing a very good job).
Published at
2024-09-07 11:05:59Event JSON
{
"id": "cb8414871029994c02999aadfef0e93293725b5e7a3caf4fc976ad04d0bf1c8b",
"pubkey": "b799ae27e0370b2856993e6d48f15d16539d4aa51fbf3ebdbd2bc40f60a4d25e",
"created_at": 1725707159,
"kind": 1,
"tags": [
[
"e",
"5980e1b60dba03296f948baab6cb0c9ed6afce57bc8b13f698b1227c8e54a3db",
"wss://relay.wellorder.net",
"root"
],
[
"p",
"82bdee506e769ebc94ee2f362d07c1960dce40bac650d826a42f8e0c019c3c96"
]
],
"content": "That's interesting. So in addition to making use of more RAM, by increasing the total memory space (RAM+swap) from ~10 GB to 18 GB, running Bitcoin Core is actually consuming more total memory. It's almost as if Core was (still is?) performing its own memory throttling (making its own decisions about which data to store in memory vs read/writing directly to disk) based on your total memory space. Maybe it does this in an attempt to optimize performance while processing the massive utxo set (if so, it would seem it's just not doing a very good job).",
"sig": "7947ade0f6434af93c266b319618597bd2eff223755f4ad17849c72bc2032fcb0ab682d3996a51906afc181130454c81cf7a02e935b628198301bf7bc1724907"
}
