<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How long does AppD take to perform Garbage Collection analysis in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Re-How-long-does-AppD-take-to-perform-Garbage-Collection/m-p/736243#M9780</link>
    <description>&lt;P&gt;Thanks for the clarification Adrian.&lt;/P&gt;

&lt;P&gt;The Java agent collects heap, memory, and GC-related metrics from standard JMX MBeans in the instrumented JVM. These metrics are available whether or not verbose GC logging is enabled.&lt;/P&gt;
&lt;P&gt;This means that the agent does not have access to the verbose GC logs and does not analyze these logs to calculate "GC Pause Duration" or "GC concurrent Duration".&lt;/P&gt;
&lt;P&gt;The agent does provide metrics for "Garbage Collection Time Spent (ms/min)" broken down by "Minor Collections", "Major Collections", and "Total".&lt;/P&gt;
&lt;P&gt;I believe that these metrics should be helpful for fine tuning the GC performance, with less overhead and effort than generating verbose GC logs and running a GC log analyzer on these logs.&lt;/P&gt;
&lt;P&gt;Screenshot of the JVM Memory page attached.&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Wed, 10 Oct 2018 12:52:24 GMT</pubDate>
    <dc:creator>Brian_Wheeldon</dc:creator>
    <dc:date>2018-10-10T12:52:24Z</dc:date>
    <item>
      <title>Re: How long does AppD take to perform Garbage Collection analysis</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Re-How-long-does-AppD-take-to-perform-Garbage-Collection/m-p/736242#M9779</link>
      <description>&lt;P&gt;Hi Brian,&lt;/P&gt;
&lt;P&gt;Thank you so much for your info. Sorry I will give you more clarification on my request.&lt;/P&gt;
&lt;P&gt;Usually when you look at Garbage collection performance, Log anysis tool&lt;/P&gt;
&lt;P&gt;such as GC log analyser gives you additional metrics to help fine tune GC performance.&lt;/P&gt;
&lt;P&gt;Common metric used is "GC Duration".&amp;nbsp;&lt;/P&gt;
&lt;P&gt;GC Duration values reported contains&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1 "GC Pause Duration"&lt;/P&gt;
&lt;P&gt;2. "GC concurrent Duration"&lt;/P&gt;
&lt;P&gt;"GC Pause Duration" is valuable metric to monitor that often needs tuning. Some GC log analysers are able to extract "GC Pause Duration".&lt;/P&gt;
&lt;P&gt;Just wondering AppD capability to provide "GC pause duration"!&lt;/P&gt;
&lt;P&gt;Definitions:&lt;/P&gt;
&lt;P&gt;Pending on event type (Fully paused or Partiall Paused)&lt;/P&gt;
&lt;P&gt;Young GC : Fully paused (GC Duration = GC Pause Duration)&lt;/P&gt;
&lt;P&gt;Old GC :&amp;nbsp; &amp;nbsp; &amp;nbsp; Partially Paused (out of 5 phases: 3-complelely paused[GC Pause Duration] &amp;amp; 2-run&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; concurrently[GC concurrent Duration]&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know your thougts.&lt;/P&gt;
&lt;P&gt;Many Thanks&lt;/P&gt;
&lt;P&gt;Adrian&lt;/P&gt;</description>
      <pubDate>Tue, 09 Oct 2018 23:10:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Re-How-long-does-AppD-take-to-perform-Garbage-Collection/m-p/736242#M9779</guid>
      <dc:creator>CommunityUser</dc:creator>
      <dc:date>2018-10-09T23:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: How long does AppD take to perform Garbage Collection analysis</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Re-How-long-does-AppD-take-to-perform-Garbage-Collection/m-p/736243#M9780</link>
      <description>&lt;P&gt;Thanks for the clarification Adrian.&lt;/P&gt;

&lt;P&gt;The Java agent collects heap, memory, and GC-related metrics from standard JMX MBeans in the instrumented JVM. These metrics are available whether or not verbose GC logging is enabled.&lt;/P&gt;
&lt;P&gt;This means that the agent does not have access to the verbose GC logs and does not analyze these logs to calculate "GC Pause Duration" or "GC concurrent Duration".&lt;/P&gt;
&lt;P&gt;The agent does provide metrics for "Garbage Collection Time Spent (ms/min)" broken down by "Minor Collections", "Major Collections", and "Total".&lt;/P&gt;
&lt;P&gt;I believe that these metrics should be helpful for fine tuning the GC performance, with less overhead and effort than generating verbose GC logs and running a GC log analyzer on these logs.&lt;/P&gt;
&lt;P&gt;Screenshot of the JVM Memory page attached.&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Wed, 10 Oct 2018 12:52:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Re-How-long-does-AppD-take-to-perform-Garbage-Collection/m-p/736243#M9780</guid>
      <dc:creator>Brian_Wheeldon</dc:creator>
      <dc:date>2018-10-10T12:52:24Z</dc:date>
    </item>
  </channel>
</rss>

