Conversation

Notices

1.  (mint@ryona.agency)'s status on Saturday, 25-May-2024 05:45:23 JST 
   The repack is still ongoing, but I feel it's going to be over soon.
   • :blank: (i@declin.eu)'s status on Saturday, 25-May-2024 05:53:50 JST :blank:

     in reply to
     @mint starting to think i need to turn off autovacuums
      and † top dog :pedomustdie: like this.
   •  (mint@ryona.agency)'s status on Saturday, 25-May-2024 05:57:27 JST 

     in reply to

     • :blank:
     @i Maybe that's what was fucking up salon and nukie's instance. But agency never outright crashed despite being on the same server as one of them, so I doubt that, likely just I/O queue getting constipated. And with boymoder I think I fixed it with by changing postgres config to pgtune's HDD profile.
   •  (mint@ryona.agency)'s status on Saturday, 25-May-2024 06:15:39 JST 

     in reply to

     • :blank:
     @i Or maybe it is suspect after all, just finished repack but still getting 500s as the autovacuum kicked in right at the end.
     Screenshot_20240525_001449.png
   •  (mint@ryona.agency)'s status on Saturday, 25-May-2024 06:17:10 JST 

     in reply to

     • :blank:
     @i And it just finished, so I guess it wasn't something critical.
   •  (mint@ryona.agency)'s status on Saturday, 25-May-2024 06:24:25 JST 

     in reply to

     • :blank:
     @i From left to right, agency and salon. For some reason agency's object table isn't included despite the fact it ran on it just now.
     Screenshot_20240525_002219.png
     Screenshot_20240525_002238.png
     † top dog :pedomustdie: likes this.
   • :blank: (i@declin.eu)'s status on Saturday, 25-May-2024 06:24:26 JST :blank:

     in reply to
     @mint do wonder how bad your churn is, sick of tuning postgres and seeing no changes