Event JSON
{
"id": "56329ba5265065f4a8fcc06bf1173b6546d9776d8b7dd0c41c912cc9b74efc60",
"pubkey": "36674e95441a48ffca080d035a5a9c654af11742a493d7eb6368968ed8fd9d0d",
"created_at": 1691769472,
"kind": 1,
"tags": [
[
"p",
"a3bae9d9efbe9099b83661bc1f5719f9f842957f28b5b692eb5fbf652f0c0acc",
"wss://relay.mostr.pub"
],
[
"p",
"cde316fed609ec8969c7925309d1c00af277393d61be57980fbf387bf80c6de9",
"wss://relay.mostr.pub"
],
[
"e",
"d012b466733644d7521bd402f0c96b3874450a449d51ef25cc61f029b305daf0",
"wss://relay.mostr.pub",
"reply"
],
[
"content-warning",
"WriteFreely scaling help"
],
[
"proxy",
"https://talk.ogre.red/users/info/statuses/110871804154935529",
"activitypub"
]
],
"content": "nostr:npub15wawnk00h6gfnwpkvx7p74cel8uy99tl9z6mdyhtt7lk2tcvptxq2rezxc \n\nIt might not be a quick fix, but spinning off older entries into their own quasi-archive tables could help, especially if they're ones that are rarely accessed. You'd need a routing mechanism somewhere to detect when to jump from the main table to the archives.\n\nAnd do you have something like Redis in place for caching common / recent queries? That could help for material that's frequently accessed but doesn't change often.",
"sig": "6dab468fd46c3cbf1ee7c5f5754617103076cbfc5eaeeef155644326958fb75cec51a84b121d67387e4c6758f3d0afc56c516b5a74afdcd32fe3214dc02e1e59"
}