Question.

[Grreat]

Which plan would be suitable for running a web server that has php capabilities (forums) and could also host a teamspeak or ventrillo server? Obviously this includes MySql, which I also plan to use for another project.

I'm assuming a voice chat server does not fall under the IRC limitation, if it still exists.

I guess network latency would be my first questionable. CPU latency shouldn't be a factor because i believe most voice chat software encodes voice clientside, and I'm not really concerned about bandwidth.

I'm thinking of the 96 package because I like the pricing.

I'm planning on using Debian though I have experience with Slackware and Gentoo. I have 0 experience with Apache, and am considering lighter web servers because of the learning curve if possible. I have IIS experience (ducks) so I know many of the concepts, at least.

Would the 96 be enough? Am I wrongly concerned and a smaller package could be usuable?

Last question: Am I doing this all wrong and I should get more than one VM for the seperate servers even though I don't plan on expanding beyond my planned architecture?

[StoryInMemo]

Considering it's just Apache and one other app (and mysql, but supporting apache), one machine at 96 should definitely do it for you. Only wildcard for me is the teamspeak / ventrillo server -- I don't know how much that takes up, but I can't imagine it is much other than routing packets.

[DJ_Max]

For a webserver, I would suggest Lighttpd (http://lighttpd.net/), there's little reason to actually use Apache. You'll get a lot more out of your server using Lighttpd. Teamspeak and Ventrillo just require a good network.

[demonlag]

[QUOTE=StoryInMemo]Considering it's just Apache and one other app (and mysql, but supporting apache), one machine at 96 should definitely do it for you. Only wildcard for me is the teamspeak / ventrillo server -- I don't know how much that takes up, but I can't imagine it is much other than routing packets.[/QUOTE]

I have a 32 package that was doing secondary DNS for me. I moved my Ventrilo server from my webserver to secondary DNS because the webserver load was killing Ventrilo. Typically Ventrilo is using sub 1MB of RAM and under 1.0% CPU time, and that is with 4-6 people talking non stop.

Not a high resource application at all.