A look into operation of the server.

Relays running since Oct 12! Thanks to nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4's amazing work.

Notes database is growing big, currently 95GB and RAM is not enough anymore. Should I upgrade or should I start removing notes?

Reply to this note

Please Login to reply.

Discussion

RAM n SWAP usage is not normal.

disk DB growth without drop table is fine. 95GB

may consider to restart. or cron job or reload restart

hdd/ssd cannot be unlimited forever. hence either he drop / trim table or config LIMIT rentention persion of 6month or 1year - 1 Year =. 31,556,952 Seconds

This won't work forever, maybe we need a FasterKV relay

it is clever to use another DB for historical notes. some relays may excel in providing long history. strfry is more suitable for recent events.

Yea partitioning

Do you run strfry compact?

i'm currently working on a two level data store scheme for replicatr... there is a super mega ZSTD compression option available on it, maximum zstd... and with big blocks (snicker) they will squash all those words very small... just playing with it at the moment in a simple second level archival store with no search capability, leaving the indexes in the main but removing the event data

well, doing it for testing at this point, because i've got another data store to test with, just a morning's work building a simple one to implement the overflow logic

is this suitable to store historical notes?

Not like an ongoing basis. Rarely. For example when I want to upgrade or move a replication or make a replication.

Btw strfry hasn't been updated for 4 months. Is the maintainer ok?

on github I am seeing eth related activity 😢