mleku on Nostr: bah... changing the event store query function to return the events serially messes ...
bah... changing the event store query function to return the events serially messes with the model of how two tier (layer2) event stores work
for now, ok, going to change it to make the assumption that all events in the L2 are known about, just there is only their index and event ID stored... i think that's ok, but it is an extra overhead to consider in the garbage collector... it kinda implies that the low/high water marks need to be lower to allow space for the size of the L2 indexes
but i guess it's not that huge, i mean... ok, tags can take up a lot of space... but compared to the event as well, and the tags are just truncated 8 bytes out of 32
ah, engineering complex things is complex
Published at
2024-11-17 05:21:20Event JSON
{
"id": "eef0f83ce1705c4b03b45935f0b69cf08ee9d348a25a2c761ce275d348b3a7cb",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1731820880,
"kind": 1,
"tags": [
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "bah... changing the event store query function to return the events serially messes with the model of how two tier (layer2) event stores work\n\nfor now, ok, going to change it to make the assumption that all events in the L2 are known about, just there is only their index and event ID stored... i think that's ok, but it is an extra overhead to consider in the garbage collector... it kinda implies that the low/high water marks need to be lower to allow space for the size of the L2 indexes\n\nbut i guess it's not that huge, i mean... ok, tags can take up a lot of space... but compared to the event as well, and the tags are just truncated 8 bytes out of 32\n\nah, engineering complex things is complex",
"sig": "93df58d7c7a178e925317ea2c6b9c5b08eb46f982e9b1dc3a8d21943447ec450eaf28cce81a06e004f1b8a56d63c84e2a70b5f1bfe22a94ddcb4ed28331ce833"
}