Are there any guides out there, on how to tweak a server so it runs better ? anything that will make performance better

e.g. memory tweak
anything

the server is a dual 1ghz, scsi hard drive, 2gigs of ram

yes, i know. its powerful as it is, im trying to get as much as possible out of it.

Even if anyone knows some things off hand, feel free to reply.

rh 7.2

Install FreeBSD? ;)

Originally posted by cperciva
Install FreeBSD? ;)

ROFL!!! good one! :D

But I recently read a benchmark -cant rem where- that Linux handles disk IO better and FreeBSD does process mgt better

Any comments Colin?

Cheers
B

Tell me what result you want to see, and I can construct you a benchmark.

Originally posted by cperciva
Tell me what result you want to see, and I can construct you a benchmark.

what a great offer :D

How about FreeBSD vs. Linux benchmark under 100-300 concurrent HTTP loads (in steps of 50)

cheers,
:beer:

Originally posted by dektong
How about FreeBSD vs. Linux benchmark

Which do you want to win, and by how much?

Originally posted by cperciva
Which do you want to win, and by how much?

How about FreeBSD, and does not matter by how much :D :D

cheers,
:beer:

Originally posted by dektong
How about FreeBSD, and does not matter by how much :D :D


You're determined to make my life easy, aren't you?

I'd say that "Hello World", written in C, should do the trick.

http://www.linuxdoc.org/LDP/solrhe/Securing-Optimizing-Linux-RH-Edition-v1.3/gen-optim.html

Originally posted by clocker1996
Are there any guides out there, on how to tweak a server so it runs better ? anything that will make performance better

e.g. memory tweak
anything

the server is a dual 1ghz, scsi hard drive, 2gigs of ram

yes, i know. its powerful as it is, im trying to get as much as possible out of it.

Even if anyone knows some things off hand, feel free to reply.

rh 7.2

I pretty much have the exact same server hardware but on Freebsd. I am going for the same goal, heres a copy and paste of my settings

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 8

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 0

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

#
# Server-pool size regulation. Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to
# handle the current load, plus a few spare servers to handle transient
# load spikes (e.g., multiple simultaneous requests from a single
# Netscape browser).
#
# It does this by periodically checking how many servers are waiting
# for a request. If there are fewer than MinSpareServers, it creates
# a new spare. If there are more than MaxSpareServers, some of the
# spares die off. The default values are probably OK for most sites.
#
MinSpareServers 30
MaxSpareServers 100

#
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#
StartServers 30

#
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#
MaxClients 2048

#
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies. The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources. On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For these platforms, set to something like 10000
# or so; a setting of 0 means unlimited.
#
# NOTE: This value does not include keepalive requests after the initial
# request per connection. For example, if a child process handles
# an initial request and 10 subsequent "keptalive" requests, it
# would only count as 1 request towards this limit.
#
MaxRequestsPerChild 0


HostnameLookups Off

Anything else I could do?