The reason I'm looking for performance tuning is my hardware :) I have
some very old hardware, an old IBM PC Server 520 with HW SCSI RAID,
but only with 2 P133 CPU's and 256 MB RAM (this is all the RAM it will
take, so no possible upgrade here). And therefore I want to remove
everything that is taking up resources.
I have disabled most of the running services, so only the ones I need
is running, but I'm having some problems finding information one some
of your suggestions and their consequences, so here comes some
questions:
As I can read on the net, fsync makes sure data is written to disk
somehow. What happens if I turn fsync off? Will I risk losing data all
the time? I'm using ext3 on all disks.
How and where do I turn off reverse-lookups in Redhat?
Adding a "-" in the syslog.conf? Huh where do you find information on
this?? What is this, and what does it do?
man mount gives me this:
noatime Do not update inode access times on this file system
(e.g, for faster access on the news spool to speed up
news servers).
This sounds greath, but it does not say if there is any trade offs.
I'm absolutely no filesystem expert, so please explain it to me :)
I hope you (or somebody) can give me some info on these subjects.
Best regards
Søren
Friday, December 6, 2002, 8:34:22 PM, Ben wrote:
BR> Go for the low-hanging fruit first.
BR> 1. Pick hardware that suits your needs...
BR> 2. Make sure you have the latest BIOS and firmware installed for all
BR> 3. Read all the fine documentation for the services that you are
BR> running. You may find that by turning off "fsync" in a config file or by
BR> turning of reverse-lookups, or adding a "-" in the syslog.conf, or
BR> setting noatime in fstab, you are making a tradeoff in logging or worst
BR> case scenario disaster preparedness that you can live with, but in
BR> exchange you can get up to a 10 fold increase in performance.
BR> 4. Carefully examine the processes that *YOU* write. CGI programs, SQL
BR> 5. Examine Kernel parameters like shared memory segments, bdflush
BR> parrameters, and the priorities of your various processes (you might be
BR> able to "nice" some background processes).
BR> Stripping your box of unnecessary software and removing lots of kernel
BR> module options may make it boot faster, and may make it more secure in
BR> certain scenarios, and it will definitely save a few MB or GB of disk
BR> space and a few KB of RAM, but in most every case I have seen makes very
BR> little dents in runtime performance.
BR> After you have done these things then you need to consider what your ROI
BR> is for further tweaking. Often times tweaking to the nth degree causes
BR> scalability and maintainability issues in the future and so it is easier
BR> to think about a scaling methodology that involves bigger or broader
BR> server infrastructure, and that will be cheaper in the long run than
BR> trying to tweak the kernel config.
BR> On Thu, 2002-12-05 at 17:31, Søren Neigaard wrote:
>> My Redhat will be a server, and not a workstation, and therefore I
>> guess I can remove some of the services starting at boot time, or?
>>
>> One thing I found in my dmesg was this: "VFS: Diskquotas version
>> dquot_6.5.0 initialized". I don't need diskquotas so can't I just
>> remove it somehow? Or am I going at it the wrong way?
>>
>> Any pointers to things that I should stop/remove from the standard
>> install?
>>
>> --
>> Med venlig hilsen/Best regards,
>> Søren Neigaard mailto:[EMAIL PROTECTED]
>> --
>> "Programming today is a race between software engineers striving to build bigger
>and better idiot-proof programs, and the Universe trying to produce bigger and better
>idiots. So far, the Universe
>> is winning."
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
