• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Anderson T. · Feb 19, 2014 at 08:49 PM ·

Memory issues with dynatrace 5.6 prod edition

Has anyone else seen an increase in CPU and more memory/GC churn when upgrading from dynatrace 5.5 to dynatrace 5.6?   Our DT server is definitely slower and clocking more, and we are trying to pick away at things we can disable to help with the issue.  Any suggestions (besides the obvious one of reducing the purepath size) would be much appreciated.  We have reduced the purepaths (which still arent small, but no different than previously), enabled JDBC stmt aggregation, disabled UEM, reduced purepath max size, and turned off several system profiles that were suspect, etc. 

Ideas?

-Todd Anderson

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

5 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Klaus E. · Feb 20, 2014 at 08:30 AM

Hi Todd,

I have seen after the upgrade at a customer an increase of skipped non-analyzed PurePaths. The reason there is that they are using our mobile native agent and user actions from this agent that get dropped were not counted in previous releases.

Klaus

 

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Feb 20, 2014 at 08:30 AM

If you already have a ticket open then please make sure you also give them all the information that you posted here.

The support team knows these JVM Settings better than I do - so - they can tell you if there is anything "suspicious" about it.

I am worried about the skipped events. Are they skipped on the server, the collector, the agent? Have you checked your collectors as well? Are they under more load?

Have all components been upgraded to the release? or are some components (e.g: individual agents) still running on the prev. version?

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Anderson T. · Feb 19, 2014 at 10:05 PM

Andy, is are there any recommended changes to dtserver.ini, aside from what is installed with 5.6?  We also merged some customizations in, that I want to make sure cause no harm:

 

-XX:+UseCompressedOops

-XX:+OptimizeStringConcat

-XX:+UseStringCache

-XX:-UseBiasedLocking

-Dcom.dynatrace.diagnostics.memory.corridorUpperLimit=90

-Dcom.dynatrace.diagnostics.memory.corridorReductionArea=85

-Dcom.dynatrace.diagnostics.memory.corridorNeutralArea=75

-Dcom.dynatrace.repository.truncation.variant=DELETE FROM {table}

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Anderson T. · Feb 19, 2014 at 09:19 PM

Hi Andy, thanks for the response.  We did indeed increase the dtserver max heap size to the limit of 14GB (previously it was 12 GB).  We dont see any longer purepaths than before, but we are seeing more skipped purepaths and skipped events.  I've reduced the instrumentation so that the purepaths are actually trending a little smaller on average than before.

We do have a support ticket open, but I thought I'd ping the community to see if someone else had already experienced this and solved it.

I've noticed the change in the memory mgmt.  In dynatrace 5.5, the tenured heap would be consumed and would not fluctuate much (not much GC churn).  Now, in dynatrace 5.6, we have the tenured heap going up and down more, and much more GC suspension time.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Feb 19, 2014 at 08:54 PM

Hi Todd

The recommendation is to actually give the server a little more memory because we switched to Java 7 which has a slightly different memory management. Here is what we say about this in the dynaTrace 5.6 Release Notes:

dynaTrace is now on Java 7

Due the fact that Oracle won't deliver additional security updates for Java 6, all dynaTrace components are now optimized for Java 7. Since Java 7 utilizes different memory management, it is recommended that you increase the maximum available memory of the dynaTrace Server and Collector by about 20%. The maximum recommended memory settings for the dynaTrace Server have been increased to 14GB.

If this doesnt help it would be interesting if you observe any other changes, e.g: do you see longer PurePaths, more Skipped Events, ... in your Server Health Dashboards as before? If that is the case I recommend opening a support ticket

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

2 People are following this question.

avatar image avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A