Anyone that is considering burstnet for a dedicated server, do it.. seriously.

Even though their support is not that great, I think that sean is like the greatest, heh..

I opened about 15 different tickets with their system, all regarding the same matter (a dedicated server was HOSSSSSSSED) -- sue me.. i needed help :rolleyes:

Sean worked with me through it to get them all fixed!!!!

So now i've got 3 perfectly working dedicated servers with them, for the price i would be paying for one anywhere else :eek:

Once again, BURST ROCKS!!

Only one small matter i am sstill working on, anyone know why apache might eat an entire server's lunch? it only has like 40 sites on it?

Also, how much ram do I need to work with about 100 sites per server? a few big ons..

thanks guys :)

There are many reasons why Apache could be consuming a lot of resources. It also could be Apache itself, or Apache modules being used, such as PHP. You can set limits globally or per virtualhost directive to limit the amount of CPU, RAM and duration of a process -- per user or again, globally -- depending on how you have Apache configured. It's too difficult to guess why without any information other than Apache itself.

As for how much RAM you should need for a server, it certainly depends on how (well) it's configured. You can go with 128 Megs without any problems, if you do it right, but 256 Megs should do fine with any 1/2 decent configuration/setup. You shouldn't need more than that, or the site's in question might be better on a more user limited server or might require better coding or limitations (which you likely can only do 1/2 of, since you're not going to want to realistically recode a site's programs/scripts if they pose a problem).