Oh I know the host provider isn't running a SCSI system for them as it's TOOOO expensive to build AND maintain. They all put in cheap stuff to get the most bang for the buck.
But if you co-locate or are allowed to build your own then it would be better to have the SCSI setup. For SATA something like this is much better than what comes on the motherboards: AMCC 3Ware 9650SE http://www.3ware.com/products/serial_ata2-9650.asp
Hey I speced out a server for work to handle 5,000 transactions a day and it was not cheap. HP was about $37K and dell was about $25K not including the fail over system which is smaller and cheaper. Awesome system though.
Express Hosting
"We are the official hosting company of UBB.threads. Ask us about our free migration services to migrate your UBB.threads installation."
#173481 - 01/14/0705:01 AMRe: Server Crashing
[Re: ntdoc]
[...] On the UBB side we have 25,000 members and 400 forums, which I believe makes us one of the largest Windows installs. [...] We have a gig of RAM and oodles of disk space. The server is usually only 20% busy so it's not maxing out the processor.
A single gig of RAM for such a huge site . If you are sure the reason for crashing is not a hardware failure or such, the first thing I would do is to add more RAM. Configure MySQL to hold all indexes into RAM to relieve hd load.
Well something is wrong with your forums, your ubb=online page is doing 41 queries every single time it's viewed, which leads me to believe it's rebuilding the cache every time that page is viewed. That could easily bring down a server. I don't know exactly what could cause that, but will let Rick work with my observation
Registered: 06/05/06
Posts: 14994
Loc: Portland, OR; USA
Offhand I'd say to check the portal page module cache and ensure things are set to 15minutes or so (at least 5); I'd highly advise against using a low number on such a large forum...
The disks are 7200RPM SATA drives. I will ask about faster disks.
This is a dedicated machine that is solely mine. The three standard event logs do not show any problems before the crash. I remote terminal into the machine so I can do whatever I want to it. I manage it and install the software myself. Normally it runs at very low processor usage and reasonable memory usage. When it crashes, I can't log in of course Then when it reboots everything seems fine and the log files don't report any problems before the crash. So it's been very hard to troubleshoot this. We had hoped it was a hardware issue with the previous disk, but apparently that was not the case.
A single gig of RAM for such a huge site . If you are sure the reason for crashing is not a hardware failure or such, the first thing I would do is to add more RAM. Configure MySQL to hold all indexes into RAM to relieve hd load.
Actually I just looked at the task manager to check, it's barely using half the RAM. That has never seemed an issue to me. If I go the route of tossing all indices into RAM, would that really take up the other 500mb?
. If you are sure the reason for crashing is not a hardware failure or such, the first thing I would do is to add more RAM. Configure MySQL to hold all indexes into RAM to relieve hd load.
##
Then when it reboots everything seems fine and the log files don't report any problems before the crash. So it's been very hard to troubleshoot this. We had hoped it was a hardware issue with the previous disk, but apparently that was not the case.
Previous Topic
Index
