The traffic stopped a few hours back, from all IPs at once. Definitely seems to have been some sort of deliberate action.
lodion
joined 2 years ago
MODERATOR OF
The unusual traffic all appeared to be coming from one location on the internet, with the same user agent string. Any traffic from that network will now receive a captcha from Cloudflare. I'm not aware of any lemmy instances hosted there, but will keep an eye on things.
For some context, CPU usage jumped when the traffic started... and dropped after the block was applied:
It sure doesn't feel like autumn so far
Not sure how I should feel that the bubble I live in seems far more accepting and empathy towards asylum seekers.
I don't think the people I live/work/socialise with are particularly extreme... but according to this we're collectively not representative of wider Australian views.
I choose to believe their sampling was flawed and somehow only sampled the worst of us.
If you're posting as an uninvolved third party about an event you're interested in, it's not an ad.
As for spam, if you post a ridiculous volume about such events it could be construed as spamming. So long as you're manually posting this shouldn't an issue.
Basically, don't be trying to sell anything or abusing the AZ site.
Don't get me wrong, I'm happy you posted this. If there are unvoiced concerns or issues, here is a good place to discuss them.
I'm not as active on lemmy as I'd like, so I'm likely not aware of issues unless they're raised somewhere like this.
For potential meta issues such as age verification, I'll be seeking input from the community when they arise and information around them is known and understood.
The volume of activity from LW reduced, and it also looks like they made some config changes on their side... at a guess more federation worker processes, allowing an almost constant stream of activity to be sent to AZ.
When the LW lag issue was previously discussed, my main constraint was (and still is) time. Longer term it would have been a financial concern.
Either way, the issue has cleared up now due to a number of factors, none of which required time or finances on our part. I call that a win.
Worth noting, LW have still not upgraded their instance to the version that introduced multiple sending threads to a remote instance. If their volume of traffic were to increase substantially again, we could "lag" again.
I'm happy to hear feedback, but tbh you should think of AZ as a benevolent dictatorship rather than a democracy. So the analogy to a company AGM isn't quite right 😃
Sure.
Its been 6 months or so... figure its time for another of these. Keep in mind there have been some major config changes in the last week, which has resulted in the oddities below.
Graphs below cover 2 months, except Cloudflare which only goes to 30 days on free accounts.
CPU:
Memory:
Network:
Storage:
Cloudflare caching:
Comments: The server is still happily chugging along. Looking even happier now that I've properly migrated pict-rs to its integrated object storage config, rather than the bodged up setup.
RAM/CPU are all fine. Storage use is growing slowly as various databases grow. Still a long way from needing to purge old posts, if ever.
Cloudflare is saving less traffic these days, since Lemmy added support to proxy all images. Not a concern, well under the bandwidth cap for the server.
As usual feel free to ask any questions.
Its been a little while since I posted stuff :)
CPU:
Memory:
Network:
Storage:
Cloudflare caching:
Comments:
Not much has changed in quite a while. I still have a cron-job running to restart Lemmy every day due to memory leaks, hopefully this improves with future updates. Outside of that, CPU, memory and network usage are fine.
Object storage usage is growing steadily, but we're a long way from paying more than the monthly minimum Wasabi fee.
view more: next ›
And for anyone curious... blue line is traffic from a country we don't normally see much traffic from. The unusual spike, then drop when I blocked the specific sources: