1993: God, how we would love it if someone could tell us anything was “just that simple”, and then of course when you see a pie chart you go “Oh, a pie chart…”. I mean, it has more religious meaning now than a crucifix to see a pie chart. I mean, because…. why is that so popular? Because it reduces complexity. The complexity is very real but his little soundbites - 1993
@garpunkal@lemm.ee - do you know of the history of site_aggregates PostgreSQL table?
I think it would be a cool feature to redirect to another community. It isn't official, but !lemmywishlist@lemmy.ml is there for programmers/developers to find.
It’s mostly DDOS attacks though, not the influx of normal users.
Really? As site_aggregates table getting 1500 rows updated on every single new comment and post local insert is just the tip of the iceberg of how nobody has scrutinized the PostgreSQL performance. Thank you to lemmy.ca last weekend for looking at AUTO_EXPLAIN on their data.
I still can't find a call function. I've tried going right at API paths that seem defined, but it gives me a 404 on testing system. It seems the ability to set or clear it on a community is disabled. But I'm not entirely confident in reading the code correctly.
ok, I did know about that, just didn't memorize the name. I'm assuming only private messages and user account info (email address) are the real concern in terms of exposure? It's mostly a public posting thing, or not?
The quantity of users on Lemmy I still consider to be pretty low, the performance bugs need to be addressed on a big server. Bugs like not having a WHERE clause on an UPDATE hitting 1500 rows in a table (one row per server) instead of 1 single row... these need to be shaken out.
The errors of the overload themselves have been a way to throttle growth of the big servers. People were not able to insert new posts and comments into Lemmy.ml - reducing outbound federation activity too, and they went to other servers. This went on all of June and July.
subscribe to every community, and let federation load overwhelm your server.
Did that, takes lots of time to wait for the content to come in.... and there is no backfill. Plus I suspect that the oldest servers (online for several years) have some migration/upgrade related data that isn't being accounted for.
if local.lemmyusers > 15, crash constantly because of PostgreSQL nonsense logic and Rust ORM.