View Full Version : is this thing going to crash in about an hour?
billm317
10-09-2007, 12:57 PM
just curious on how things have improved since the last time it crashed
ross11988
10-09-2007, 12:59 PM
lol good point
steph3n
10-09-2007, 12:59 PM
Everyone go to chat and it won't crash no need for play by play in the forums, and the chat is on a different server even if the forums go down you can feed your addiction.
kylejack
10-09-2007, 01:00 PM
They're going to be dumping the Search function shortly (DO IT NOW!) :) After they do that, I'm sure it will be fine.
billm317
10-09-2007, 01:02 PM
After they do that, I'm sure it will be fine.
That's a mighty steep assumption you just made :)
Anyone know if the new hardware got put into place like they were talking about a couple weeks ago?
steph3n
10-09-2007, 01:03 PM
That's a mighty steep assumption you just made :)
Anyone know if the new hardware got put into place like they were talking about a couple weeks ago?
not in place yet.
kylejack
10-09-2007, 01:06 PM
That's a mighty steep assumption you just made :)
It always fixes it after we crash it due to high traffic, and it generally stays up after they do that, too.
Problem is that it isn't the hardware. It is the db software. We should get Josh to pay a consultant from MySql to help get it stabilized. We can all pitch in a few bucks to pay for it.
CasualApathy
10-09-2007, 01:11 PM
Whats the link for the debate streaming video?
Bryan
10-09-2007, 01:21 PM
Problem is that it isn't the hardware. It is the db software. We should get Josh to pay a consultant from MySql to help get it stabilized. We can all pitch in a few bucks to pay for it.
We're running on 1GB of RAM, all reports show this is way low- the new server has 4GB which we can bump to 8 if needed.
Still I agree- we need to get a SQL expert.
JoshLowry
10-09-2007, 01:21 PM
Yes, it will crash around 410 users online.
Search was just turned off.
We have a larger server but have not made the transfer over to it just yet. The new one should be up sometime this week.
Mortikhi
10-09-2007, 01:21 PM
After the first crash, I would have found another host provider, but that's just me.
billm317
10-09-2007, 01:23 PM
After the first crash, I would have found another host provider, but that's just me.
it's not like people haven't offered this for free
but anyway lol
kylejack
10-09-2007, 01:23 PM
After the first crash, I would have found another host provider, but that's just me.
Regardless of host, VBulletin can only take so much abuse. They're working on getting a new box to host it on.
billm317
10-09-2007, 01:27 PM
We're running on 1GB of RAM,
just for fun... what speed processor is this running on?
We're running on 1GB of RAM, all reports show this is way low- the new server has 4GB which we can bump to 8 if needed.
Still I agree- we need to get a SQL expert.
Shortage of resources = slow, != crash.
billm317
10-09-2007, 01:32 PM
Shortage of resources = slow, != crash.
crash can also mean several things
i have a feeling that term gets used rather loosely
kylejack
10-09-2007, 01:32 PM
Shortage of resources = slow, != crash.
If all the SQL queries can't be processed, it certainly can result in a crash.
Ninja Homer
10-09-2007, 01:32 PM
We're running on 1GB of RAM, all reports show this is way low- the new server has 4GB which we can bump to 8 if needed.
Still I agree- we need to get a SQL expert.
I don't know what you have for rack space in the data center you're in, or even if these are your own machines, but you should be able to put the web server on one machine, and the database on the other and vastly improve performance. Bumping up to the better server should do it for now though. :)
If all the SQL queries can't be processed, it certainly can result in a crash.
It will result in a sql timeout, not a crash. MySQL is corrupting the db flat files, which can be nothing but buggy db software.
billm317
10-10-2007, 09:10 AM
just for fun... what speed processor is this running on?
billm317
10-10-2007, 09:15 AM
It will result in a sql timeout, not a crash. MySQL is corrupting the db flat files, which can be nothing but buggy db software.
I find it very hard to believe that vbulletin + mysql can only handle 410 concurrent users. Those are both, I dunno, pretty popular pieces of software.
kylejack
10-10-2007, 09:17 AM
I find it very hard to believe that vbulletin + mysql can only handle 410 concurrent users. Those are both, I dunno, pretty popular pieces of software.
Exactly. Any kind of processor strain can crash a computer, particularly on flaky hardware, hence the hardware upgrade. Something Awful uses a bastardized version of MySql and VBulletin, so we know it can support a lot of users.
Exactly. Any kind of processor strain can crash a computer, particularly on flaky hardware, hence the hardware upgrade. Something Awful uses a bastardized version of MySql and VBulletin, so we know it can support a lot of users.
Flaky hardware can indeed crash even well written software. But hardware problems will show up sporatically even under light load.
As far as the db file corruption, slow processors cannot make this happen with well written software. Otherwise banking systems would have crashed every 10 seconds back when their db software was running on 486 processors.
GET A MYSQL CONSULTANT!
:D
jmunjr
10-10-2007, 09:33 AM
So have you guys enabled MySQL Query Cache and properly configured it?
Another thing you guys could do is use PostgreSQL, which is more industrial-strength.
Powered by vBulletin® Version 4.2.3 Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.