ECI website is overloaded as we're only a few thousand signatures away
ECI website is overloaded as we're only a few thousand signatures away
Just hopped in to check and it looks like we're effectively DDoSing the Petition site by refreshing.
You can either join the watch party on the official discord, or use some other tracker website to see the numbers get updated to help alleviate the traffic so that more people can sign.
You're viewing a single thread.
@QuadratureSurfer @skg looking at the code of the progress tracker, the tracker website makes direct requests to ECI every 3 seconds without even waiting for the previous requests to finish{0}.
The large number of people keeping this tracker open could very well be the cause of the overload:
https://github.com/Alex1337F/StopKillingGamesTracker/issues/25Closing the progress tracker and maybe reducing its exposure a wee bit until it's fixed sounds like a good idea :blobcateyes:
Maybe the team behind ECI should have expected this kind of load, sure, but it's what we have today and it'd be a shame to lose the initiative to this :blobcatfacepalm:
edit: oops, looks like Lemmy misinterpreted my notation for "footnote links" out of square brackets and rendered this post in a broken way, let's see if curlies help
edit²: there is a PR that intends to stop new update requests from firing when an earlier request is unfinished: https://github.com/Alex1337F/StopKillingGamesTracker/pull/26 — which should help *somewhat*
{0}: https://github.com/Alex1337F/StopKillingGamesTracker/blob/master/main.js#L972-L973
Is it making those requests per user, or making them once and then sharing the results with all users?
@QuadratureSurfer best I can tell, per every instance of the page open. So roughly per user.
The requests are made straight from viewers' browsers to ECI.
Oof, that's not good. Thanks for the heads-up!
Definitely a better idea to join a watch party then and watch someone else stream it live.
Yikes, that doesn't scale well!