Server load and MYSQL

[crash3m at comcast.net]

with those specs I dont think medusa/webmin etc... are going to be the
problem.   I suggest running top/ps to see whats chewing up the ram/cpu
then eliminating the problem.   DB queries can be quite intensive from
my understanding, but then again I dont do DB's so my opinion use
pretty much useless I'm sure ;)

My $0.02

ML

On Mon, 21 Oct 2002 17:23:12 -0500
Jason Clinton <clintonj at umkc.edu> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Aaron wrote:
> | Hi all.  I'm looking for a second opinion. (or a third, fourth,
> fifth....)|
> | Here's the situation:  I'm running a server with the following
> specs:| Dual P3 1.3Ghz, 1GB ECC Registered RAM, Dual 18GB SCSI Ultra
> 160 10K RPM| drives, Adaptec 29160 (the 64bit version)...  <--
> Important specs. :)|
> | This server is running RedHat 7.3 (with an upgraded kernel.
> 
> 
> | Any help, suggestions, opinions, etc would be greatly appreciated.
> |
> 
> First thing I would do is go through all the daemons that are running
> that Redhat enables by default that you don't need and start
> eliminating them. Webmin, Medusa and Squid are useless if it's a web
> server. Other things like disabling X and other apps that you don't
> need running can save you allot of resources. Is there a cron job that
> might be causing this? Check your crontab...
> 
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQE9tH5Psu4jBEqJRr8RAm1OAKDgZb4YcguGbDkkSit4lA6VYg7rRACeI+nK
> oh3Fl0j5cOQACiJ5ZS27XAo=
> =0hM0
> -----END PGP SIGNATURE-----
> 
> 
> 
> majordomo at kclug.org Enter without the quotes in body of message