Trouble paying bills?
- Thread starter Gwyn
- Start date
not a billing issue
There was a spike this afternoon where 300 people were on the site at the same time and the server overloaded. It looks like Ali's journal got a new link a major site.
Anyhoo, my ISP shut me down until I could change some settings. I should be able to handle that kind of traffic now. We'll see tomorrow if I'm ok.
There was a spike this afternoon where 300 people were on the site at the same time and the server overloaded. It looks like Ali's journal got a new link a major site.
Anyhoo, my ISP shut me down until I could change some settings. I should be able to handle that kind of traffic now. We'll see tomorrow if I'm ok.
I've been getting a lot of "The server is too busy at the moment. Please try again later" messages. I realize this is a normal message that people get when the bandwidth reaches the cap but I was curious what the cap is set at.......Also is it a dedicated server? I'm not trying to be nosy, I'm just curious because I might know of some better options.
..
Andy
It's cool that there's at least a message so people don't think the site is down for no reason......
::::::::The capped bandwidth option works exactly how it sounds. As a customer you choose a bandwidth level you want to guarantee you never exceed at any point in time. If the requests to your server platform exceed that level our routers will drop the end users TCP/IP requests. This could result in slowness and in extreme circumstances complete unresponsiveness to the end user. of course like all technology there is a trade off. In this case the trade off is a potential for decreased performance. The benefit is the protection that you will not incur an abnormally high bill as a result of a hacked machine or some other issue forcing additional bandwidth utilization. Once the end user requests fall below the cap, normal operation will resume automatically.::::::
..
Andy
It's cool that there's at least a message so people don't think the site is down for no reason......
::::::::The capped bandwidth option works exactly how it sounds. As a customer you choose a bandwidth level you want to guarantee you never exceed at any point in time. If the requests to your server platform exceed that level our routers will drop the end users TCP/IP requests. This could result in slowness and in extreme circumstances complete unresponsiveness to the end user. of course like all technology there is a trade off. In this case the trade off is a potential for decreased performance. The benefit is the protection that you will not incur an abnormally high bill as a result of a hacked machine or some other issue forcing additional bandwidth utilization. Once the end user requests fall below the cap, normal operation will resume automatically.::::::
Last edited:
It's not a bandwidth issue. It's about too many people being connected to the same server using too many processes. There's something called "server load". When things are normal, it should be around 2-4. When it starts reaching 5, there could be a problem. The other day, I had a spike of 300 people and the server load reached 50, very bad.
So... I changed a couple of things in the background processes, and the load seems to be under control. The other thing I changed was to put a maximum load on the server. Now if I get a spike of 100's of people, and the server load rises above a certain number, vbulletin starts sending out the "server busy" message. If you get that message, wait for 30 seconds and try again. Odds are you will get the page to load on the 2nd or 3rd try.
So... I changed a couple of things in the background processes, and the load seems to be under control. The other thing I changed was to put a maximum load on the server. Now if I get a spike of 100's of people, and the server load rises above a certain number, vbulletin starts sending out the "server busy" message. If you get that message, wait for 30 seconds and try again. Odds are you will get the page to load on the 2nd or 3rd try.