Hi Gary,
   
  We had a similar problem back at my last place and *sucks the life out of the 
machine* is about right.
   
  Sounds like it could be a storage leak/creep within the heap that is causing 
the Java heap to go into more frequent garbage collections, especially if the 
heap is lightly allocated - hopefully it's at least 512 MB or above, as free 
space diminishes over time to the point where a compaction of the Java heap may 
be occurring. The compaction process takes considerable CPU to complete. I'm 
not sure of the reporting at this point with version 6 of WAS but turning on 
verbose GC, garbage collection, may shed some light on this anomaly and if it 
is indeed heap space related. BTDTGTS.
   
  Of course this could also be a runaway thread, bad logic, in which case 
you'll need some tracing to find the culprit but would lean on the above if it 
is happening, like, late afternoons around the same time.
   
  I also wonder if log offloads might be causing this but I can't seem to 
remember if this was a cause of significant CPU within WAS. I'm sure we'll get 
more elegant responses in the morning.
   
  A bit off topic, sorry, I just got done watching the Forbin Project with my 
son, great movie, I forget who recommended it but thanks....
  
Gary Green <[EMAIL PROTECTED]> wrote:
  If someone knows where I should ask this question, please tell me where to
go. ;)

Otherwise...

I was chatting with the manager of the tech support group at another company
and he was telling me that in his shop they experience a terrible slowdown
in WebSphere most afternoons; "sucks the life out of the machine" comes to
mind. They do not have anyone that does performance or capacity work to
"run the numbers"; and they collect very little SMF data even if they did or
knew how to "run the numbers". He thinks it's the application programmers
poorly written code, probably Java doing some daily end of day stuff. To
make matters worse, they are still on 1.4, with plans to make a brief
stopover on 1.7 before heading off to 1.9.

They are pretty much a vanilla IBM shop with a couple of DB2 V7 production
regions a couple of production CICS regions and some/few regions each for
QA, Dev and testing. I think he said WebSphere was... version 6 if that
makes sense... (I am not conversant in WebSphere). They are on a ~480 mip
Z9.

I know this is not really much to go on but does anyone have any suggestions
I could pass along? Perhaps some insight or suggested diagnostic processes?


Gary Green
While the big event is over, there is still time for you to help me with my
efforts to assist those stricken with cancer!
Please support my efforts by visiting:

http://www.active.com/donate/tntsonj/tntsonjGGreen 

Thank you.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to