You'd want to change the initdefault setting from 5 to 3 (like RedHat, SuSE
uses 2 for multi-abuser w/ no network and 3 for multi-abuser with
networking).
One wonders how an initdefault of 5 got set w/o a framebuffer. Ouch.
There are also some other tunables to allow you to manage the "disk
caching" but I've long since lost the URL; it's somewhere on the
developerworks. It's a matter of echoing various values to various /proc
file thingies.
*SIGH*
(Imagines a Tyrranosaurus Rex carrying a row of Penguins down it's back,
arranged kind of like the armor plates of a Stegosaurus.)
BTW, anybody here still have a "Peace Love Linux" flag? I wanna get one
for my sailboat. It'd sure be better than the "Tampa Bay Buccaneers" flags
I usually see...
--------------------
John R. Campbell, Speaker to Machines (GNUrd) {813-356|697}-5322
Adsumo ergo raptus sum
MacOS X: Because making Unix user-friendly was easier than debugging
Windows.
Red Hat Certified Engineer (#803004680310286)
IBM Certified: IBM AIX 4.3 System Administration, System Support
----- Forwarded by John Campbell/Tampa/IBM on 11/16/2004 04:39 PM -----
Adam Thornton
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
mine.net> cc:
Sent by: Linux on Subject: Re: [LINUX-390] Linux
Performance Issue
390 Port
<[EMAIL PROTECTED]
IST.EDU>
11/16/2004 05:14
PM
Please respond to
Linux on 390 Port
On Nov 16, 2004, at 2:58 PM, John Kaba wrote:
> We have just recently installed SuSE SLES8 under our VM3.1.0 system,
> and
> are experiencing some performance issues. Our Realtime monitor reveals
> that Linux is utilizing approx 65% of our CPU cycles, but we really
> have
> nothing running. I was told by our Linux guy to give it lots of
> memory, so
> I defined it with 1G. I'm wondering if this is my problem, or if I
> might
> have something else set up wrong. We have Tivoli Directory Server 5.2
> fixpack1, DB2 ver 8.2, and websphere express 5.1, but it is not
> configured
> yet. We have just installed these products, and they are not being
> used at
> all, still we are seeing results like this:
>
You Linux image is way too big and you're probably seeing VM getting
tired paging it in and out. Try reducing it to 384MB. You will also
want to turn off timer ticks. I don't remember exactly what it is you
need to echo to where in /proc, but I'm sure someone else does.
The other thing that's hurting you is KDE. Why are you running a
desktop manager on your 390? Turn *off* X entirely--you don't have a
local display there anyway. Again, I don't remember what runlevel
"services, no X" (I think it's "2", but I won't swear to that) is in
SuSE, but I'm sure someone does.
Adam
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
