Getting a new server, suggestions to handle these specs?

[bobbleheadR2D2]

Getting a new server, suggestions to handle these specs?

What level of server do you suggest to handle the below.

AKA, processor, ram, OS, and if you really want to get crazy, optimization specs for PHP and MYSQL settings.

30+ Domains - most with little to average average activity

2 or so VERY active - MYSQL PHP heavy

PHP/MYSQL heavily used, PHP on almost every site.

PHP includes used on many sites, pulling flat file info and
header/footer/sidebar files into a main page.

Run 2+ Vbulletin Message Boards, HEAVILY modified above and beyond core installations

Mod Rewrite via .htaccess used heavily

Sites usually graphic intensive on top of all PHP/MYSQL needs

Some sites serve large static files such as MP3s and MPEGS, rushed at times
when new content added.

Need to serve MYSQL driven board systems (Vbulletin) with 1000+ users accessing large static files such as JPEGS, MP3s, MPEGS THROUGH the board system, via attachments and direct links to server files.

So, what do you all suggest to handle such a set up?

[ChrisLM2001]

PHP includes used on many sites, pulling flat file info and
header/footer/sidebar files into a main page.

That alone ups your requirements! Flat file serving can reduce a server into a crawl fest. :(

What your after is a web hosting setup, and that's different than a vB forum setup. You'd be needing more than one server, and other hardware. So you're looking at a $500+/mon bill with all those requirements -- as it'll be at least 1 mysql server (4+GB memory) and 1 web frontend server (2GB memory). With 2x1000 member communities and the above, look at dual opteron with 8+GB for the mysql, and at least 3 web frontends, load balancer, offsite backup server, and hardware firewall (as that big of a community will attract wannabe hackers).

Chris

[bobbleheadR2D2]

See here is the thing tho,

On my current setup, I was using PHP-Nukes, and a VB add-on front end (good one) to power "front pages" on several sites.

This basically crashed the server whenever users got beyond 250 on either.

When I switched to the flat file systems for news delivery, crashes decreased significantly.

Only when my VB users online reach over 250/300 does the server slow, and then, crash.

Ive found that if we attach "hot" images or files as attachments to boards (essential for front page news deilvery via any VB portal), that kills the server as well. And this is with 300 users online. This happens even now when the boards get hot with discussion on a topic or image, not connected to the main pages.

I wont have 1000 online consistently, BUT, I want the ability to handle that.

And, I would move away from any flat file system if it meant speed up, just that is opposite what Ive experience to be true to this point.

Could you run several regular PHP driven websites with includes, and 1 1000+ plus VB on a dual xenon, 3.0+ 2 gig ram box? I mean, really, without crashes.

[ChrisLM2001]

From what I've seen, with 1000+ members, a dual Xeon won't be enough. Apache and Mysql will crush it to death. You'll have to split the load.

There's only so many connections Apache can keep open before the memory is used all up. Then compound the heavy memory requirements of mysql, and it's too many resources needed for one box. And don't forget the I/O would be taxed, further slowing the data delivery.

At the least a dual Xeon with a 2GB web frontend server. Or the server is going to crawl, and no member will care to stay if they have to fight just to get a connection, too.

ADDED: A good rule of them about resources (just for vB)...

0 to 100 = Shared will do.
100 to 200 = High VPS will do.
250 to 500 = Dual Xeon will do.
500 to 700 = Dual Xeon (2GB) with 1 web front end.
750 to 1000 = Dual Xeon (2GB) with 2 2GB web front ends.
1000+ = Dual Xeon (4GB) with 3 2GB web front ends.

Every 250 consistent members you'll be needing a 2GB web front end server for best performance. That'll take care of all of the connections without killing the I/O.

That should leave 10 to 25% in reserve for peaks, but it's very "ify" due to no two people will host the same thing. You'll need to experiment with the right formula for your needs.

Chris

[bobbleheadR2D2]

Apache and Mysql will crush it to death.

I know, Im on a P4 2.X with 1 gig ram now, hosting these very scenerios


And don't forget the I/O would be taxed, further slowing the data delivery.

I know, heavy I/O waits, with server loads spiking over 100 at times now


I appreciate your feedback. So basically, if you want to run a popular VB site with over 500 people average, you need 2 dedicated servers, especially if you have other semi-visited PHP sites on the same box(es).

Anyone else agree/disagree? VB Team members? If so, why, how. Tis a mystery that has baffled me for over 2 years, would like to get a final answer before I upgrade both VB and the server to compensate.

Thanks!

[bobbleheadR2D2]

ADDED: A good rule of them about resources (just for vB)...

0 to 100 = Shared will do.
100 to 200 = High VPS will do.
250 to 500 = Dual Xeon will do.
500 to 700 = Dual Xeon (2GB) with 1 web front end.
750 to 1000 = Dual Xeon (2GB) with 2 2GB web front ends.
1000+ = Dual Xeon (4GB) with 3 2GB web front ends.

Every 250 consistent members you'll be needing a 2GB web front end server for best performance. That'll take care of all of the connections without killing the I/O.

That should leave 10 to 25% in reserve for peaks, but it's very "ify" due to no two people will host the same thing. You'll need to experiment with the right formula for your needs.

Chris

Read your addition, duely noted, and makes sense, good guide to go from. Unless someone else makes a good argument otherwise, I will use that as a reference in my future endeavors :)

Thanks much!