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.
@Zagorath@aussie.zone @Nath@aussie.zone @lodion@aussie.zone , we’re trying our best to use non-LW communities
And you know what? I don’t feel like I’m missing anything. Lots of posts and comments to keep me busy for hours.
Ironically, the whole Lemmy activity makes it to you, just three days later
How is that ironic?
maybe not irony but it is funny op said i don’t feel like i’m missing anything! and it turns out they’re not it’s just delayed
True! Just outdated
What does this mean? Does it mean that a post from LW needs 2.98 days to appear on aussie.zone ?
Yup, exactly so. I’ll often notice a reply to one of my comments from a LW user will only show up in my inbox about 3 days later.
i don’t know if there’s any prioritising of types of actions, eg. posts are given higher priority than comments which is higher than up/down votes but when I made posts on lemmy.world I’d get an initial wave of upvotes from other instances and then like 12 hours later a lot of upvotes from lemmy.world users
Is this how long it takes for posts to federate? Why would it be so long?
I thought after lw upgraded the delays would go down :|
It should have. The backend added parallel syncing since a few versions back. By all accounts it should be going down.
The final bullet point of https://lemmy.world/post/23471887 suggests that that feature may not have been enabled yet.
That would be very unresonable imho. It’s the most important feature for them.
Perhaps they wanted to assess as few changes as possible simultaneously before turning on any optional features. I would imagine they will get to it fairly quickly.
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.
FYI @mesamunefire@lemmy.world , and why I now try to use !fediverse@lemmy.zip rather than the LW version
Any idea how aussie.zone is hosted? Syncing can become bottlenecked as instances grow and discover more communities. If they’re using a remote host they may need to upgrade or adjust their setup to hold sync with the larger instances.
Now 3.79
I know 😔
These are great charts, are these from the standard Prometheus endpoints in Lemmy? What queries do you use?
they’re using my federation exporter as data source.
it’s just scraping the federation api every 5 min for each included instance and then visualizing that.
Thank you! I’m going to set this up for my instance!
@Nothing4You@programming.dev is the owner of those dashboards