Conversation

Notices

Embed this notice
Owl (owl@nicecrew.digital)'s status on Friday, 25-Oct-2024 05:27:22 JST Owl
That was when he blocked me after I thought I'd dunk on him after trying to talk some mad shit.

In conversation about a month ago from nicecrew.digital permalink
- Embed this notice
  ins0mniak (ins0mniak@majestic12.airforce)'s status on Friday, 25-Oct-2024 05:27:19 JST ins0mniak
  in reply to
  @Owl @transgrammaractivist @dj @NonPlayableClown yeah thats the thing, I get a lot of broken threads where I can't see who my friends are talking to.
  
  It's a bitch move, he thinks he runs fedi or something.
  
  In conversation about a month ago permalink
  
  ✙ dcc :pedomustdie: :phear_slackware: likes this.
- Embed this notice
  Owl (owl@nicecrew.digital)'s status on Friday, 25-Oct-2024 05:27:20 JST Owl
  in reply to
  Four months back I muted Poa.st for a day just to see what happened. The results were surprising. What I don't understand about defederation is, just because you don't want to talk to someone, nobody else should be able to either? That's fucked.
  In conversation about a month ago permalink
  Attachments
  1. Untitled attachment
- Embed this notice
  ins0mniak (ins0mniak@majestic12.airforce)'s status on Friday, 25-Oct-2024 05:27:21 JST ins0mniak
  in reply to
  @Owl @transgrammaractivist @dj @NonPlayableClown He de-federated my instance.
  
  I'm happy about it tbh my timeline has been chill quality ever since.
  
  In conversation about a month ago permalink
- Embed this notice
  Phantasm (phnt@fluffytail.org)'s status on Friday, 25-Oct-2024 05:29:14 JST Phantasm
  in reply to
  @cvnt @ins0mniak @transgrammaractivist @Owl @dj @NonPlayableClown Yeah that really sucked. I don't even know who wrote that broken code 4 years ago. At least he fixed it somewhat quickly.
  
  There was a similar bug recently where remote blocks were rejected. Sort of an unintended anti-blockbot measure.
  
  https://git.pleroma.social/pleroma/pleroma/-/issues/3331
  In conversation about a month ago permalink
  Attachments
  1. Domain not in remote thumbnail source whitelist: git.pleroma.social
    
    Incoming remote blocks aren't handled properly (#3331) · Issues · Pleroma / pleroma · GitLab
    
    Environment Installation type (OTP or From Source): Source Pleroma version (could be found in the "Version" tab of...
  ✙ dcc :pedomustdie: :phear_slackware: likes this.
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 05:29:15 JST broken god
  in reply to
  @phnt @NonPlayableClown @Owl @dj @ins0mniak @transgrammaractivist
  
  Breaking follows is basic userland, ask me how I know he doesn't test shit before pushing updates.
  
  In conversation about a month ago permalink
- Embed this notice
  Phantasm (phnt@fluffytail.org)'s status on Friday, 25-Oct-2024 05:29:16 JST Phantasm
  in reply to
  @cvnt @ins0mniak @transgrammaractivist @Owl @dj @NonPlayableClown To some extent I enjoy running develop. It's like a wheelspin of what will break next every time I update.
  
  To be fair, the stalling federation was an Oban issue.
  
  In conversation about a month ago permalink
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 05:29:17 JST broken god
  in reply to
  @ins0mniak @NonPlayableClown @Owl @dj @transgrammaractivist
  
  I was, the core website is still over wg backhaul over starlink, but 2.7.0 Pleroma isn't worth hosting. Feld is retarded.
  
  In conversation about a month ago permalink
- Embed this notice
  ins0mniak (ins0mniak@majestic12.airforce)'s status on Friday, 25-Oct-2024 05:29:18 JST ins0mniak
  in reply to
  @cvnt @transgrammaractivist @Owl @dj @NonPlayableClown Yeah its comf.
  
  You running that over starlink too huh?
  
  In conversation about a month ago permalink
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 05:29:19 JST broken god
  in reply to
  @ins0mniak @NonPlayableClown @Owl @dj @transgrammaractivist
  
  I didn't filter shit on proprietary, was a different whole network.
  
  In conversation about a month ago permalink
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 05:29:20 JST broken god
  in reply to
  @ins0mniak @Owl @NonPlayableClown @dj @transgrammaractivist
  
  That's how it feels using P's hw. Lots of the noise gone.
  
  In conversation about a month ago permalink
- Embed this notice
  ins0mniak (ins0mniak@majestic12.airforce)'s status on Friday, 25-Oct-2024 05:29:20 JST ins0mniak
  in reply to
  @cvnt @transgrammaractivist @Owl @dj @NonPlayableClown I feel like I'm a fedi within a fedi these days lol.
  
  Sometimes ill respond to P and he's like "oh dude check out rest of the thread"
  
  I'm like brah I cant.
  
  Its a tradeoff . I get less gablin bullshit and more hangouts with people
  
  In conversation about a month ago permalink
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 06:27:05 JST broken god
  in reply to
  @ins0mniak @phnt @NonPlayableClown @Owl @dj @transgrammaractivist
  
  They're not even good at racism.
  
  In conversation about a month ago permalink
- Embed this notice
  ins0mniak (ins0mniak@majestic12.airforce)'s status on Friday, 25-Oct-2024 06:27:06 JST ins0mniak
  in reply to
  @phnt @transgrammaractivist @Owl @dj @NonPlayableClown The worst was after the last gab meltdown.
  
  They got this huge influx of new users that would just bombard every other post with their wingnat shit.
  
  In conversation about a month ago permalink
  
  broken god likes this.
- Embed this notice
  Phantasm (phnt@fluffytail.org)'s status on Friday, 25-Oct-2024 06:27:07 JST Phantasm
  in reply to
  @Owl @ins0mniak @transgrammaractivist @dj @NonPlayableClown I muted poa.st on Hitler's birthday because my TWKN was spammed by that and completely forgot about it for 3 weeks. A month later I finally realized that something was missing.
  In conversation about a month ago permalink
  Attachments
  1. Untitled attachment
- Embed this notice
  ins0mniak (ins0mniak@majestic12.airforce)'s status on Friday, 25-Oct-2024 06:29:40 JST ins0mniak
  in reply to
  @cvnt @phnt @transgrammaractivist @Owl @dj @NonPlayableClown If you're gonna do something do it right.
  
  In conversation about a month ago permalink
  
  broken god likes this.
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 06:33:06 JST broken god
  in reply to
  @phnt @NonPlayableClown @Owl @dj @ins0mniak @transgrammaractivist
  
  The Rothschilds didn't have to try very hard with some these losers.
  
  In conversation about a month ago permalink
- Embed this notice
  Phantasm (phnt@fluffytail.org)'s status on Friday, 25-Oct-2024 06:33:07 JST Phantasm
  in reply to
  @cvnt @ins0mniak @transgrammaractivist @Owl @dj @NonPlayableClown What do you expect from people that sit at their computer all day and post about jews while also spamming nigger every now and then because it's supposed to be funny.
  
  In conversation about a month ago permalink
  
  broken god likes this.
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 06:38:19 JST broken god
  in reply to
  @ins0mniak @NonPlayableClown @Owl @dj @phnt @transgrammaractivist
  
  Bruh, I repeatedly said we need to Saigon taxi the worthwhile out. They don't want to move, that's new and scary. It's why S2 and Styx both have Gab accounts and are absent here.
  
  I was too forgiving is my point. Some garbage should stay in the bin where you found it.
  
  In conversation about a month ago permalink
- Embed this notice
  ins0mniak (ins0mniak@majestic12.airforce)'s status on Friday, 25-Oct-2024 06:38:20 JST ins0mniak
  in reply to
  @cvnt @phnt @transgrammaractivist @Owl @dj @NonPlayableClown If they can't assimilate they have to go back.
  
  In conversation about a month ago permalink
- Embed this notice
  ins0mniak (ins0mniak@majestic12.airforce)'s status on Friday, 25-Oct-2024 06:42:08 JST ins0mniak
  in reply to
  @cvnt @phnt @transgrammaractivist @Owl @dj @NonPlayableClown Yeah I feel you on that.
  
  In conversation about a month ago permalink
  
  broken god likes this.
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 06:45:25 JST pistolero
  in reply to
  @cvnt @phnt @NonPlayableClown @Owl @dj @ins0mniak @transgrammaractivist
  
  > ask me how I know he doesn't test shit before pushing updates.
  
  "there isn't a Pleroma instance that exists which cannot handle the load on available hardware" still irks me because it means that the person that wrote it was ignoring the performance issues that had been reported in the bug tracker as well as in messages on fedi. (I don't think most people could have convinced Pleroma to stay up when subjected to FSE's load.) I guess nothing has changed since FSE's last merge with upstream.
  
  In conversation about a month ago permalink
  
  ✙ dcc :pedomustdie: :phear_slackware: and broken god like this.
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 06:46:51 JST broken god
  in reply to
  @p @NonPlayableClown @Owl @dj @ins0mniak @phnt @transgrammaractivist
  
  Imagine thinking an rpi4 was underpowered for your website, and the issue isn't your fucking website.
  
  In conversation about a month ago permalink
- Embed this notice
  (mint@ryona.agency)'s status on Friday, 25-Oct-2024 06:50:24 JST
  in reply to
  @p @phnt @cvnt @ins0mniak @transgrammaractivist @Owl @dj @NonPlayableClown In his defense, he's been a big help with identifying the root cause of performance issue (a bug in Oban that made it crash its queue processing tasks) that until that point only affected my instances and one other guy that made a bug report.
  
  In conversation about a month ago permalink
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 07:09:28 JST pistolero
  in reply to
  @cvnt @NonPlayableClown @Owl @dj @ins0mniak @phnt
  
  > Imagine thinking an rpi4 was underpowered for your website, and the issue isn't your fucking website.
  
  In this case, he was talking about maximum-size Frantech instances at the time: https://freespeechextremist.com/objects/508dc765-46de-4e28-adde-a8a6fd1d8ee0 . Granted, it's gotten better sometimes (worse sometimes) but breaking follows is a thing that shouldn't happen at any point on a release version.
  
  The bae.st media import is actually running on a CM-4 and the actual bottleneck is the disk and it's chugging but I just sort of took it as a given that this is something I have to fix. There was an instance running on a Switch for a while, and I'm sure you're aware of mint's antics. lain cares about that kind of platform, so it's nice that lain is around.
  In conversation about a month ago permalink
  Attachments
  1. Untitled attachment
  2. Untitled attachment
  , ✙ dcc :pedomustdie: :phear_slackware: and broken god like this.
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 07:11:02 JST broken god
  in reply to
  @p @NonPlayableClown @Owl @dj @ins0mniak @phnt
  
  I mean, I was specific about the release for that reason. I am trying my best to not just be discarding.
  
  In conversation about a month ago permalink
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 07:16:24 JST pistolero
  in reply to
  @mint @NonPlayableClown @Owl @cvnt @dj @ins0mniak @phnt Yeah? That's good to hear, maybe he cares about craftsmanship.
  
  In conversation about a month ago permalink
  
  and broken god like this.
- Embed this notice
  :blank: (i@declin.eu)'s status on Friday, 25-Oct-2024 07:21:29 JST :blank:
  in reply to
  @p @phnt @cvnt @ins0mniak @Owl @dj @NonPlayableClown it would also be nice if lain was around to actually make a 2.7.1 release like they said they should half a month ago
  
  In conversation about a month ago permalink
  
  and broken god like this.
- Embed this notice
  Phantasm (phnt@fluffytail.org)'s status on Friday, 25-Oct-2024 07:31:52 JST Phantasm
  in reply to
  @p @cvnt @ins0mniak @transgrammaractivist @Owl @dj @NonPlayableClown The main problem is that lain likely never expected to Pleroma grow this large to instances with hundreds of users. Something which would have influenced some of the design decisions. And that the developers don't run those active big instances.
  
  I don't remember what version FSE runs on (2.2.X I think), but I can say that at least things didn't get worse with releases from 2.5.0 to current develop (apart from maybe increased IO usage I have yet to investigate in 2.7.0). I heard that some of the expensive DB queries were improved recently. Feld also committed some fixes found with static analysis and that's about it.
  
  You can still run Pleroma on cheap hardware, it just requires a lot of know-how in optimizing Postgres and Linux. FluffyTail runs on BuyVMs $7 tier with the DB stored on a slab and it is yet to encounter a major performance issue after 1.5 years. Granted I'm the only user, so there isn't a lot of stress on the system.
  
  In conversation about a month ago permalink
  
  broken god likes this.
- Embed this notice
  Phantasm (phnt@fluffytail.org)'s status on Friday, 25-Oct-2024 07:33:09 JST Phantasm
  in reply to
  @i @cvnt @p @ins0mniak @Owl @dj @NonPlayableClown lain said he wants to make a new release recently. This or last week I think.
  
  In conversation about a month ago permalink
  
  broken god likes this.
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 09:24:27 JST pistolero
  in reply to
  @phnt @NonPlayableClown @Owl @cvnt @dj @ins0mniak @transgrammaractivist
  
  > The main problem is that lain likely never expected to Pleroma grow this large to instances with hundreds of users.
  
  Well, sure, I made that remark in the linked-to thing:
  
  > FSE is an edge case, but will not be forever. I think it is a good problem to have that scaling is becoming an issue, you don't wanna build super scalability into something that nobody ends up using, but it is the case that there are scaling issues that presently affect pleroma instances.
  
  And that's November 2020.
  
  > And that the developers don't run those active big instances.
  
  I offered perf datasets many times. Server logs, Postgres logs. At the time that I wrote that post, there was a Prometheus endpoint that was open to the public on every single instance, so an interested party could collect performance data on every live Pleroma instance; it closed in the release immediately after that post.
  
  I get it doesn't touch them and I get that the idea wasn't to run instances with this many users, but it's not number of users that introduce the scaling issues: it's number of activities.
  
  > I don't remember what version FSE runs on (2.2.X I think),
  
  It's modified and has fixes backported, but it is 2.2.2: http://demo.fedilist.com/instance/fsebugoutzone.org . (Still zero downtime! Everyone can suck my dick, I'm a goddamn genius hackerman.)
  
  > You can still run Pleroma on cheap hardware, it just requires a lot of know-how in optimizing Postgres and Linux.
  
  Well, a single-user one, following a few hundred people, I don't think you need much effort. At that level, concurrent users *do* start to matter.
  
  > FluffyTail runs on BuyVMs $7 tier with the DB stored on a slab and it is yet to encounter a major performance issue after 1.5 years.
  
  Oh, yeah, FSE started like that and I think we got to about a dozen people before I had to upgrade to whatever :francisco:'s next tier was.
  In conversation about a month ago permalink
  Attachments
  1. Domain not in remote thumbnail source whitelist: fsebugoutzone.org
    
    fsebugoutzone.org
    
    FSE temporary bugout zone until the new code is ready, but mostly a development instance, so it will not run like regular FSE: closed registrations (but if you had an account, your old username/password will work), I will shoot anything that annoys me while I am hacking (and if you are hoping for a warning shot, please do not annoy me until ammo prices drop), etc. Lots of things will be broken periodically because this is a development instance. Direct complaints to @p, or if you are a total dick, just #fediblock us based on rumors/assumptions without trying to reach out like you did with FSE. Full explanation here: https://blog.freespeechextremist.com/blog/update-and-roadmap.html
  broken god likes this.
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 09:35:27 JST pistolero
  in reply to
  @i @phnt @NonPlayableClown @Owl @cvnt @dj @ins0mniak If the problem with 2.7.0 was that basic shit was broken, do you really want them to rush 2.7.1?
  
  In conversation about a month ago permalink
  
  broken god likes this.
- Embed this notice
  :blank: (i@declin.eu)'s status on Friday, 25-Oct-2024 09:35:28 JST :blank:
  in reply to
  @phnt @cvnt @p @ins0mniak @Owl @dj @NonPlayableClown yes, but they keep talking more, releasing none
  In conversation about a month ago permalink
  Attachments
  1. Untitled attachment
    https://declin.eu/media/ae2cb712233a61fc2a914b49224b32bcbf6a0a72d6090af52ee2a6e22371fcc3.png
- Embed this notice
  RedTechEngineer (redtechengineer@fedi.lowpassfilter.link)'s status on Friday, 25-Oct-2024 10:06:40 JST RedTechEngineer
  in reply to
  @p @i @phnt @cvnt @ins0mniak @Owl @dj @NonPlayableClown 2.7.0.5 when
  
  In conversation about a month ago permalink
  
  broken god likes this.
- Embed this notice
  feld (feld@friedcheese.us)'s status on Friday, 25-Oct-2024 10:27:22 JST feld
  in reply to
  @cvnt @phnt @NonPlayableClown @Owl @dj @ins0mniak @transgrammaractivist I didn't break follows, I found a bug that existed for years and fixed it
  
  In conversation about a month ago permalink
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 10:28:34 JST broken god
  in reply to
  @feld @NonPlayableClown @Owl @ins0mniak @phnt @transgrammaractivist
  
  Even if it's not your fault I am going to shit on you. Call the FBI, this is a threat.
  
  In conversation about a month ago permalink
- Embed this notice
  broken god (cvnt@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 10:32:57 JST broken god
  in reply to
  @p @i @NonPlayableClown @Owl @dj @ins0mniak @phnt.
  
  akkomabox on azure, somehow Pasture is stuck selling it.
  
  In conversation about a month ago permalink
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 10:32:58 JST pistolero
  in reply to
  @i @NonPlayableClown @Owl @cvnt @dj @ins0mniak @phnt I don't think *another* fork is a good solution. A release engineer maybe, but it's their call.
  
  In conversation about a month ago permalink
- Embed this notice
  :blank: (i@declin.eu)'s status on Friday, 25-Oct-2024 10:33:00 JST :blank:
  in reply to
  @p @phnt @cvnt @ins0mniak @Owl @dj @NonPlayableClown making a release in the middle of rewriting the work queue was the stupid bit, not making a release a month after it's fixed, and weeks after people complained about it, isn't any better
  
  they could cherry pick that single commit change into 2.7.2 (2.7.1 was a pleroma-fe emoji picker bug fix release apparently) for all i care
  
  pleroma's codebase needs a hard forking, but with federation details relying on implementation edge cases not accidentally changing, it's hard to muster up the will power to care enough to go through with it
  
  In conversation about a month ago permalink
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 10:38:32 JST pistolero
  in reply to
  @cvnt @NonPlayableClown @Owl @dj @i @ins0mniak @phnt We're all screwed.
  seller_response.jpeg
  In conversation about a month ago permalink
  Attachments
  1. seller_response.jpeg
    https://fsebugoutzone.org/media/35414450-8671-4eed-b839-e1075b265cdd/seller_response.jpeg?name=seller_response.jpeg
  broken god likes this.
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Friday, 25-Oct-2024 10:39:08 JST pistolero
  in reply to
  @cvnt @NonPlayableClown @Owl @dj @i @ins0mniak @phnt Maybe not, I don't know. Falling asleep in my chair.
  saypizzatodrugs.png
  In conversation about a month ago permalink
  Attachments
  1. saypizzatodrugs.png
    https://fsebugoutzone.org/media/6fb514e8-29f2-4271-bd25-f5d47f5b2a1d/saypizzatodrugs.png?name=saypizzatodrugs.png
  Haelwenn /элвэн/ :triskell: and broken god like this.
- Embed this notice
  feld (feld@friedcheese.us)'s status on Friday, 25-Oct-2024 10:40:11 JST feld
  in reply to
  @p @cvnt @phnt @NonPlayableClown @Owl @dj @ins0mniak @transgrammaractivist Nobody proved there was an *Oban* bottleneck and still haven't.
  
  I'm always running my changes live on my instances. They were massively overpowered. Now I have a severely underpowered server and it's still fine.
  
  If I could reproduce reported issues it would be much easier to solve them but things generally just work for me.
  
  A ton of work has been put into correctness (hundreds of Dialyzer fixes) and tracking down elusive bugs and looking for optimizations like reducing JSON encode/decode work when we don't need to, avoiding excess queries, etc.
  
  I'm halfway done with an entire logging rewrite and telemetry integration which will make it even easier to identify bottlenecks.
  
  It's actually been going really great 🤷
  
  In conversation about a month ago permalink
- Embed this notice
  ins0mniak (ins0mniak@majestic12.airforce)'s status on Friday, 25-Oct-2024 10:41:36 JST ins0mniak
  in reply to
  @feld @phnt @cvnt @p @transgrammaractivist @Owl @NonPlayableClown
  
  In conversation about a month ago permalink
  
  broken god and feld like this.
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Saturday, 26-Oct-2024 00:05:57 JST pistolero
  in reply to
  @ins0mniak @feld @NonPlayableClown @Owl @cvnt @phnt @transgrammaractivist Bosoms.
  
  In conversation about a month ago permalink
  
  ✙ dcc :pedomustdie: :phear_slackware: likes this.
- Embed this notice
  feld (feld@friedcheese.us)'s status on Saturday, 26-Oct-2024 00:28:15 JST feld
  in reply to
  - pistolero
  @p
  
  > I mean, like I mentioned, the Prometheus endpoints were public at the time.
  
  Problem is that this data is useful for monitoring overall health of an instance but doesn't give enough granular information to track down a lot of issues. With the metrics/telemetry work I have in progress we'll be able to export more granular Pleroma-specific metrics that will help a lot.
  
  > The main bottleneck is the DB
  
  So often it's just badly configured Postgres. If your server has 4 cores and 4 GB of RAM you can't go use pgtune and tell it you want to run Postgres with 4 cores and 4GB. There's nothing leftover for the BEAM. You want at least 500MB-1GB dedicated to BEAM, more if your server has a lot of local users so it can handle memory allocation spikes.
  
  And then what else is running on your OS? That needs resources too. There isn't a good way to predict the right values for everyone. 😭 Like I said, it's running *great* on my little shitty thin client PC with old slow Intel J5005 cores and 4GB RAM. But I have an SSD for the storage and almost nothing else runs on the OS (FreeBSD). I'm counting a total of 65 processes before Pleroma, Postgres, and Nginx are running. Most Linux servers have way more services running by default. That really sucks when trying to make things run well on lower specced hardware.
  
  You also have to remember that BEAM is greedy and will intentionally hold the CPU longer than it needs because it wants to produce soft-realtime performance results. This needs to be tuned down on lower resource servers because BEAM itself will be preventing Postgres from doing productive work. It's just punching itself in the face then. Set these vm.args on any server that isn't massively overpowered:
  
  +sbwt none
  +sbwtdcpu none
  +sbwtdio none
  
  > using an entire URL for an index is costing a lot in disk I/O
  
  For the new Rich Media cache (link previews stored in the db so they're not constantly refetched) I hashed the URLs for the index for that same reason. Research showed a hash and the chosen index type were super optimal.
  
  Another thing I did was I noticed we were storing *way* too much data in Oban jobs. Like when you federated an activity we were taking the entire activity's JSON and storing it in the jobs. Imagine making a post with 100KB of content that needs to go to 1000 servers? Each delivery job in the table was HUGE. Now it's just the ID of the post and we do the JSON serialization at delivery time. Much better, lower resource usage overall, lower IO.
  
  Even better would be if we could serialize the JSON *once* for all deliveries but it's tricky because we gotta change the addressing for each delivery. Jason library has some features we might be able to leverage for this but it doesn't seem important to chase yet. Even easier might be to put placeholders in the JSON text, store it in memory, and then just use regex or cheaper string replacement to fill those fields at delivery time. Saves all that repeat JSON serialization work.
  
  Other things I've been doing:
  
  - making sure Oban jobs that have an error we should really treat as permanent are caught and don't allow the job to repeat. It's wasteful for us, rude to remote servers when we're fetching things
  
  - finding every possible blocker for rendering activities/timelines and making those things asynchronous. One of the most recent ones I found was with polls. They could stall rendering a page of the timeline if the poll wasn't refreshed in the last 5 mins or whatever. (and also... I'm pretty sure polls were still being refreshed AFTER the poll was closed 🤬)
  
  I want Pleroma to be the most polite Fedi server on the network. There are still some situations where it's far too chatty and sends requests to other servers that could be avoided, so I'm trying to plug them all. Each of these improvements lowers the resource usage on each server. Just gotta keep striving to make Pleroma do *less* work.
  
  I do have my own complaints about the whole Pleroma releases situation. I wish we were cutting releases like ... every couple weeks if not every month. But I don't make that call.
  
  In conversation about a month ago permalink
  
  likes this.
- Embed this notice
  pistolero (p@fsebugoutzone.org)'s status on Saturday, 26-Oct-2024 00:28:16 JST pistolero
  in reply to
  @feld @NonPlayableClown @Owl @cvnt @ins0mniak @phnt @transgrammaractivist
  
  > Nobody proved there was an *Oban* bottleneck and still haven't.
  
  Well, this was a remark years back. (It does still irk me.) Everything I know about the current Oban bug is second-hand, I am running what might be the only live Pleroma instance with no Gleason commits (happy coincidence; I was actually dodging another extremely expensive migration and then kicked off the other project, which meant I don't want to have to hit a moving target if I can avoid it, so I stopped pulling); at present, I backport a security fix (or just blacklist an endpoint) once in a while.
  
  Unless you mean the following thing, but I haven't run 2.7.0. I don't know what that bug is.
  
  > If I could reproduce reported issues it would be much easier to solve them but things generally just work for me.
  
  I mean, like I mentioned, the Prometheus endpoints were public at the time. You could see my bottlenecks. (I think that would be cool to reenable by default; they'd just need to stop having 1MB of data in them if people are gonna fetch them every 30s, because enough people doing that can saturate your pipe.)
  
  > A ton of work has been put into correctness (hundreds of Dialyzer fixes) and tracking down elusive bugs and looking for optimizations like reducing JSON encode/decode work when we don't need to, avoiding excess queries, etc.
  
  I'm not sure what the Dialyzer is (old codebase), but improvements are good to hear about. That kind of thing gets you a 5%, 10% bump to a single endpoint, though. The main bottleneck is the DB; some cleverness around refetching/expiration would get you some much larger performance gains, I think; using an entire URL for an index is costing a lot in disk I/O. There's a lot of stuff to do, just not much of it is low-hanging, I think.
  
  > It's actually been going really great 🤷
  
  :bigbosssalute: That is awesome to hear.
  
  In conversation about a month ago permalink

Public

Conversation

Notices

Feeds