- Joined
- Jun 17, 2000
- Messages
- 19,712
- Reaction score
- 31,139
I had posted this first a few days ago in the VIP Forum, but now that I have more information I decided to post this here.
After the first weekend of the season, I began researching exactly what a forum like ours really needs in terms of server resources in order to run efficiently even when 3000+ people are here using the board. I've spoken to the hosting company at length and have researched what some of the top messageboards on the internet use for a processor, SCSI hard drives, etc. and have come up with a solution that will eliminate the game day slow downs. This will be an expensive endeavor, but I know there has been some frustration since game one and I'm not willing to deal with this for the next 14-weeks. You should see a lightening fast board going forward once the transition is complete.
I will answer the number one question for those who think that there is an obvious solution, since I've seen this in several threads:
Q: Why can't you block guests on gameday from the board which seems like an obvious solution to the problem?
A: I can block them from accessing the board, but they're not blocked from the server. They still receive a message stating they have to register to view the board. This still requires DB queries, which doesn't solve the problem. We then receive over 100 registrations per hour, and they all login and stay anyway. Believe it or not a high percentage (almost 75% from what I tracked last Sunday) were Pats Fans who were either finding the board for the first time or were regular readers who simply didn't have an account.
Q: What is the problem, and can we do anything this weekend to make it run better until we switch next week?
A: Believe it or not, this is actually the number one issue: For those who use the gameday thread, please wait at least 30 seconds in-between trying to refresh the page. When hundreds of you are sitting there hitting refresh each second, you're performing over 1,000 queries per second which is why the board slows down so much during the game. In case no one noticed last weekend, as soon as the game was over the board speeded up within minutes, and the server stats confirmed this. So try and wait a little bit before clicking refresh. Once we have the new server you can click however much you want.
I know this is a pain and obviously we dealt with it again last weekend, which was necessary because I wasn't finished going over all the options and making sure that we had all the details worked out. Earlier this week I had final discussions with them, but decided on a couple of better resources to add in to make absolutely sure, and I have finalized exactly what we're going to be doing. So I have placed the order, but the way it looks right now we probably won't have it until Tuesday or Wednesday, and then they'll perform the migration around the end of this week, which works out well since we have the bye coming up.
I will be disabling all the server-intensive features of vBulletin tomorrow (Sunday) and will disable Guests from viewing more than a small number of threads to lighten the load, and this will be the last weekend we have an issue.
In the meantime bear with me and we'll get this problem eliminated, I promise. - Ian
After the first weekend of the season, I began researching exactly what a forum like ours really needs in terms of server resources in order to run efficiently even when 3000+ people are here using the board. I've spoken to the hosting company at length and have researched what some of the top messageboards on the internet use for a processor, SCSI hard drives, etc. and have come up with a solution that will eliminate the game day slow downs. This will be an expensive endeavor, but I know there has been some frustration since game one and I'm not willing to deal with this for the next 14-weeks. You should see a lightening fast board going forward once the transition is complete.
I will answer the number one question for those who think that there is an obvious solution, since I've seen this in several threads:
Q: Why can't you block guests on gameday from the board which seems like an obvious solution to the problem?
A: I can block them from accessing the board, but they're not blocked from the server. They still receive a message stating they have to register to view the board. This still requires DB queries, which doesn't solve the problem. We then receive over 100 registrations per hour, and they all login and stay anyway. Believe it or not a high percentage (almost 75% from what I tracked last Sunday) were Pats Fans who were either finding the board for the first time or were regular readers who simply didn't have an account.
Q: What is the problem, and can we do anything this weekend to make it run better until we switch next week?
A: Believe it or not, this is actually the number one issue: For those who use the gameday thread, please wait at least 30 seconds in-between trying to refresh the page. When hundreds of you are sitting there hitting refresh each second, you're performing over 1,000 queries per second which is why the board slows down so much during the game. In case no one noticed last weekend, as soon as the game was over the board speeded up within minutes, and the server stats confirmed this. So try and wait a little bit before clicking refresh. Once we have the new server you can click however much you want.
I know this is a pain and obviously we dealt with it again last weekend, which was necessary because I wasn't finished going over all the options and making sure that we had all the details worked out. Earlier this week I had final discussions with them, but decided on a couple of better resources to add in to make absolutely sure, and I have finalized exactly what we're going to be doing. So I have placed the order, but the way it looks right now we probably won't have it until Tuesday or Wednesday, and then they'll perform the migration around the end of this week, which works out well since we have the bye coming up.
I will be disabling all the server-intensive features of vBulletin tomorrow (Sunday) and will disable Guests from viewing more than a small number of threads to lighten the load, and this will be the last weekend we have an issue.
In the meantime bear with me and we'll get this problem eliminated, I promise. - Ian
Last edited: