Lemmy

12572 readers

3 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

How to Choose a Lemmy Instance Based on Latency and Least Blocked Users? (lemmy.ml)

submitted 1 year ago by Veritas@lemmy.ml to c/lemmy@lemmy.ml

8 comments fedilink hide all child comments

Hi everyone, I'm having trouble finding a Lemmy instance that works well for me. The main instance I use is down, and most others are too slow. I'm wondering if there's a way to choose an instance based on latency and the least blocked users. I found two relevant issues on the awesome-lemmy-instances GitHub page: issue #12 about choosing an instance based on latency and issue #17 about choosing an instance with the least blocked users. However, I'm not sure how to implement these into the main script to generate a readme with a few recommended instances. Does anyone have any advice or tips on how to choose a Lemmy instance based on these criteria? Thanks in advance for your help!

you are viewing a single comment's thread
view the rest of the comments

[–] RoundSparrow@lemmy.ml 4 points 1 year ago

Something to consider... Lemmy runs fast with no data in it. Latency issue is tied to how much data they have stored in PostgreSQL. If they aren't holding full copies of all the remote communities, sure it is faster, but your searches and All aren't going to turn up much.