DX Application Performance Management

 View Only
  • 1.  Intelligent Instrumentation taking too much CPU

    Posted Dec 21, 2015 07:48 PM

    We have a user that wrote:

     

                    During analysis of a thread dump from our MicroServices environment it was observed that the “Intelligent Instrumentation Thread” (com/wily/introscope/agent/trace/intelligent/HighPerformanceIntelligence) was consuming about 30% of the CPU cycles. The environment is WAS 8.5 and Agent ver is 9.7. Do you have any reports of such behavior? Is this related to any configs?

     

    IntelligentInstrumentation.jpg

     

    I indicated that we can turn this off. We are running with default agent set up for 9.7.1.16 agent

     

    This is the first I have heard of this....

     

    Thanx

     

    Steve



  • 2.  Re: Intelligent Instrumentation taking too much CPU

    Broadcom Employee
    Posted Dec 21, 2015 08:39 PM

    Hi Steve,

    It looks like there have been a few reports of this symptom after upgrade to 9.7.x where the (smart/intelligent) deep trace property is enabled by default (although the level is set to low).

    Agent Ability to Collect Deep Visibility Components Now Enabled by Default

    How to Configure the Agent for Smart Instrumentation

     

    If customer needs to use it but wants to reduce the CPU overhead KulbirNijjer might have some tuning suggestions

    Hope this helps

    Regards,

    Lynn



  • 3.  Re: Intelligent Instrumentation taking too much CPU

    Posted Dec 21, 2015 08:55 PM

    Hi Steve,

    We definitely need more details:

    -How was this analysis done, what tool was used ?

    -Over what period of time this usage was measured, from screenshot appears around 10-11 hours but pls. confirm ?

    -Did this cause any performance issues with the application itself ?

     

    As you indicated this thread is part of the Smart Instrumentation feature in Agent and by itself thread is not doing a lot of processing, simply updating system time though runs very frequently(read quickly). As such it normally shouldn't have any impact to application performance or block any processing.

     

    Regards,

    Kulbir.