General
cancel
Showing results for 
Search instead for 
Did you mean: 

Linux Advance Server CPU resources.

sdip
Advisor

Linux Advance Server CPU resources.

Hi,

I am newbie in Linux world.

I have just installed Linux Advance Server 2.1 in Proliant 580 server. After that I configured WebLogic Server on it.

Currently top is showing there are 8 CPU but actually it has only 2 CPUs. I chekced /proc/cpuinfo, it also showing 8 CPU. Also system load is getting high by Java processes.

See the following information.

[root@app1 linux-2.4]# uname -a
Linux app1 2.4.9-e.3smp #1 SMP Fri May 3 16:48:54 EDT 2002 i686 unknown

[root@app1 linux-2.4]# dmesg | grep -i processor
CPU: Physical Processor ID: 2
Booting processor 6/6 eip 2000
CPU: Physical Processor ID: 3
Booting processor 7/7 eip 2000
CPU: Physical Processor ID: 3
Total of 8 processors activated (22315.00 BogoMIPS).

Please let me know why this strange behaviour is showing in Linux. Is there any document or link avaiable where I will get WebLogic recommended Kernel Parameter information.

Thanks
SD

4 REPLIES
I_M
Honored Contributor

Re: Linux Advance Server CPU resources.

Hi

Are you using Hyper Threading?
2.4.9-e.12 fix HT support.
And latest kernel is e.25

Good luck
Caesar_3
Esteemed Contributor

Re: Linux Advance Server CPU resources.

Hello!

What processors do you have?
The top take the data about CPU from /proc/cpuinfo
In MP and the processort is HT then you
have more processors on every processor.

Caesar
K.C. Chan
Trusted Contributor

Re: Linux Advance Server CPU resources.

All,
I noticed the dude says he has 2 CPUs, with HT you will see 4 CPUs. This doesn't explain why he is seeing 8, Unless there are 4 CPUs on the server.
Reputation of a thousand years can be determined by the conduct of an hour
Stuart Browne
Honored Contributor

Re: Linux Advance Server CPU resources.

KC is right. But I'd start with what Caeser said, upgrade the kernel.

As for the Java giving a high load average, make sure you are using nice 'wait()'s. One of the Java apps we had was being nasty when waiting for information on a socket.
One long-haired git at your service...