- cross-posted to:
- asklemmy@lemmy.ml
- cross-posted to:
- asklemmy@lemmy.ml
Can my humble, single-user instance handle it? Are there any settings I need to be careful about? Should I just backup my server and wing it?
You must log in or register to comment.
Can my humble, single-user instance handle it?
Maybe?
FWIW this information is based on the experience when using remote hosting not self hosting.
The main issue for us was tuning the database performance. The bot can beat your database to death sometimes and just throwing resources at it won’t necessarily solve it. related low effort meme Our experience was that the bot performance hit wasn’t really noticable immediately but it adds up as more and more communities are added to the database. There also seem to be bursts of database load at times, maybe that’s when new instances join the network? They seem to only last a short time though and haven’t really caused problems.
TLDR- Expect an eventual performance hit. If it’s too much you can always disable the bot or adjust what it does.
did you guys end up caching the db queries to help alleviate it?
I’m not sure it’s been entirely solved. Our host is working through an unrelated hardware problem that hit in the middle of our last round of tuning but things have been behaving better aside from that.
The answer for us has been in adjusting the lemmy pool size to the database and tweaking the available resources to find a happy medium.
