Howard Chu @ Symas on Nostr: This is another aspect of #LMDB's design that most people don't appreciate - by ...
This is another aspect of #LMDB's design that most people don't appreciate - by requiring you to declare up front the maximum size you'll allow the DB to grow to, you'll never be awakened at 5am to deal with a server that ran out of disk space. Or a server that killed other apps because it ate up all of the free disk space. Put the DB on a filesystem (or a raw block device), set the maxsize equal to the free space remaining on that storage, and forget about it.
https://mastodon.social/@gvwilson/111861409907828826Published at
2024-02-02 14:52:47Event JSON
{
"id": "a068889c8e95df0c18546392f760238de5834d68436823dfb4207e1d01363954",
"pubkey": "5aeb250b3075a12bd05e16c8a3c40da91a553fa92164a39915a3a0615fe51864",
"created_at": 1706885567,
"kind": 1,
"tags": [
[
"t",
"lmdb"
],
[
"proxy",
"https://mastodon.social/users/hyc/statuses/111862452582273308",
"activitypub"
]
],
"content": "This is another aspect of #LMDB's design that most people don't appreciate - by requiring you to declare up front the maximum size you'll allow the DB to grow to, you'll never be awakened at 5am to deal with a server that ran out of disk space. Or a server that killed other apps because it ate up all of the free disk space. Put the DB on a filesystem (or a raw block device), set the maxsize equal to the free space remaining on that storage, and forget about it.\n\nhttps://mastodon.social/@gvwilson/111861409907828826",
"sig": "e0068379d82f9d3e2c8505da687a62eec664a14550da23a62eaf2e916382c81df6968c76bf8bce1e88db09de404e6f392de5531055e86ad62ba9dcadc3bc02e5"
}