Hello all,

Apologies if this isn’t the right place, but I have moved instances a few times, and in doing so I’ve accumulated a number of subscriptions from my old instances. I always used the “migrate” feature, and I have roughly 200 communities I’m subscribed to. Most are from various other instances that aren’t my own. That being said, I have Lemmy open on “subscribed” and “scaled”, as I found this gives me just what I want to see when I boot up the site.

But it is very slow, sometimes even timing out on Jerboa. I thought it was my instance, but I’ve had this issue on other instances as well. I’d imagine federating all my subscriptions would take some time, but then wouldn’t “All” cause even more problems? I’ve tried to look into this to no avail.

Am I the only one? I’m asking this more out of curiosity than an actual solution.

  • poVoq@slrpnk.netEnglish
    6·
    11 days ago

    Aside from general issues others have mentioned, our instance (slrpnk.net) is seeing some especially high database load in the last couple of days and I also noticed the subscribed page to be even slower than usual. I tried to figure out what it causing it, but so far there is no clear smoking gun, but I suspect some AI scrapers found a way to target the Lemmy API directly so our current scraper protections for the webinterface are inadequate.

  • poVoq@slrpnk.netEnglish
    5·
    11 days ago

    What you can try is to clear your browser cache for the main domain. In the past there was a bug in Lemmy that caused Firefox based browsers to accumulate many gigabytes of cache data and that slowed down the loading of the page significantly. In the latest version there are some fixes for this and it shouldn’t effect app usage, but I suspect this problem still persists to some extend.

  • your_paranoid_neighbour@lemmy.dbzer0.comEnglish
    2·
    11 days ago

    Every instance is like this it seems, maybe lemmy doesn’t make a batched select at the cache and the db, but idk.

    Maybe a new webscale backend could solve this, but i’m just a java backend developer, not a rust one. Maybe could be an interesting project, scala + pulsar + batching, turning lemmy into a microservices hellscape.

    Edit: but

  • SlurpingPus@lemmy.worldEnglish
    2·
    11 days ago

    To add to other answers, the result for the ‘all’ feed is likely to be cached, either explicitly by the server app or implicitly by the database. Personal feeds are less likely to be cached, since they’re only used by individual users.