UPDATE: I found out the cause of an extremely esoteric bug / issue with the Pushshift API. Once every 10 or so seconds, the main Verizon router will take 5+ seconds to respond to simple pings. Resetting the router fixes the issue for another 24-36 hours, but eventually it will
Conversation
Replying to
encounter this really weird bug. My guess is that the volume of traffic going through it is causing some type of bug to manifest.
I will be looking into getting a new router from Verizon or checking if there is a firmware update for the existing one.
1
1
Essentially what this bug does is cause the API to get "stuck" with a batch of requests every 10 or so seconds so there are constant latency spikes that cause the cluster to get a little out of whack. (yes, this is accurate technical jargon).
1
1
To put it another way, imagine if I asked you to multiple two numbers and I asked you every couple of seconds for the product of two numbers. Then suddenly you didn't hear any requests from me and then suddenly I asked you for the answer to 10-20 products all at once.
1
This Tweet was deleted by the Tweet author. Learn more
Replying to
I was actually in the middle of an Overwatch game and every ten seconds, my game would get all out of whack. I then started pinging the main router and sure enough, once every ten seconds, it would take 5-6 seconds to respond. So that would affect every API behind the router.
1
Show replies