On Fri, Dec 06, 2002 at 02:34:22PM -0500, Ben Russo wrote to Søren Neigaard: > Go for the low-hanging fruit first.
Søren, One low plum is to edit your /etc/inittab to change your initdefault to 3 (that is, not to fire up X automatically). It can be useful to have X, even on a server, but keep it shutdown except for when you need it. That will free up RAM, keep your caches cleaner, and save CPU cycles. Speaking of RAM, it is cheap these days, if you are lacking performance, adding more RAM can frequently help. *Are* you lacking in performance? What kind of stuff are you going to be serving and to whom (LAN or WAN)? > For example, if you have a LARGE transaction processing database > then your disk seeks and writes are going to be a big issue. > In this case you would do well to invest in a Hardware Raid > controller with battery backed write cache and consider RAID 10. If you have less money, software raid can speed things up too. Databases love lots of RAM. > Or, if your server is a Web Application Server, (a "slashdot" > like server, or ecommerce server) then your CPU and RAM are > going to make a lot of difference since you can probably keep > most everything cached in RAM and your bottleneck will be CPU > for all the PHP and PERL and APACHE stuff. I have heard of sites splitting out static pages to a separate (and more svelte) web server, like boa, and only using Apache for those pages that actually need Apache's flexibility. Unless someone is giving you free bandwidth, the hardware it takes to saturate a given internet connection is usually a lot cheaper than a few months of paying for that internet connection. Seriously compute bount tasks are obvious exceptions to this platitude. -kb -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
