Conversation

Notices

1. Embed this notice
   Tosti ? (tost@mk.toast.cafe)'s status on Tuesday, 31-Jan-2023 06:15:35 JST Tosti ?

   • Puniko ?

   @puniko@mk.absturztau.be if you want to experiment more, you can try setting deliverJobConcurrency to 512 (on top of deliverJobPerSec being -1)
   do be a bit careful though since it's IO-sensitive (so you might need to lower it a bit based on your workers, you can easily tell based on whether or not you get a bunch of timeouts in logs after a delete)

   • Embed this notice
     Puniko ? (puniko@mk.absturztau.be)'s status on Tuesday, 31-Jan-2023 06:15:34 JST Puniko ?

     in reply to

     @tost@mk.toast.cafe i know about deliverJobConcurrency. used that before a bunch, so can set it as a last resort. thanks tho.
     
     probably will raise the worker count this weekend first and see how that goes

   • Embed this notice
     Tosti ? (tost@mk.toast.cafe)'s status on Tuesday, 31-Jan-2023 06:25:47 JST Tosti ?

     in reply to

     • Puniko ?

     @puniko@mk.absturztau.be it's mostly IO-bound so worker count shouldn't change that much

     Puniko ? likes this.