https://grafana.lem.rocks/d/bdid38k9p0t1cf/federation-health-single-instance-overview?orgId=1&var-instance=lemmy.world&var-remote_instance=aussie.zone

Parallel sending of federated activities to other instances. This can be especially useful for instances on the other side of the world, where latency introduces serious bottlenecks when only sending one activity at a time. A few instances have already been using intermediate software to batch activities together, which is not standard ActivityPub behavior, but it allows them to eliminate most of the delays introduced by latency. This mostly affects instances in Australia and New Zealand, but we’ve also seen federation delays with instances in US from time to time. This will likely not be enabled immediately after the upgrade, but we’re planning to enable this shortly after.

https://lemmy.world/post/23471887

  • Die4Ever
    link
    fedilink
    English
    arrow-up
    7
    ·
    edit-2
    1 day ago

    if the requests are all serialized, if the ping time is like 300ms, and if each request takes like 100ms of CPU time

    that means you only need 648,000 actions in queue to equal 3 days

    when you consider that even upvotes/downvotes of posts/comments count as actions, I could see it happening

    but the queue isn’t completely serialized anymore, so maybe this number is still a bit unbelievable (EDIT: seems like LW has not yet enabled the feature for parallel sending)

    • Alphane Moon@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 day ago

      A single action cannot take 100 ms of CPU time. This does not sound realistic.

      And why is this with aussie.zone only? This would be all instances, no?

      • Rimu@piefed.social
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        20 hours ago

        Recording a vote from an already-known account is way less than 100 ms, yes. Usually it’s less than 100 ms but sometimes it can be several seconds.

        When an activity is received the cryptographic signature on it needs to be checked and that means sending a network request to the creator’s instance to retrieve the creator’s public key (and profile pic, and cover pic each of which are more network requests. Then resize and store those images).

        Images in posts need to be downloaded, resized, scanned for objectionable material, etc.

        Every network request is quite unpredictable as many instances are overloaded or poorly configured.

      • Otter@lemmy.ca
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 day ago

        Aussie.zone might be the most extreme case, since its physical location is the farthest away from the largest Lemmy instance