mleku on Nostr: so, i'm gonna do it rewriting this database so instead of storing the events as ...
so, i'm gonna do it
rewriting this database so instead of storing the events as values, it's just gonna put them in a filesystem in their binary form, with the filename being the event id hash
the memory leak is all about unpacking those out of the database, and it can be avoided and pushing it into the filesystem means i don't have to think about the read caching, that's already handled by the kernel
Published at
2024-10-26 22:14:36Event JSON
{
"id": "ce499f50e5c285acf4b8ca55b48f10da01236c3c394462b6bc109d00ba3d4405",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1729980876,
"kind": 1,
"tags": [
[
"client",
"noStrudel",
"31990:266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5:1686066542546"
]
],
"content": "so, i'm gonna do it\n\nrewriting this database so instead of storing the events as values, it's just gonna put them in a filesystem in their binary form, with the filename being the event id hash\n\nthe memory leak is all about unpacking those out of the database, and it can be avoided and pushing it into the filesystem means i don't have to think about the read caching, that's already handled by the kernel",
"sig": "2765129bc34d134110ec94990f182eaf3773572d8269f6550ab7291497a20933f1ecf080dc1708a5ba647ff98e1ed178f173699030ae2bb7451fbaf79424f44c"
}
