Here we saw a overall increase in DB response time but still able to separate cause from effect....Any leanings I can use here? Basically I want to find the culprit and separate the noise. May be it is a single execution of a query that caused this etc.. How much can DT be used here?
Answer by Andreas G. ·
I would check the Database Hotspot and Database Dashlet in that timeframe. Typically these things are either data driven or load driven problems. If it is data-driven the Database Dashlets will show you certain statements being executed hundreds or even thousand times. Check out the following blog which contains a section on too many DB statements: http://apmblog.compuware.com/2013/04/10/top-8-application-performance-landmines/
Also - we recently recorded a webinar on how to analyze database hotspots - available on APM University: How to solve database performance issues.
Answer by Jibi U. ·
I gonna check this out in detail. Meanwhile I did a dashboard compare for database tashlet over a 10 min time period. Wanted to look at the change in execution %. But was not able to come to a conclusion may be because of the scale of things. Anyways will see the webinar later.
JANUARY 15, 3:00 PM GMT / 10:00 AM ET