# Service flow timings and Percentages breakdown are not matching. Please clarify **URL:** \ **Category:** Real User Monitoring\ **Tags:** services-classic, user-sessions, request-attributes\ **Created:** [December 4, 2020, 2:25am UTC](https://community.dynatrace.com/t/service-flow-timings-and-percentages-breakdown-are-not-matching-please-clarify/20979 "2020-12-04T02:25:58Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![sureshKumarK](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/sureshkumark/32/11469_2.png) [@sureshKumarK](https://community.dynatrace.com/u/sureshKumarK)\ **Post date:** [December 4, 2020, 2:25am UTC](https://community.dynatrace.com/t/service-flow-timings-and-percentages-breakdown-are-not-matching-please-clarify/20979/1 "2020-12-04T02:25:58Z")
![27541-1607049710738.jpg](https://global.discourse-cdn.com/dynatrace/original/3X/e/8/e8ddd7c757384468d2f53002ed4b37c805861a80.jpeg) Hi, please see the screenshot attached. I am trying to calculate the response times breakdown on each tier and the percentage of contribution manually for better understanding. Please help me with what I am missing here. **A --\>** User Action duration is 4.02 seconds (_ **If my understanding is not accurate, please help me on how to add these numbers together to get approx. 4.02 sec?** )_ **B (2 requests, Avg. response time 1.63 sec)--\>** 81% (3.2 seconds) is the contribution where as remaining 19% is on DOM, TCP connection, etc. (network related) **1 --\>** 50% of calls ( 8x per request) , Avg. response time per request is 127 ms =\> 1 x 8 x 127ms = 0.1016 sec (approx..) Question here is Dynatrace shows this tier as 25% of response time contribution. 0.1016 sec is not 25% of 81%. If 25% represents percentage of calls distribution how to explain remaining 75% ? **2 --\>** 50% of calls ( 30x per request), Avg. response time per request is 2.96 ms. Same question as above. Number doesn’t match with 1.7%. **3 --\>** 100% of calls ( 7x per request), Avg. response time per request is 688 microsec. 0.8% doesn’t match **4 --\>** 100% of calls ( 7x per request), Avg. response time per request is 1.97 ms. 0.7% doesn’t match **5 --\>** 100% of calls ( 1x per request), Avg. response time per request is 298 microsec. % not shown by Dynatrace here. Appreciate your help! ---
**Author:** ![sureshKumarK](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/sureshkumark/32/11469_2.png) [@sureshKumarK](https://community.dynatrace.com/u/sureshKumarK)\ **Post date:** [December 10, 2020, 7:45pm UTC](https://community.dynatrace.com/t/service-flow-timings-and-percentages-breakdown-are-not-matching-please-clarify/20979/2 "2020-12-10T19:45:59Z")
I was able to find some info from Dynatrace support about Service flow % and RT calculation. I will update here when I have complete details. DT Support: ```auto In general, the service flow is calculated on the timing on each individual call, therefore the provided formula in general is correct BUT only for 1 level.The second, third etc. level needs to consider ratios from the parent level.This makes the more complex then the 1 level formula. ``` For the second tier, etc.. a modified formula can be used. New formula is: ServiceRT \* Call-Share-Of Service\* Call-Per-Request-Of Service / (Call-Per-Request-Of Root \* Root RT) A couple of things to clarify is that: - Actually, we calculate on each call so the exact data is not based on average values, we operate on each call. - The above formula is a close estimation: In general, we sum up all nodes of each call and divide it through the overall sum. ---
**Author:** ![Babar\_Qayyum](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/babar_qayyum/32/13620_2.png) [@Babar\_Qayyum](https://community.dynatrace.com/u/Babar_Qayyum)\ **Post date:** [January 11, 2021, 11:16am UTC](https://community.dynatrace.com/t/service-flow-timings-and-percentages-breakdown-are-not-matching-please-clarify/20979/3 "2021-01-11T11:16:38Z")
Hello [@Suresh K.](https://answers.dynatrace.com/users/15050/view.html) The **Contributor breakdown** chart gives you a quick overview of time spent on the frontend, the network, and the server. I believe this is a fast and quickest approach to analyze user actions. > **[Analyze individual user actions in RUM Classic](https://docs.dynatrace.com/docs/observe/digital-experience/rum-classic/web-applications/analyze-and-use/analyze-individual-user-actions)** > > Understand how you can access user action detail pages and analyze user actions. Regards, Babar ---
**Author:** ![sureshKumarK](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/sureshkumark/32/11469_2.png) [@sureshKumarK](https://community.dynatrace.com/u/sureshKumarK)\ **Post date:** [January 12, 2021, 12:04am UTC](https://community.dynatrace.com/t/service-flow-timings-and-percentages-breakdown-are-not-matching-please-clarify/20979/4 "2021-01-12T00:04:14Z")
Thanks [@Babar Q.](https://answers.dynatrace.com/users/5357/view.html) I was able to get the following info. ‘x%’ Response time contribution that shown on any service/tier on Service flow diagram is the % contribution of Root time (User action duration) Below is an example of a user action (Avg. User action duration 4.021 sec.) Hope this helps. Thanks, Suresh ![27843-1610409631427.jpg](https://global.discourse-cdn.com/dynatrace/original/2X/5/59da6749f063c827323d4f4c75a85ee97fc34651.jpeg)