In DT how we can find it out which method has consumed more memory. While running the test after a certain period, the memory is not get released it got crashed. How we can analyse this more through DT.
Answer by Andreas G. · Jun 05, 2013 at 11:14 AM
dynaTrace has a great solution for memory diagnostics. It wont tell you which method allocated how much memory - but - it will tell you which objects are responsible for your out-of-memory exceptions.
After you have identified which objects are a problem and "who" keeps them alive you can go one step further and define "Memory Sensor Rules" - they will show you memory allocations for specific classes along the PurePath.
Best is to start with the following webinar that explains the memory diagnostics process step-by-step: dynaLearn Webinar - Memory and Thread Diagnostics - February 15, 2012
Thanks Andreas.
But How we can identify the objects that are responsible for out-of-memory exceptions.
How to set the Memory sensor Rules.
The Webinar explains all of this. Also - check out the documentation - there are some good examples: Memory Diagnostics
I'd like to also add this page from the documentation, which I used yesterday to help someone determine the exact cause of a memory leak by walking through step-by-step what was done in the document.
Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!
Learn the enhanced capabilities of the next generation Dynatrace AI root cause analysis and how to feed it with your own data sources.
Wednesday, February 20, 2019
Register today!
Would you like to have an early taste of what we have cooked up for 2019? We would love to hear your feedback and improve some of the new features. Check NAM 2019 Beta release notes.
Sign up today!