Conversation

Notices

1. Embed this notice
   pwm (pwm@crlf.ninja)'s status on Monday, 29-Apr-2024 05:32:03 JST pwm
   Have I mentioned that I HATE the pleroma db lately?
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 29-Apr-2024 05:32:02 JST 

     in reply to
     @pwm Who doesn't?
   • Embed this notice
     🍔fat fuck🍔 (road to sick cunt) (not_benis@cawfee.club)'s status on Monday, 29-Apr-2024 05:37:23 JST 🍔fat fuck🍔 (road to sick cunt)

     in reply to

     • 
     @mint @pwm my thoughts exactly
      likes this.
   • Embed this notice
     pwm (pwm@crlf.ninja)'s status on Monday, 29-Apr-2024 05:58:14 JST pwm

     in reply to

     • 
     @mint I guess I could manually create the index I need but sheesh
     query goes from instantaneous to 20s just from adding an order by in order to paginate on the client side
      likes this.
   • Embed this notice
      (mint@ryona.agency)'s status on Monday, 29-Apr-2024 05:59:22 JST 

     in reply to
     @pwm Are you trying to optimize pleromer itself or making something separate that grabs data from its DB directly?
   • Embed this notice
     pwm (pwm@crlf.ninja)'s status on Monday, 29-Apr-2024 08:16:00 JST pwm

     in reply to

     • 
     @mint I was pulling post text out of the db for a separate application, see dsmc logs.
     Just yanking posts out is fast but not deterministic, which I need in order to paginate through query results in the client program, which I'm doing to not pull 64000 posts in one go.
     I'm not sure if I shouldn't just suck it up, technically I already did what I wanted, it was just too slow for me to be satisfied.
      likes this.