Gr8One — Thu, 08 Nov 2001 23:01:07 +0000

Thanks for all the info, netcommr, i'll keep it all in mind.

netcommr — Thu, 08 Nov 2001 19:48:05 +0000

from personal experience...

use a *nix/apache machine

pre-compile heavily used scripts under mod-perl, use fast-cgi for others

dual processors (or more) is recommended

get as much memory (ram) as you can (1 gig min.)

many perl scripts use a lot of hard drive resources, go with scsi drives on a raid 5/50, go with smaller drives and more of them!! (1 big drive will bog the whole system down)

make sure you nic card is 100 base (bus-mastering)

depending on the number of users and output of scripts, your bandwidth can grow exponencially. You may start with a T1 and find out its used up quickly. Prepare for upgrades this area quickly. I run around 6-8 gigs a day so expect to 'pay' highly in this area.

keep your own pages fast (static) and use a minimum of server parse pages (SSI,PHP)

when you really rolling in the future, keep load balancing in mind for your scripting machines

run your DAILY BACKUPS(!!) at slowest times

mairving — Thu, 01 Nov 2001 02:13:41 +0000

You might give some more details of what you are planning on running like no. of visitors, what kind of bandwidth. You won't be very popular with many hosts running memory/processors hogs like cgi, though.

mjames — Wed, 31 Oct 2001 23:16:14 +0000

Moved this to a more appropriate forum for you.

I haven't run a site like that, but would imagine that kind of site would have massive bandwidth problems, as you suspect, and especially if you get popular. That's just the nature of CGI. That's why I like PHP and MySQL.