• Post Reply Bookmark Topic Watch Topic
  • New Topic

Java processes(weblogic) using high cpu in linux system  RSS feed

 
dylan payne
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My system consuming high cpu.I checked the database side but its okey.I need some advice.You can see the process.I looked with top and top -h commands and here some dump threads.I saw many GC worker thread process.Whats the main problem and how can I fix it?

Top command


Top -H command


 
dylan payne
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
any advice
 
Karthik Shiraly
Bartender
Posts: 1210
25
Android C++ Java Linux PHP Python
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How many CPU cores does your system have?
On what basis are you saying it's high CPU?
 
dylan payne
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Karthik Shiraly wrote:How many CPU cores does your system have?
On what basis are you saying it's high CPU?


Its firm system.We have got 2 machines and 2 clusters.
-d64 -Xms8G -Xmx8G (service start parameters)

here system:



 
Karthik Shiraly
Bartender
Posts: 1210
25
Android C++ Java Linux PHP Python
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Looks like the output of cpuinfo is truncated, but based on what you have put up it's a system with 12 processors, each with 6 cores with hyperthreading enabled (because siblings=12).
So we are talking about 48 cores in all or 96 vCPUs - a massively powerful system.
Edit: No I got it wrong. It's the same physical ID. So it's one processor with 6 cores with hyperthreading. So 12 vCPUs.

I don't really see anything in the screenshot that says overall CPU utilization is high. 184% means 1 vCPU is 100% and one more is 84% occupied. Similarly for other entries.
10 GC threads doesn't seem high either. JRockit GC probably works differently, but if it was Hotspot, it would have created 16-24 GC threads for 48 cores Edit: similar number of threads.

What makes you say it's high CPU? Are you actually seeing any problems or errors?
 
Karthik Shiraly
Bartender
Posts: 1210
25
Android C++ Java Linux PHP Python
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Moving this topic from "Java in General" to Performance forum
 
dylan payne
Ranch Hand
Posts: 36
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Karthik Shiraly wrote:Looks like the output of cpuinfo is truncated, but based on what you have put up it's a system with 12 processors, each with 6 cores with hyperthreading enabled (because siblings=12).
So we are talking about 48 cores in all or 96 vCPUs - a massively powerful system.
Edit: No I got it wrong. It's the same physical ID. So it's one processor with 6 cores with hyperthreading. So 12 vCPUs.

I don't really see anything in the screenshot that says overall CPU utilization is high. 184% means 1 vCPU is 100% and one more is 84% occupied. Similarly for other entries.
10 GC threads doesn't seem high either. JRockit GC probably works differently, but if it was Hotspot, it would have created 16-24 GC threads for 48 cores Edit: similar number of threads.

What makes you say it's high CPU? Are you actually seeing any problems or errors?


CPU is really high.Normally java using %30 or less.But its increased incredible high in last two days.We cant use like this
I upload the full dump file, can you look please, I couldnt find anythng.
I counldnt atach because size
here download link http://www.megafileupload.com/en0e/dump_thread.rar

 
Karthik Shiraly
Bartender
Posts: 1210
25
Android C++ Java Linux PHP Python
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'll take a look today, but not right now.
 
Tim Holloway
Bartender
Posts: 18531
61
Android Eclipse IDE Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Most likely one or more deployed webapps is being a CPU pig.

What makes it challenging is that the OS thread ID and the JVM internal thread ID are 2 different values, so finding WHICH application is running rampant means translating the OS thread ID to its corresponding Java thread ID and then further homing in on the exact code where the issue occurs.
 
Don't get me started about those stupid light bulbs.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!