🍷 nostr.wine is handling the new read traffic without a sweat. filter.nostr.wine holding strong for our paid users. The efficiency improvements we made to query chunking seems to be working.

We are now serving around 500gb per day across all nostr.wine services and thats with some rate limiting for read spammers + keeping a careful watch of the daily traffic. If I wasn’t actively blocking/communicating with aggregators/crawlers it could be 2-3x as much.

A lot heavier on bandwidth than I would have originally expected. CPU/Memory usage is under control now.

Reply to this note

Please Login to reply.

Discussion

πŸ’―

Ty always for your hard work πŸ˜ŠπŸ’œ

think i heavily rely on 🍷 whenever it’s down i can feel the pain πŸ€“

Working towards a (almost) never down future 🍷

Alright, so i assume your goal is to run a free public relay, right?

This is some hardware specifications that were used by some relay operators

#[3]

#[4]

#[5]

Small Relay example (For small number of users)

#[6]

Actually, the main issue is bandwidth. You will need a server with large bandwidth capacity especially if your relay becomes popular

#[7]