Another idea: even with everything on ZFS you can fine-tune caching. I would put .bitcoin/blocks (historical data) on a separate ZFS dataset and allow only metadata caching on that dataset:
zfs set primarycache=metadata $YOUR_DATASET
Indexes like txindex probably deserve data caching, not sure.
note1gxfn050dgsx45w0dyylsnts5548st8k3az6898l8yz6y7l4p4e8spfhd0m
xmrk ₿ ⚡️ /
npub1zu…2qhzy
2023-10-09 17:10:35
Author Public Key
npub1zues2p7qdajk9hv7xn5ldntj3pufzl3jwzwa4dhlavxdkj27g92q62qhzyPublished at
2023-10-09 17:10:35Event JSON
{
"id": "dd5983b02801e134657f2850247cb25373af57cc93fb9c2cef510bc255ebdcf3",
"pubkey": "17330507c06f6562dd9e34e9f6cd728878917e32709ddab6ffeb0cdb495e4154",
"created_at": 1696871435,
"kind": 1,
"tags": [],
"content": "Another idea: even with everything on ZFS you can fine-tune caching. I would put .bitcoin/blocks (historical data) on a separate ZFS dataset and allow only metadata caching on that dataset:\nzfs set primarycache=metadata $YOUR_DATASET\n\nIndexes like txindex probably deserve data caching, not sure.\n\nnote1gxfn050dgsx45w0dyylsnts5548st8k3az6898l8yz6y7l4p4e8spfhd0m",
"sig": "fd47820c8ebf510f4b5ba7176f083524a9933e89c47fec65b959dc78e4992ee4b85138e46d95e9de93282cd8ac08f011f35fa7d394c25af92c9b86ccef2a3058"
}