No Bonus Ball live stream???

My ignorance -- how would a couple hundred people cause thousands of requests per second?

I'm not sure if you used the stream. But when it was out, I was able to click on the video and refresh the stream. I was able to do this 10-15 times in a couple of seconds. 10 x 300 people and you've got 3000 requests per second. (this is a bit dramatic, but gives you an idea of how it can happen) You know that there are many people who just sat there pressing the refresh button constantly for minutes. You're talking about a crazy number of requests to the server in a very short period of time.
 
Last edited:
My ignorance -- how would a couple hundred people cause thousands of requests per second?

One person clicks refresh...doesnt work...ten seconds later clicks it again. Rinse, repeat multiply x 200-400 over a 90 minute time span. I bet on a graph the traffic for the website is nice and flat with a GIANT spike.
 
I don't know the streaming - bandwith industry...so is this possible/probable or a lame excuse for a terrible stream that should have been tested many times before going live with it..Industry guys..Justin, Mark..can any of you confirm?

I would also guess, that because they are trusting the people who built this site to tell them what is going on. That they are getting a tech translated explanation and possibly a distortion of the reality of the situation. Your site doesn't get shut off like that unless you've automatically triggered some kind of Denial of Service protection. Which is going to turn out to be a design flaw. I'm just guessing here, but the guess comes from lots of experience.
 
I'm not sure if you used the stream. But when it was out, I was able to click on the video and refresh the stream. I was able to do this 10-15 times in a couple of seconds. 10 x 300 people and you've got 3000 requests per second. (this is a bit dramatic, but gives you an idea of how it can happen) You know that there are many people who just sat there pressing the refresh button constantly for minutes. You're talking about a crazy number of requests to the server in a very short period of time.

Guess I just can't imagine anyone pressing a refresh key 10-15 times per second.
 
How about an effing announcement to let us know if they are trying to finish the second half tonight???
 
The only thing that sucked worse than the stream was the game itself. I see BB as the bastardized love child of snooker, one pocket, and straight pool.
 
One person clicks refresh...doesnt work...ten seconds later clicks it again. Rinse, repeat multiply x 200-400 over a 90 minute time span. I bet on a graph the traffic for the website is nice and flat with a GIANT spike.

At Large is a stickler for accuracy in numbers, almost OCD about it.

What he means is, how can a hundred people cause more than 100 requests per second?

Assuming that a person takes at least 1 second to hit the refresh button and see the results before hitting it again it's not realistic to think that it's more than one request per person per second.
 
Guess I just can't imagine anyone pressing a refresh key 10-15 times per second.

I was being a bit hyperbolic, that may be excessive. But see how many times you can click your mouse in a second. There was nothing rate-limiting the amount of refreshes I could send out. So it was basically as fast as you can click your mouse.
 
I bet on a graph the traffic for the website is nice and flat with a GIANT spike.

True. But surely, that giant spike didn't last 3 hours. The problems were there before the stream even started. There must have been other issues...

Much respect,

-Blake
 
Well, years from now when Bonus Ball has Pac-Manned all other forms of pocket billiards, we'll be sitting with our grand children telling them about the night the pro game was officially introduced to the world.
 
True. But surely, that giant spike didn't last 3 hours. The problems were there before the stream even started. There must have been other issues...

Much respect,

-Blake

What I'm concluding based on what these guys are saying is this. The service provider they used for the stream wasn't up to snuff to handle the traffic, which caused all the lag. In response to the lag, viewers started hammering their refresh button over and over which then caused the website to crash.

That's my laymens understanding of it anyways.
 
I want to know if there is any chance I can view the second half tonight.

"Today's match will be archived for later viewing." So said they (WPBL) on Facebook, apparently. I'd bet that won't be within the next couple of hours, though.
 
New york won all of the singles matches.Final score was 15 -2 New York.
Nevel scored the first 30-0 win over Daulton.
 
Back
Top