On Wed, Mar 28, 2007 at 05:55:23PM +0530, Siju George wrote: > > The server i have is > > ====================================================================== > 1x Dual-Core Opteron 2210 (1.8GHz) on a Dual CPU Motherboard > > 2x 2GB RAM/PC3200 (4GB Total) > > 2x Onboard GbE LANs > > CD-ROM > > 1U 2 Hot-Swap Bays Chassis & Mounting Brackets > > x Dual Channel SATA RAID Adapter > > 2x 500GB 7200 RPM SATA RE Hot-Swap HDD's > ========================================================================= > The hardware specs look good. How much bandwidth will the server have going to it? I mean is your ISP connection a dedicated T1, T3, or something else?
> So I hope I should be Installing ( right? ) > > kernel-image-2.6.8-12-amd64-k8-smp - Linux kernel image for version > 2.6.8 on AMD64 SMP systems > > to harness the full power of the CPU as currently it shows only > You want to be using Etch. > > Just wondering mdadm can monitor this hardware Raid Controller? is it > supported? > I think you need the monitoring tools from 3ware. However, I am not certain. In any case, mdadm is for the Linux software RAID implementations. > I hope to Install LVM and have seperate partitions for > "/var/log" and "/var/www" so I can adjust them if there is any need in > future. > Put everything on LVM. That allows you to create separate partitions as necessary. > What do you suggest use up the whole 500 GB disks or leave some free > Space for later use? > I would say, start with the partitions as small as you can. Use XFS and grow the partitions as necessary. > Should I use. > > "apache2-mpm-worker" or "apache2-mpm-prefork"? > > because > > http://www.debianhelp.co.uk/apacheinstall.htm > > says "apache-mpm-worker" could be a risk. > > Also this will be on PHP5 and will be contacting a MySQL 5.0 Database > Server with the same Specs. > With PHP, I believe that you *must* use prefork. This is because PHP is not really thread-safe. Even if they have managed to clean up the PHP core, most external libraries are not thread-safe. If you have any choice in the matter, use Python or Perl instead of PHP so that you can use apache's worker MPM, which by all accounts should perform lots better. At the risk of starting a flameware, please don't use MySQL. That is, unless you are a super experienced expert. It is well known that MySQL's performance drops very quickly as the number of connections increases. This can be mitigated with clustering and performance tuning (for example, slashdot uses a MySQL cluster and they have been performance tuning it for like 8 years). However, since you have only one server, you really want a database that will scale well in one instance. For that, I can recommend PostgreSQL (unless you want to spring for Oracle or DB2, but you are unlikely to get support for those on Debian). > Hope these informations are enough :-) > > Please let me know if you need more. > Regards, -Roberto -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com
signature.asc
Description: Digital signature
