Conversation

Notices

1.  (mint@ryona.agency)'s status on Friday, 26-Apr-2024 07:34:01 JST 

   • Yukkuri
   @iamtakingiteasy A topic of pleromer DB optimizations got brought up again, and since you have around the same amount of relays you're subscribed to as me, I wonder how bloated you activity table by their announces is.
   select data->>'type', count(data->>'type') as count from activities group by data->>'type' order by count desc;
   • Yukkuri (iamtakingiteasy@eientei.org)'s status on Friday, 26-Apr-2024 16:57:23 JST Yukkuri

     in reply to

     @mint

     ?column? | count ------------+---------- Create | 31829515 Announce | 26433161 EmojiReact | 7229597 Like | 6665429 Update | 690690 Delete | 529471 Undo | 378142 Listen | 38424 Follow | 12465 Accept | 10933 Remove | 8458 Add | 4843 Block | 2285 Reject | 564 Flag | 363 Move | 101 Note | 5 (17 rows)
      likes this.
   •  (mint@ryona.agency)'s status on Friday, 26-Apr-2024 17:35:00 JST 

     in reply to

     • Yukkuri
     @iamtakingiteasy 35% of activities are announces, out of which a good portion likely is going to come from relays. Had the same situation and managed to decrease CPU consumption by slimming dowh the database by removing them. See if this improves performance and longevity.
     https://gitgud.io/ryonagency/pleroma/-/blob/ryona-dev/lib/pleroma/web/activity_pub/mrf/relay_optimization.ex
     https://ryona.agency/objects/aa269a40-cfae-4a87-86de-8e63771649f8
     https://ryona.agency/objects/487aa4d3-82f9-4d6d-adb1-fb306fed04b4
   • Yukkuri (iamtakingiteasy@eientei.org)'s status on Saturday, 27-Apr-2024 00:51:27 JST Yukkuri

     in reply to
     @mint Thanks, I'll keep it in mind, but CPU consumption isn't an issue for Eientei yet, nor is database size (for now). Also for MRF maybe it's better to ignore an activity rather than reject it, to avoid some implementations getting stuck in redelivery loop.
      likes this.
   •  (mint@ryona.agency)'s status on Saturday, 27-Apr-2024 00:53:51 JST 

     in reply to

     • Yukkuri
     @iamtakingiteasy Pleb said the same, I'm not aware if there's even an option besides :ok and :reject, and since Pleroma returns "ok" on inbox endpoint even if the activity is rejected, it shouldn't matter. fetch_object_from_id also checks if there's an object in database before fetching as well.
   • Yukkuri (iamtakingiteasy@eientei.org)'s status on Saturday, 27-Apr-2024 09:13:37 JST Yukkuri

     in reply to
     @mint There isn't in upstream, but you can add something like :ignore in common pipeline: https://gitlab.eientei.org/eientei/pleroma/-/blob/eientei/lib/pleroma/web/activity_pub/pipeline.ex?ref_type=heads&blame=1#L55 and then use it in MRF. IIRC at least for some time :reject were causing 4xx response. Maybe it isn't the case any more and this hack is not needed now.
      likes this.
   • :blank: (i@declin.eu)'s status on Saturday, 27-Apr-2024 09:13:50 JST :blank:

     in reply to

     • Yukkuri
     @iamtakingiteasy @mint thanks for the reminder of this, remembered vaguely someone made the :ignore but was confused when i didn't find it anywhere else after
      likes this.