DX Application Performance Management

  • 1.  Analysis - Current Status of Worker Processes/Threads (%)

    Posted Oct 26, 2016 11:25 PM

     

    In the picture above the 3 key metrics are:
    Open Slot With No Current Processes / Threads (%) - Percentage that ta is waiting for new incoming requests.
    Keepalive (read) - Numbers of existing connections (live).
    Waiting for Connection - Percentages connections awaiting processing start.

     

    In the image above analysis we can say that 88% of the time the server is waiting for new incoming requests via the metric Open Slot With the Current Process? You can download it?

    In metric keepalive we have the percentage of existing connections.

    In metric Waiting for Connection - we have the percentage of connections waiting for the processing start.

    Conclusion: (It is safe to say that?)
    We can say that most of the time the server loses waiting for connections?

    Any tips for this conclusion?

    Thank you so much!



  • 2.  Re: Analysis - Current Status of Worker Processes/Threads (%)

    Posted Oct 27, 2016 11:24 PM

    Hello! Someone?



  • 3.  Re: Analysis - Current Status of Worker Processes/Threads (%)

    Broadcom Employee
    Posted Oct 28, 2016 05:48 AM

    Hi Olivia:

        I requested internally if someone can respond to this. 

    Thanks

    Hal German



  • 4.  Re: Analysis - Current Status of Worker Processes/Threads (%)

    Broadcom Employee
    Posted Oct 28, 2016 09:52 AM

    Open Slot With No Current Processes / Threads (%) - Percentage that ta is waiting for new incoming requests.
    Keepalive (read) - Numbers of existing connections (live).
    Waiting for Connection - Percentages connections awaiting processing start.

     

    This can be interpreted in a few ways.

     

    1. The app spends less time waiting for a connection.  This could mean that there aren't many connections or the connections come through, request finishes quickly and then it disconnects thereby leaving many open slots available.  i.e. a checkout line at the store where the cashier processes items quickly and efficiently.

    2. Connection comes in, sees that too many connections are already being handled and time out.

    3. Not too much traffic going through.

     

    I'm inclined to think its either 1 or 3.