Intro information
| Component | Image | CPU | Memory | Restarts |
|---|---|---|---|---|
| botflow | 2000_Q1_V2_edb2fc7f | 600m | 1408Mi | 0 |
| engine | 2000_Q1_V2_cc72e86b | 1400m | 2560Mi | 0 |
| postgres | 15.3 | 1600m | 3000Mi | 0 |
| redis | 7.0.0 | 50m | 96Mi | 0 |
| ui | 2000_Q1_V2_99010997 | 50m | 128Mi | 0 |
| Agents | Ramp-up | Clients | Ramp-up | Time Under Load |
|---|---|---|---|---|
| 3 | 20 | 4 | 15 | 00:39:00 |
| Component | Image | CPU | Memory | Restarts |
|---|---|---|---|---|
| botflow | 2000_Q1_V1_4fc47431 | 600m | 1408Mi | 0 |
| engine | 2000_Q1_V1_e24b5a43 | 1400m | 2560Mi | 0 |
| postgres | 15.3 | 1600m | 3000Mi | 0 |
| redis | 7.0.0 | 50m | 96Mi | 0 |
| ui | 2000_Q1_V1_7fca0612 | 50m | 128Mi | 0 |
| Agents | Ramp-up | Clients | Ramp-up | Time Under Load |
|---|---|---|---|---|
| 3 | 20 | 4 | 15 | 00:29:00 |
1. Performance metrics
1.1 Transaction groups description
DB - Get last agent id data
DB - Get last contact id
DB - Get last conversation id
DB - Get agents tokens
/api/v1/accounts/{accountId}/agents
/api/v1/accounts/{accountId}/inbox_members
/api/v1/accounts/{accountId}/teams/{teamId}/team_members
/app/login
/auth/sign_in
host/
/auth/validate_token
/api/v1/accounts/{accountId}/
/api/v1/accounts/{accountId}/notification_settings
/api/v1/accounts/{accountId}/notification_settings/global
/api/v1/accounts/{accountId}/labels
/api/v1/accounts/{accountId}/custom_attribute_definitions
/api/v1/profile/availability
/auth/active_providers
/brand-assets/logo-small.png
/api/v1/accounts/{accountId}/contacts/(cont_id)
/api/v1/accounts/{accountId}/contacts/(cont_id)/conversations
/api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number}
/api/v1/accounts/{accountId}/inbox_members/{inboxId}
/api/v1/accounts/{accountId}/conversations/{conv_id}/labels
/api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all
/api/v1/accounts/1/dialogs/labels?dialogId[]=(dialog_id)
update_last_seen
check conversation status = open
/api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1
/api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me
/api/v1/accounts/(accountId)/conversations/(conv_id)
toggle_status resolved
check conversation status = resolved
Agent - Welcome msg
Agent - Reply msg 1
Agent - Reply msg 2
Agent - Reply msg 3
Agent - Reply msg 5
Agent - Reply msg 4
Bot - Agent request msg
Bot - Language menu msg
Bot - Entry msg
Client - CSAT answer
Client - Text msg 1
Client - Text msg 2
Client - Text msg 3
Client - Text msg 4
Client - Text msg 5
1.2 Summary
1.2.1 Summary data
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Database query ET mean | 1022.9 | 962.333 | +6.294% |
| Average Create Agents ET pct90 | 673.76 | 314.945 | +113.929% |
| Average Log In requests ET pct90 | 180.255 | 142.125 | +26.828% |
| Average Client Messages ET mean | 95.305 | 92.578 | +2.946% |
| Average Client Messages ET pct90 | 96.576 | 96.23 | +0.358% |
| Average Client Messages ET max | 97.928 | 97.533 | +0.405% |
| Average Request Throughput of all requests | 1.0 | 1.14 | -14.0% |
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Database query ET mean | 1022.9 | 962.333 | +6.294% |
| Average Create Agents ET pct90 | 553.653 | 286.0 | +93.585% |
| Average Log In requests ET pct90 | 180.255 | 142.125 | +26.828% |
| Average Client Messages ET mean | 80.796 | 96.046 | -15.878% |
| Average Client Messages ET pct90 | 82.327 | 99.574 | -17.321% |
| Average Client Messages ET max | 82.327 | 99.574 | -17.321% |
| Average Request Throughput of all requests | 0.987 | 1.094 | -9.781% |
In Create Agents transaction group was observed colossal (113.929%) handling time performance deterioration with new build in the responsible code block.
In Log In requests transaction group was observed significant (26.828%) handling time performance deterioration with new build in the responsible code block.
No transaction errors were observed in both builds.
In Create Agents transaction group was observed colossal (93.585%) handling time performance deterioration with new build in the responsible code block.
No transaction errors were observed in both builds.
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Create Agents ET pct90 | 1394.4 | 0.0 | N/A |
| Average Log In requests ET pct90 | 187.575 | 228.5 | -17.910% |
| Average Dashboard requests ET pct90 | 84.679 | 65.125 | +30.025% |
| Average Workflow Actions ET pct90 | 188.606 | 140.524 | +34.216% |
| Average Workflow Actions ET max | 227.328 | 203.306 | +11.816% |
| Average Agent Messages ET mean | 189.695 | 126.916 | +49.465% |
| Average Agent Messages ET pct90 | 379.363 | 269.772 | +40.624% |
| Average Agent Messages ET max | 452.135 | 341.09 | +32.556% |
| Average Client Messages ET mean | 69.041 | 61.869 | +11.592% |
| Average Client Messages ET pct90 | 101.433 | 100.751 | +0.677% |
| Average Client Messages ET max | 122.354 | 139.598 | -12.353% |
| Average Request Throughput of all requests | 1.117 | 1.342 | -16.766% |
| Average Request Throughput of all Agent messages | 0.86 | 1.048 | -17.939% |
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Create Agents ET pct90 | 1394.4 | 0.0 | N/A |
| Average Log In requests ET pct90 | 187.575 | 228.5 | -17.910% |
| Average Dashboard requests ET pct90 | 84.679 | 65.125 | +30.025% |
| Average Workflow Actions ET pct90 | 204.795 | 148.064 | +38.315% |
| Average Workflow Actions ET max | 242.783 | 201.604 | +20.426% |
| Average Agent Messages ET mean | 189.157 | 126.942 | +49.011% |
| Average Agent Messages ET pct90 | 378.015 | 270.256 | +39.873% |
| Average Agent Messages ET max | 450.518 | 343.009 | +31.343% |
| Average Client Messages ET mean | 71.093 | 64.034 | +11.024% |
| Average Client Messages ET pct90 | 100.917 | 99.531 | +1.393% |
| Average Client Messages ET max | 122.808 | 137.484 | -10.675% |
| Average Request Throughput of all requests | 1.026 | 1.219 | -15.833% |
| Average Request Throughput of all Agent messages | 0.86 | 1.05 | -18.095% |
In Log In requests transaction group was observed visible (17.91%) handling time performance improvement with new build in the responsible code block.
In Workflow Actions transaction group was observed significant (34.216%) handling time performance deterioration with new build in the responsible code block.
In Agent Messages transaction group was observed significant (40.624%) Engine handling time performance deterioration with new build.
In Agent Messages transaction group was observed significant (32.556%) deterioration in maximum transaction handling time with new build. Which, in return, points at increased instability of responsible code block and component in overall in handling large amounts of simultaneous requests.
Was observed significant (17.939%) deterioration of throughput of all transactions with new build. Which, in return, directly points at poorer performance of Engine and Database pair.
In Agent Messages transaction group was observed visible (39.873%) Engine handling time performance deterioration with new build.
In Agent Messages transaction group was observed visible (31.343%) deterioration in maximum transaction handling time with new build. Which, in return, points at increased instability of responsible code block and component in overall in handling large amounts of simultaneous requests.
Was observed visible (18.095%) deterioration of throughput of all transactions with new build. Which, in return, directly points at poorer performance of Engine and Database pair.
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Database query ET mean | 1022.9 | 962.333 | +6.294% |
| Average Create Agents ET pct90 | 750.971 | 339.476 | +121.215% |
| Average Log In requests ET pct90 | 182.695 | 170.917 | +6.891% |
| Average Dashboard requests ET pct90 | 75.173 | 62.708 | +19.878% |
| Average Workflow Actions ET pct90 | 182.6 | 135.903 | +34.361% |
| Average Workflow Actions ET max | 217.951 | 194.254 | +12.199% |
| Average Agent Messages ET mean | 190.213 | 125.481 | +51.587% |
| Average Agent Messages ET pct90 | 370.161 | 262.102 | +41.228% |
| Average Agent Messages ET max | 439.052 | 330.162 | +32.981% |
| Average Client Messages ET mean | 70.69 | 63.551 | +11.233% |
| Average Client Messages ET pct90 | 101.213 | 100.575 | +0.634% |
| Average Client Messages ET max | 120.82 | 137.296 | -12.000% |
| Average Request Throughput of all requests | 1.104 | 1.323 | -16.553% |
| Average Request Throughput of all Agent messages | 0.86 | 1.046 | -17.782% |
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Database query ET mean | 1022.9 | 962.333 | +6.294% |
| Average Create Agents ET pct90 | 553.653 | 286.0 | +93.585% |
| Average Log In requests ET pct90 | 182.695 | 170.917 | +6.891% |
| Average Dashboard requests ET pct90 | 75.075 | 63.013 | +19.142% |
| Average Workflow Actions ET pct90 | 201.507 | 144.391 | +39.556% |
| Average Workflow Actions ET max | 236.209 | 193.722 | +21.932% |
| Average Agent Messages ET mean | 188.865 | 125.597 | +50.374% |
| Average Agent Messages ET pct90 | 366.937 | 262.859 | +39.595% |
| Average Agent Messages ET max | 435.597 | 332.368 | +31.059% |
| Average Client Messages ET mean | 72.034 | 65.192 | +10.495% |
| Average Client Messages ET pct90 | 100.6 | 99.428 | +1.179% |
| Average Client Messages ET max | 120.997 | 135.34 | -10.598% |
| Average Request Throughput of all requests | 1.098 | 1.228 | -10.586% |
| Average Request Throughput of all Agent messages | 0.86 | 1.047 | -17.861% |
In Create Agents transaction group was observed colossal (121.215%) handling time performance deterioration with new build in the responsible code block.
In Workflow Actions transaction group was observed significant (34.361%) handling time performance deterioration with new build in the responsible code block.
In Agent Messages transaction group was observed significant (41.228%) Engine handling time performance deterioration with new build.
In Agent Messages transaction group was observed significant (32.981%) deterioration in maximum transaction handling time with new build. Which, in return, points at increased instability of responsible code block and component in overall in handling large amounts of simultaneous requests.
Was observed significant (17.782%) deterioration of throughput of all transactions with new build. Which, in return, directly points at poorer performance of Engine and Database pair.
In Create Agents transaction group was observed colossal (93.585%) handling time performance deterioration with new build in the responsible code block.
In Agent Messages transaction group was observed visible (39.595%) Engine handling time performance deterioration with new build.
In Agent Messages transaction group was observed visible (31.059%) deterioration in maximum transaction handling time with new build. Which, in return, points at increased instability of responsible code block and component in overall in handling large amounts of simultaneous requests.
Was observed visible (17.861%) deterioration of throughput of all transactions with new build. Which, in return, directly points at poorer performance of Engine and Database pair.
1.2.2 Summary spread
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Database query ET spread of mean | 257.701 | 137.948 | +86.81% |
| Average Create Agents ET spread of pct90 | 166.554 | 87.974 | +89.322% |
| Average Log In requests ET spread of pct90 | 47.823 | 38.731 | +23.475% |
| Average Client Messages ET spread of mean | 38.331 | 24.168 | +58.602% |
| Average Client Messages ET spread of pct90 | 24.532 | 17.637 | +39.094% |
| Average Client Messages ET spread of max | 18.912 | 24.207 | -21.874% |
| Average Request Throughput of all requests spread | 0.267 | 0.323 | -17.337% |
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Database query ET spread of mean | 227.587 | 220.969 | +2.995% |
| Average Create Agents ET spread of pct90 | 118.257 | 72.378 | +63.388% |
| Average Log In requests ET spread of pct90 | 51.18 | 17.308 | +195.701% |
| Average Client Messages ET spread of mean | 22.529 | 19.325 | +16.580% |
| Average Client Messages ET spread of pct90 | 23.796 | 22.633 | +5.139% |
| Average Client Messages ET spread of max | 24.934 | 21.59 | +15.489% |
| Average Request Throughput of all requests spread | 0.3 | 0.227 | +32.159% |
In Create Agents transaction group was observed colossal (89.322%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Log In requests transaction group was observed significant (23.475%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Client Messages transaction group was observed massive (39.094%) increase in volatility of handling time data dispersion with new build. Which, in return, directly points at poorer stability of Botflow.
In Client Messages transaction group was observed significant (21.874%) decrease in volatility of maximum transaction handling time data with new build. Which, in return, points at better efficiency of responsible code block.
In Create Agents transaction group was observed colossal (63.388%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Log In requests transaction group was observed colossal (195.701%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Client Messages transaction group was observed visible (5.139%) increase in volatility of handling time data dispersion with new build. Which, in return, directly points at poorer stability of Botflow.
In Client Messages transaction group was observed significant (15.489%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Create Agents ET spread of pct90 | 430.894 | 87.386 | +393.093% |
| Average Log In requests ET spread of pct90 | 77.579 | 44.322 | +75.035% |
| Average Dashboard requests ET spread of pct90 | 35.129 | 12.451 | +182.138% |
| Average Workflow Actions ET spread of pct90 | 36.429 | 18.429 | +97.672% |
| Average Workflow Actions ET spread of max | 82.498 | 28.2 | +192.546% |
| Average Agent Messages ET spread of mean | 37.584 | 35.918 | +4.638% |
| Average Agent Messages ET spread of pct90 | 127.958 | 34.137 | +274.837% |
| Average Agent Messages ET spread of max | 83.694 | 63.615 | +31.563% |
| Average Client Messages ET spread of mean | 28.149 | 10.313 | +172.947% |
| Average Client Messages ET spread of pct90 | 21.044 | 28.959 | -27.332% |
| Average Client Messages ET spread of max | 40.025 | 35.635 | +12.319% |
| Average Request Throughput of all requests spread | 0.304 | 0.3 | +1.333% |
| Average Request Throughput of all Agent messages spread | 0.184 | 0.178 | +3.371% |
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Create Agents ET spread of pct90 | 557.595 | 112.125 | +397.298% |
| Average Log In requests ET spread of pct90 | 56.657 | 41.366 | +36.965% |
| Average Dashboard requests ET spread of pct90 | 22.403 | 14.358 | +56.031% |
| Average Workflow Actions ET spread of pct90 | 55.898 | 29.541 | +89.222% |
| Average Workflow Actions ET spread of max | 66.813 | 44.936 | +48.685% |
| Average Agent Messages ET spread of mean | 56.113 | 26.076 | +115.190% |
| Average Agent Messages ET spread of pct90 | 130.471 | 66.742 | +95.486% |
| Average Agent Messages ET spread of max | 119.85 | 71.539 | +67.531% |
| Average Client Messages ET spread of mean | 20.767 | 14.337 | +44.849% |
| Average Client Messages ET spread of pct90 | 35.113 | 22.669 | +54.894% |
| Average Client Messages ET spread of max | 32.923 | 32.429 | +1.523% |
| Average Request Throughput of all requests spread | 0.316 | 0.248 | +95.506% |
| Average Request Throughput of all Agent messages spread | 0.257 | 0.22 | +16.818% |
In Create Agents transaction group was observed colossal (393.093%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Log In requests transaction group was observed colossal (75.035%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Dashboard requests transaction group was observed colossal (182.138%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Workflow Actions transaction group was observed colossal (97.672%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Workflow Actions transaction group was observed colossal (192.546%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
In Agent Messages transaction group was observed colossal (274.837%) increase in volatility of handling time data dispersion with new build. Which, in return, directly points at poorer stability of Engine.
In Agent Messages transaction group was observed massive (31.563%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
In Client Messages transaction group was observed massive (27.332%) decrease in volatility of handling time data dispersion with new build. Which, in return, directly points at better stability of Botflow.
In Client Messages transaction group was observed significant (12.319%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
In Create Agents transaction group was observed colossal (397.298%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Log In requests transaction group was observed massive (36.965%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Dashboard requests transaction group was observed colossal (56.031%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Workflow Actions transaction group was observed colossal (89.222%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Workflow Actions transaction group was observed massive (48.685%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
In Agent Messages transaction group was observed colossal (95.486%) increase in volatility of handling time data dispersion with new build. Which, in return, directly points at poorer stability of Engine.
In Agent Messages transaction group was observed colossal (67.531%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
In Client Messages transaction group was observed colossal (54.894%) increase in volatility of handling time data dispersion with new build. Which, in return, directly points at poorer stability of Botflow.
Was observed significant (16.818%) increase in volatility of throughput of all transactions with new build. Which, in return, directly points at increased instability of the system in overall. The throughput of agents messages requests took a huge part in instability.
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Database query ET spread of mean | 275.875 | 204.493 | +34.907% |
| Average Create Agents ET spread of pct90 | 271.664 | 51.201 | +430.583% |
| Average Log In requests ET spread of pct90 | 42.546 | 29.353 | +44.946% |
| Average Dashboard requests ET spread of pct90 | 26.094 | 7.754 | +236.523% |
| Average Workflow Actions ET spread of pct90 | 72.839 | 18.56 | +292.452% |
| Average Workflow Actions ET spread of max | 91.377 | 31.795 | +187.394% |
| Average Agent Messages ET spread of mean | 73.238 | 35.685 | +105.235% |
| Average Agent Messages ET spread of pct90 | 73.136 | 78.321 | -6.620% |
| Average Agent Messages ET spread of max | 146.439 | 79.96 | +83.14% |
| Average Client Messages ET spread of mean | 23.281 | 8.739 | +166.403% |
| Average Client Messages ET spread of pct90 | 23.494 | 19.07 | +23.199% |
| Average Client Messages ET spread of max | 36.223 | 36.786 | -1.530% |
| Average Request Throughput of all requests spread | 0.446 | 0.28 | +59.286% |
| Average Request Throughput of all Agent messages spread | 0.159 | 0.151 | +5.298% |
| Metric Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Average Database query ET spread of mean | 322.954 | 143.821 | +124.553% |
| Average Create Agents ET spread of pct90 | 201.612 | 68.954 | +192.386% |
| Average Log In requests ET spread of pct90 | 41.706 | 41.922 | -0.515% |
| Average Dashboard requests ET spread of pct90 | 22.78 | 13.534 | +68.317% |
| Average Workflow Actions ET spread of pct90 | 66.672 | 31.169 | +113.905% |
| Average Workflow Actions ET spread of max | 73.294 | 37.049 | +97.830% |
| Average Agent Messages ET spread of mean | 57.671 | 28.844 | +99.941% |
| Average Agent Messages ET spread of pct90 | 114.542 | 58.026 | +97.398% |
| Average Agent Messages ET spread of max | 117.224 | 66.271 | +76.886% |
| Average Client Messages ET spread of mean | 20.323 | 14.362 | +41.505% |
| Average Client Messages ET spread of pct90 | 29.675 | 18.48 | +60.579% |
| Average Client Messages ET spread of max | 35.57 | 29.335 | +21.254% |
| Average Request Throughput of all requests spread | 0.322 | 0.255 | +26.275% |
| Average Request Throughput of all Agent messages spread | 0.287 | 0.216 | +32.870% |
In Create Agents transaction group was observed colossal (430.583%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Log In requests transaction group was observed massive (44.946%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Dashboard requests transaction group was observed colossal (236.523%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Workflow Actions transaction group was observed colossal (292.452%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Workflow Actions transaction group was observed colossal (187.394%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
In Agent Messages transaction group was observed visible (6.62%) decrease in volatility of handling time data dispersion with new build. Which, in return, directly points at better stability of Engine.
In Agent Messages transaction group was observed colossal (83.14%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
In Client Messages transaction group was observed significant (23.199%) increase in volatility of handling time data dispersion with new build. Which, in return, directly points at poorer stability of Botflow.
Was observed visible (5.298%) increase in volatility of throughput of all transactions with new build. Which, in return, directly points at increased instability of the system in overall. The throughput of agents messages requests took a huge part in instability.
In Create Agents transaction group was observed colossal (192.386%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Dashboard requests transaction group was observed colossal (68.317%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Workflow Actions transaction group was observed colossal (113.905%) increase in volatility of handling time data dispersion with new build. Which, in return, points at poorer stability of responsible code block.
In Workflow Actions transaction group was observed colossal (97.83%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
In Agent Messages transaction group was observed colossal (97.398%) increase in volatility of handling time data dispersion with new build. Which, in return, directly points at poorer stability of Engine.
In Agent Messages transaction group was observed colossal (76.886%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
In Client Messages transaction group was observed colossal (60.579%) increase in volatility of handling time data dispersion with new build. Which, in return, directly points at poorer stability of Botflow.
In Client Messages transaction group was observed significant (21.254%) increase in volatility of maximum transaction handling time data with new build. Which, in return, points at non-efficiency of responsible code block.
Was observed massive (32.87%) increase in volatility of throughput of all transactions with new build. Which, in return, directly points at increased instability of the system in overall. Additionally, the throughput of agents messages requests took a lesser part in instability.
1.3 Transaction Data
1.3.1 Data by transaction
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| DB - Get agents tokens | 85.86 | 85.0 | +1.012% |
| DB - Get last contact id | 85.86 | 78.0 | +10.077% |
| DB - Get last conversation id | 2896.98 | 2724.0 | +6.35% |
'DB - Get last conversation id' transaction with weight '94.40%' has the highest value of ET in the group '2896.98'.
This means that this transaction can be viewed as a bottleneck factor.
'DB - Get agents tokens' transaction with weight '2.80%' has the lowest value of ET in the group '85.86'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '3374.07%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'DB - Get last contact id' transaction with weight '2.80%' has the highest value of difference in the group '+10.077%'.
This means that this transaction can be viewed as a target for improvement.
'DB - Get agents tokens' transaction with weight '2.80%' has the lowest value of difference in the group '+1.012%'.
The '+' character indicates an increase in ET, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/agents | 1394.4 | 684.0 | +103.86% |
| /api/v1/accounts/{accountId}/inbox_members | 137.76 | 87.0 | +58.345% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 128.8 | 87.0 | +48.046% |
'/api/v1/accounts/{accountId}/agents' transaction with weight '83.95%' has the highest value of ET in the group '1394.4'.
This means that this transaction can be viewed as a bottleneck factor.
'/api/v1/accounts/{accountId}/teams/{teamId}/team_members' transaction with weight '7.75%' has the lowest value of ET in the group '128.8'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '1082.61%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/agents' transaction with weight '83.95%' has the highest value of difference in the group '+103.86%'.
This means that this transaction can be viewed as a target for improvement.
'/api/v1/accounts/{accountId}/teams/{teamId}/team_members' transaction with weight '7.75%' has the lowest value of difference in the group '+48.046%'.
The '+' character indicates an increase in ET, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '55.81%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /app/login | 170.8 | 141.0 | +21.135% |
| /auth/sign_in | 387.96 | 278.0 | +39.554% |
| /auth/validate_token | 108.58 | 109.5 | -0.84% |
| host/ | 53.68 | 40.0 | +34.2% |
'/auth/sign_in' transaction with weight '53.81%' has the highest value of ET in the group '387.96'.
This means that this transaction can be viewed as a bottleneck factor.
'host/' transaction with weight '7.45%' has the lowest value of ET in the group '53.68'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '722.73%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'/auth/sign_in' transaction with weight '53.81%' has the highest value of difference in the group '+39.554%'.
This means that this transaction can be viewed as a target for improvement.
'/auth/validate_token' transaction with weight '15.06%' has the lowest value of difference in the group '-0.84%'.
The special notice can be given to the absolute value '40.39%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 147.163 | 130.833 | +12.482% |
| Bot - Entry msg | 60.95 | 56.5 | +7.876% |
| Bot - Language menu msg | 67.487 | 59.333 | +13.743% |
'Bot - Agent request msg' transaction with weight '53.40%' has the highest value of ET in the group '147.163'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Bot - Entry msg' transaction with weight '22.12%' has the lowest value of ET in the group '60.95'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '241.45%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Bot - Language menu msg' transaction with weight '24.49%' has the highest value of difference in the group '+13.743%'.
This means that this transaction can be viewed as a target for improvement.
'Bot - Entry msg' transaction with weight '22.12%' has the lowest value of difference in the group '+7.876%'.
The '+' character indicates an increase in ET, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 153.7 | 141.667 | +8.494% |
| Bot - Entry msg | 62.54 | 57.0 | +9.719% |
| Bot - Language menu msg | 69.96 | 62.0 | +12.839% |
'Bot - Agent request msg' transaction with weight '53.70%' has the highest value of ET in the group '153.7'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Bot - Entry msg' transaction with weight '21.85%' has the lowest value of ET in the group '62.54'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '245.76%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Bot - Language menu msg' transaction with weight '24.44%' has the highest value of difference in the group '+12.839%'.
This means that this transaction can be viewed as a target for improvement.
'Bot - Agent request msg' transaction with weight '53.70%' has the lowest value of difference in the group '+8.494%'.
The '+' character indicates an increase in ET, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 153.7 | 141.667 | +8.494% |
| Bot - Entry msg | 62.54 | 57.0 | +9.719% |
| Bot - Language menu msg | 69.96 | 62.0 | +12.839% |
'Bot - Agent request msg' transaction with weight '53.70%' has the highest value of ET in the group '153.7'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Bot - Entry msg' transaction with weight '21.85%' has the lowest value of ET in the group '62.54'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '245.76%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Bot - Language menu msg' transaction with weight '24.44%' has the highest value of difference in the group '+12.839%'.
This means that this transaction can be viewed as a target for improvement.
'Bot - Agent request msg' transaction with weight '53.70%' has the lowest value of difference in the group '+8.494%'.
The '+' character indicates an increase in ET, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/agents | 2.15 | 1.667 | +28.974% |
| /api/v1/accounts/{accountId}/inbox_members | 2.58 | 1.5 | +72.0% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/inboxes | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/teams | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 2.58 | 1.5 | +72.0% |
| /app/login | 0.86 | 1.0 | -14.0% |
| /auth/sign_in | 0.86 | 1.0 | -14.0% |
| /auth/validate_token | 0.86 | 1.0 | -14.0% |
| Bot - Agent request msg | 1.72 | 2.0 | -14.0% |
| Bot - Entry msg | 1.29 | 1.5 | -14.0% |
| Bot - Language menu msg | 1.29 | 1.5 | -14.0% |
| host/ | 0.86 | 1.0 | -14.0% |
'/api/v1/accounts/{accountId}/inbox_members' transaction with weight '14.63%' has the highest value of requests per time bucket in the group - '2.58'.
Thus, this transaction can be viewed as the most used one in at least one time bucket.",
'/api/v1/accounts/{accountId}/inbox_members/{inboxId}' transaction with weight '4.88%' has the lowest value of requests per time bucket in the group - '0.86'.
Thus, this transaction can be viewed as the least used one at least in one time bucket.
'/api/v1/accounts/{accountId}/inbox_members' transaction with weight '14.63%' has the highest value of difference in the group '+72.0%'.
This transaction can be viewed as a example of most improvement.
'/api/v1/accounts/{accountId}/inbox_members/{inboxId}' transaction with weight '4.88%' has the lowest value of difference in the group '-14.0%'.
This transaction can be viewed as a target for improvement.
The special notice can be given to the absolute value '86.00%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
Improvements or deteriorations in throughput of the respective transactions is result of these transactions decrease or increase of ET timings.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Client - Text msg 5 | 0.0 | 0.0 | 0% |
| Client - Text msg 4 | 0.0 | 0.0 | 0% |
| Client - Text msg 3 | 0.0 | 0.0 | 0% |
| Client - Text msg 2 | 0.0 | 0.0 | 0% |
| Client - Text msg 1 | 0.0 | 0.0 | 0% |
| Client - CSAT answer | 0.0 | 0.0 | 0% |
| Bot - Agent request msg | 0.0 | 0.0 | 0% |
| Bot - Entry msg | 0.0 | 0.0 | 0% |
| Bot - Language menu msg | 0.0 | 0.0 | 0% |
| Agent - Reply msg 1 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 2 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 3 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 4 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 5 | 0.0 | 0.0 | 0% |
| Agent - Welcome msg | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/ | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/agents | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 0.0 | 0.0 | 0% |
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/dialogs/labels?dialogId[]=(dialog_id) | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/custom_filters?filter_type=conversation | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/inbox_members | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/inboxes | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/labels | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/notification_settings | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/notification_settings/global | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/notifications/unread_count | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/teams | 0.0 | 0.0 | 0% |
| /api/v1/notification_subscriptions | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 0.0 | 0.0 | 0% |
| /api/v1/profile/availability | 0.0 | 0.0 | 0% |
| /app/login | 0.0 | 0.0 | 0% |
| /auth/validate_token | 0.0 | 0.0 | 0% |
| /auth/sign_in | 0.0 | 0.0 | 0% |
| /auth/active_providers | 0.0 | 0.0 | 0% |
| check conversation status = open | 0.0 | 0.0 | 0% |
| check conversation status = resolved | 0.0 | 0.0 | 0% |
| toggle_status resolved | 0.0 | 0.0 | 0% |
| update_last_seen | 0.0 | 0.0 | 0% |
| host/ | 0.0 | 0.0 | 0% |
| DB - Get last conversation id | 0.0 | 0.0 | 0% |
| DB - Get last contact id | 0.0 | 0.0 | 0% |
| DB - Get agents tokens | 0.0 | 0.0 | 0% |
| /brand-assets/logo-small.png | 0.0 | 0.0 | 0% |
No charts available.
No transaction errors were observed in both builds.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/agents | 1394.4 | 0.0 | N/A |
'/api/v1/accounts/{accountId}/agents' transaction execution time desynchronization detected between builds - Build_v1 has zero ET value.
This can be possible when execution in one of the builds is too fast or too slow. Does require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /app/login | 170.8 | 141.0 | +21.135% |
| /auth/sign_in | 408.7 | 559.0 | -26.887% |
| /auth/validate_token | 108.58 | 164.0 | -33.793% |
| host/ | 62.22 | 50.0 | +24.44% |
'/auth/sign_in' transaction with weight '54.47%' has the highest value of ET in the group '408.7'.
This means that this transaction can be viewed as a bottleneck factor.
'host/' transaction with weight '8.29%' has the lowest value of ET in the group '62.22'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '656.86%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'host/' transaction with weight '8.29%' has the highest value of difference in the group '+24.44%'.
This means that this transaction can be viewed as a target for improvement.
'/auth/validate_token' transaction with weight '14.47%' has the lowest value of difference in the group '-33.793%'.
The special notice can be given to the absolute value '58.23%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/ | 322.92 | 352.0 | -8.261% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions | 360.36 | 220.0 | +63.8% |
| /api/v1/accounts/{accountId}/labels | 594.36 | 284.0 | +109.282% |
| /api/v1/accounts/{accountId}/notification_settings | 341.64 | 336.0 | +1.679% |
| /api/v1/accounts/{accountId}/notification_settings/global | 238.68 | 180.0 | +32.6% |
| /api/v1/profile/availability | 425.88 | 388.0 | +9.763% |
| /auth/active_providers | 229.32 | 172.0 | +33.326% |
| /brand-assets/logo-small.png | 196.56 | 152.0 | +29.316% |
'/api/v1/accounts/{accountId}/labels' transaction with weight '21.93%' has the highest value of ET in the group '594.36'.
This means that this transaction can be viewed as a bottleneck factor.
'/brand-assets/logo-small.png' transaction with weight '7.25%' has the lowest value of ET in the group '196.56'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '302.38%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/labels' transaction with weight '21.93%' has the highest value of difference in the group '+109.282%'.
This means that this transaction can be viewed as a target for improvement.
'/api/v1/accounts/{accountId}/' transaction with weight '11.92%' has the lowest value of difference in the group '-8.261%'.
The special notice can be given to the absolute value '117.54%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 113.082 | 129.591 | -12.739% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 132.1 | 91.738 | +43.997% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 243.287 | 156.888 | +55.07% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 84.926 | 84.398 | +0.626% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 144.619 | 81.124 | +78.269% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 144.276 | 75.106 | +92.097% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 145.176 | 153.048 | -5.143% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 96.122 | 88.224 | +8.952% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 101.614 | 101.724 | -0.108% |
| check conversation status = open | 150.161 | 141.172 | +6.367% |
| check conversation status = resolved | 135.73 | 158.87 | -14.565% |
| toggle_status resolved | 1063.019 | 540.955 | +96.508% |
| update_last_seen | 108.217 | 122.0 | -11.298% |
'toggle_status resolved' transaction with weight '39.93%' has the highest value of ET in the group '1063.019'.
This means that this transaction can be viewed as a bottleneck factor.
'/api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me' transaction with weight '3.19%' has the lowest value of ET in the group '84.926'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '1251.70%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'toggle_status resolved' transaction with weight '39.93%' has the highest value of difference in the group '+96.508%'.
This means that this transaction can be viewed as a target for improvement.
'check conversation status = resolved' transaction with weight '5.10%' has the lowest value of difference in the group '-14.565%'.
The special notice can be given to the absolute value '111.07%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 165.211 | 142.912 | +15.603% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 149.371 | 127.706 | +16.965% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 303.442 | 167.441 | +81.223% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 112.2 | 141.018 | -20.436% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 165.792 | 85.088 | +94.848% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 183.85 | 117.441 | +56.547% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 219.797 | 273.24 | -19.559% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 105.019 | 103.059 | +1.902% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 112.728 | 122.147 | -7.711% |
| check conversation status = open | 221.045 | 150.531 | +46.844% |
| check conversation status = resolved | 137.452 | 166.733 | -17.562% |
| toggle_status resolved | 1136.003 | 631.517 | +79.885% |
| update_last_seen | 144.266 | 392.02 | -63.199% |
'toggle_status resolved' transaction with weight '35.99%' has the highest value of ET in the group '1136.003'.
This means that this transaction can be viewed as a bottleneck factor.
'/api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all' transaction with weight '3.33%' has the lowest value of ET in the group '105.019'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '1081.71%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/conversations/{conv_id}/labels' transaction with weight '5.25%' has the highest value of difference in the group '+94.848%'.
This means that this transaction can be viewed as a target for improvement.
'update_last_seen' transaction with weight '4.57%' has the lowest value of difference in the group '-63.199%'.
The special notice can be given to the absolute value '158.05%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 255.358 | 124.69 | +104.794% |
| Agent - Reply msg 2 | 173.89 | 127.811 | +36.052% |
| Agent - Reply msg 3 | 162.523 | 132.939 | +22.254% |
| Agent - Reply msg 4 | 168.454 | 149.503 | +12.676% |
| Agent - Reply msg 5 | 133.456 | 114.283 | +16.777% |
| Agent - Welcome msg | 241.26 | 112.423 | +114.6% |
'Agent - Reply msg 1' transaction with weight '22.50%' has the highest value of ET in the group '255.358'.
This means that this transaction can be viewed as a bottleneck factor.
'Agent - Reply msg 5' transaction with weight '11.76%' has the lowest value of ET in the group '133.456'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '191.34%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '21.26%' has the highest value of difference in the group '+114.6%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 4' transaction with weight '14.84%' has the lowest value of difference in the group '+12.676%'.
The '+' character indicates an increase in ET, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '101.92%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 493.39 | 275.153 | +79.315% |
| Agent - Reply msg 2 | 364.401 | 262.33 | +38.909% |
| Agent - Reply msg 3 | 267.323 | 261.294 | +2.307% |
| Agent - Reply msg 4 | 337.434 | 358.37 | -5.842% |
| Agent - Reply msg 5 | 227.208 | 250.044 | -9.133% |
| Agent - Welcome msg | 578.335 | 214.347 | +169.813% |
'Bot - Agent request msg' transaction with weight '16.54%' has the highest value of ET in the group '150.242'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Bot - Entry msg' transaction with weight '7.29%' has the lowest value of ET in the group '66.231'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '226.85%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Client - Text msg 1' transaction with weight '9.57%' has the highest value of difference in the group '+16.246%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '9.92%' has the lowest value of difference in the group '-39.135%'.
The special notice can be given to the absolute value '55.38%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 534.865 | 383.567 | +39.445% |
| Agent - Reply msg 2 | 495.42 | 300.061 | +65.106% |
| Agent - Reply msg 3 | 315.963 | 303.091 | +4.247% |
| Agent - Reply msg 4 | 412.98 | 525.133 | -21.357% |
| Agent - Reply msg 5 | 258.48 | 286.938 | -9.918% |
| Agent - Welcome msg | 685.4 | 259.267 | +164.361% |
'Agent - Welcome msg' transaction with weight '25.36%' has the highest value of ET in the group '685.4'.
This means that this transaction can be viewed as a bottleneck factor.
'Agent - Reply msg 5' transaction with weight '9.56%' has the lowest value of ET in the group '258.48'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '265.17%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '25.36%' has the highest value of difference in the group '+164.361%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 4' transaction with weight '15.28%' has the lowest value of difference in the group '-21.357%'.
The special notice can be given to the absolute value '185.72%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 136.742 | 125.248 | +9.177% |
| Bot - Entry msg | 61.311 | 56.468 | +8.577% |
| Bot - Language menu msg | 65.065 | 58.52 | +11.184% |
| Client - CSAT answer | 60.274 | 66.675 | -9.6% |
| Client - Text msg 1 | 56.188 | 48.486 | +15.885% |
| Client - Text msg 2 | 72.227 | 56.675 | +27.441% |
| Client - Text msg 3 | 61.049 | 53.016 | +15.152% |
| Client - Text msg 4 | 71.128 | 62.275 | +14.216% |
| Client - Text msg 5 | 55.856 | 48.947 | +14.115% |
'Bot - Agent request msg' transaction with weight '21.37%' has the highest value of ET in the group '136.742'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Client - Text msg 5' transaction with weight '8.73%' has the lowest value of ET in the group '55.856'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '244.81%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Client - Text msg 2' transaction with weight '11.29%' has the highest value of difference in the group '+27.441%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '9.42%' has the lowest value of difference in the group '-9.6%'.
The special notice can be given to the absolute value '37.04%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 150.242 | 137.671 | +9.131% |
| Bot - Entry msg | 66.231 | 59.932 | +10.51% |
| Bot - Language menu msg | 72.716 | 67.864 | +7.15% |
| Client - CSAT answer | 90.118 | 148.063 | -39.135% |
| Client - Text msg 1 | 86.88 | 74.738 | +16.246% |
| Client - Text msg 2 | 133.98 | 122.47 | +9.398% |
| Client - Text msg 3 | 98.686 | 87.17 | +13.211% |
| Client - Text msg 4 | 129.881 | 124.324 | +4.47% |
| Client - Text msg 5 | 79.523 | 73.547 | +8.125% |
'Bot - Agent request msg' transaction with weight '16.54%' has the highest value of ET in the group '150.242'.
This means that this transaction can be viewed as a bottleneck factor.
'Bot - Entry msg' transaction with weight '7.29%' has the lowest value of ET in the group with value '66.231'.
This means that this transaction can be viewed as the least lightweight in the group.
The special notice can be given to the '226.85%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Client - Text msg 1' transaction with weight '9.57%' has the highest value of difference in the group '+16.246%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '9.92%' has the lowest value of difference in the group '-39.135%'.
The special notice can be given to the absolute value '55.381 percentage points' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance changes may require further investigation.
-----------------------------------
'Bot - Agent request msg' transaction with weight '16.54%' has the highest value of ET in the group '150.242'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Bot - Entry msg' transaction with weight '7.29%' has the lowest value of ET in the group '66.231'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '226.85%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Client - Text msg 1' transaction with weight '9.57%' has the highest value of difference in the group '+16.246%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '9.92%' has the lowest value of difference in the group '-64.299%'.
The special notice can be given to the absolute value '80.55%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 177.881 | 153.0 | +16.262% |
| Bot - Entry msg | 76.445 | 112.591 | -32.104% |
| Bot - Language menu msg | 127.886 | 96.364 | +32.711% |
| Client - CSAT answer | 144.072 | 235.0 | -38.693% |
| Client - Text msg 1 | 92.22 | 91.147 | +1.177% |
| Client - Text msg 2 | 144.075 | 191.424 | -24.735% |
| Client - Text msg 3 | 124.108 | 104.833 | +18.386% |
| Client - Text msg 4 | 138.021 | 169.0 | -18.331% |
| Client - Text msg 5 | 80.56 | 84.0 | -4.095% |
'Bot - Agent request msg' transaction with weight '16.09%' has the highest value of ET in the group '177.881'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Bot - Entry msg' transaction with weight '6.92%' has the lowest value of ET in the group '76.445'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '232.69%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Bot - Language menu msg' transaction with weight '11.57%' has the highest value of difference in the group '+32.711%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '13.04%' has the lowest value of difference in the group '-38.693%'.
The special notice can be given to the absolute value '71.40%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/ | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/agents | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 2.048 | 2.455 | -16.578% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 1.191 | 1.44 | -17.292% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/custom_filters?filter_type=conversation | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/dialogs/labels?dialogId[]=(dialog_id) | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/inboxes | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/labels | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/notification_settings | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/notification_settings/global | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/notifications/unread_count | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/teams | 0.86 | 1.0 | -14.0% |
| /api/v1/notification_subscriptions | 0.86 | 1.0 | -14.0% |
| /api/v1/profile/availability | 0.86 | 1.0 | -14.0% |
| /app/login | 0.86 | 1.0 | -14.0% |
| /auth/active_providers | 0.86 | 1.0 | -14.0% |
| /auth/sign_in | 0.86 | 1.0 | -14.0% |
| /auth/validate_token | 0.86 | 1.0 | -14.0% |
| Agent - Reply msg 1 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 2 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 3 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 4 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 5 | 0.86 | 1.1 | -21.818% |
| Agent - Welcome msg | 0.86 | 1.1 | -21.818% |
| Bot - Agent request msg | 2.795 | 3.429 | -18.489% |
| Bot - Entry msg | 2.782 | 3.227 | -13.790% |
| Bot - Language menu msg | 2.782 | 3.409 | -18.392% |
| Client - CSAT answer | 0.86 | 1.1 | -21.818% |
| Client - Text msg 1 | 0.86 | 1.1 | -21.818% |
| Client - Text msg 2 | 0.86 | 1.1 | -21.818% |
| Client - Text msg 3 | 0.86 | 1.1 | -21.818% |
| Client - Text msg 4 | 0.86 | 1.1 | -21.818% |
| Client - Text msg 5 | 0.86 | 1.1 | -21.818% |
| check conversation status = open | 0.86 | 1.063 | -19.097% |
| check conversation status = resolved | 0.86 | 1.067 | -19.4% |
| host/ | 0.86 | 1.0 | -14.0% |
| toggle_status resolved | 0.86 | 1.103 | -22.031% |
'Bot - Agent request msg' transaction with weight '6.31%' has the highest value of requests per time bucket in the group - '2.795'.
Thus, this transaction can be viewed as the most used one in at least one time bucket.
'/api/v1/accounts/(accountId)/conversations/(conv_id)' transaction with weight '1.94%' has the lowest value of requests per time bucket in the group - '0.86'.
Thus, this transaction can be viewed as the least used one at least in one time bucket.
'Bot - Entry msg' transaction with weight '6.28%' has the highest value of difference in the group '-13.79%'.
Where negative number shows degradation in the whole group.
'Client - Text msg 3' transaction with weight '1.94%' has the lowest value of difference in the group '-24.095%'.
This transaction can be viewed as a target for improvement.
Improvements or deteriorations in throughput of the respective transactions is result of these transactions decrease or increase of ET timings.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 0.86 | 1.1 | -27.907% |
| Agent - Reply msg 2 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 3 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 4 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 5 | 0.86 | 1.1 | -21.818% |
| Agent - Welcome msg | 0.86 | 1.1 | -21.818% |
'Agent - Reply msg 1' transaction with weight '16.67%' has the highest value of requests per time bucket in the group - '0.86'.
Thus, this transaction can be viewed as the most used one in at least one time bucket.
'Agent - Reply msg 1' transaction with weight '16.67%' has the lowest value of requests per time bucket in the group - '0.86'.
Thus, this transaction can be viewed as the least used one at least in one time bucket.
'Agent - Reply msg 1' transaction with weight '16.67%' has the highest value of difference in the group '-21.818%'.
This transaction can be viewed as a target for improvement.
'Agent - Reply msg 1' transaction with weight '16.67%' has the lowest value of difference in the group '-21.818%'.
This transaction can be viewed as a target for improvement.
Improvements or deteriorations in throughput of the respective transactions is result of these transactions decrease or increase of ET timings.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Client - Text msg 5 | 0.0 | 0.0 | 0% |
| Client - Text msg 4 | 0.0 | 0.0 | 0% |
| Client - Text msg 3 | 0.0 | 0.0 | 0% |
| Client - Text msg 2 | 0.0 | 0.0 | 0% |
| Client - Text msg 1 | 0.0 | 0.0 | 0% |
| Client - CSAT answer | 0.0 | 0.0 | 0% |
| Bot - Agent request msg | 0.0 | 0.0 | 0% |
| Bot - Entry msg | 0.0 | 0.0 | 0% |
| Bot - Language menu msg | 0.0 | 0.0 | 0% |
| Agent - Reply msg 1 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 2 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 3 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 4 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 5 | 0.0 | 0.0 | 0% |
| Agent - Welcome msg | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/ | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/agents | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 0.0 | 0.0 | 0% |
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/dialogs/labels?dialogId[]=(dialog_id) | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/custom_filters?filter_type=conversation | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/inbox_members | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/inboxes | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/labels | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/notification_settings | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/notification_settings/global | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/notifications/unread_count | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/teams | 0.0 | 0.0 | 0% |
| /api/v1/notification_subscriptions | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 0.0 | 0.0 | 0% |
| /api/v1/profile/availability | 0.0 | 0.0 | 0% |
| /app/login | 0.0 | 0.0 | 0% |
| /auth/validate_token | 0.0 | 0.0 | 0% |
| /auth/sign_in | 0.0 | 0.0 | 0% |
| /auth/active_providers | 0.0 | 0.0 | 0% |
| check conversation status = open | 0.0 | 0.0 | 0% |
| check conversation status = resolved | 0.0 | 0.0 | 0% |
| toggle_status resolved | 0.0 | 0.0 | 0% |
| update_last_seen | 0.0 | 0.0 | 0% |
| host/ | 0.0 | 0.0 | 0% |
| DB - Get last conversation id | 0.0 | 0.0 | 0% |
| DB - Get last contact id | 0.0 | 0.0 | 0% |
| DB - Get agents tokens | 0.0 | 0.0 | 0% |
| /brand-assets/logo-small.png | 0.0 | 0.0 | 0% |
No charts available.
No transaction errors were observed in both builds.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| DB - Get agents tokens | 85.86 | 85.0 | +1.012% |
| DB - Get last contact id | 85.86 | 78.0 | +10.077% |
| DB - Get last conversation id | 2896.98 | 2724.0 | +6.35% |
'DB - Get last conversation id' transaction with weight '94.40%' has the highest value of ET in the group '2896.98'.
This means that this transaction can be viewed as a bottleneck factor.
'DB - Get agents tokens' transaction with weight '2.80%' has the lowest value of ET in the group '85.86'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '3374.07%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'DB - Get last contact id' transaction with weight '2.80%' has the highest value of difference in the group '+10.077%'.
This means that this transaction can be viewed as a target for improvement.
'DB - Get agents tokens' transaction with weight '2.80%' has the lowest value of difference in the group '+1.012%'.
The '+' character indicates an increase in ET, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/agents | 1394.4 | 684.0 | +103.86% |
| /api/v1/accounts/{accountId}/inbox_members | 137.76 | 87.0 | +58.345% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 128.8 | 87.0 | +48.046% |
'/api/v1/accounts/{accountId}/agents' transaction with weight '83.95%' has the highest value of ET in the group '1394.4'.
This means that this transaction can be viewed as a bottleneck factor.
'/api/v1/accounts/{accountId}/teams/{teamId}/team_members' transaction with weight '7.75%' has the lowest value of ET in the group '128.8'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '1082.61%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/agents' transaction with weight '83.95%' has the highest value of difference in the group '+103.86%'.
This means that this transaction can be viewed as a target for improvement.
'/api/v1/accounts/{accountId}/teams/{teamId}/team_members' transaction with weight '7.75%' has the lowest value of difference in the group '+48.046%'.
The '+' character indicates an increase in ET, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '55.81%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /app/login | 170.8 | 141.0 | +21.135% |
| /auth/sign_in | 394.873 | 371.667 | +6.244% |
| /auth/validate_token | 108.58 | 127.667 | -14.951% |
| host/ | 56.527 | 43.333 | +30.448% |
'/auth/sign_in' transaction with weight '54.03%' has the highest value of ET in the group '394.873'.
This means that this transaction can be viewed as a bottleneck factor.
'host/' transaction with weight '7.74%' has the lowest value of ET in the group '56.527'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '698.56%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'host/' transaction with weight '7.74%' has the highest value of difference in the group '+30.448%'.
This means that this transaction can be viewed as a target for improvement.
'/auth/validate_token' transaction with weight '14.86%' has the lowest value of difference in the group '-14.951%'.
The special notice can be given to the absolute value '45.40%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/ | 75.53 | 88.0 | -14.170% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions | 83.265 | 55.0 | +51.391% |
| /api/v1/accounts/{accountId}/labels | 90.285 | 62.6 | +44.225% |
| /api/v1/accounts/{accountId}/notification_settings | 80.535 | 75.5 | +6.669% |
| /api/v1/accounts/{accountId}/notification_settings/global | 58.045 | 45.0 | +28.989% |
| /api/v1/profile/availability | 106.47 | 97.0 | +9.763% |
| /auth/active_providers | 57.33 | 43.0 | +33.326% |
| /brand-assets/logo-small.png | 49.14 | 38.0 | +29.316% |
'/api/v1/profile/availability' transaction with weight '17.73%' has the highest value of ET in the group '106.47'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'/brand-assets/logo-small.png' transaction with weight '8.18%' has the lowest value of ET in the group '49.14'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '216.67%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/custom_attribute_definitions' transaction with weight '13.86%' has the highest value of difference in the group '+51.391%'.
This means that this transaction can be viewed as a target for improvement.
'/api/v1/accounts/{accountId}/' transaction with weight '12.58%' has the lowest value of difference in the group '-14.17%'.
The special notice can be given to the absolute value '65.56%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 110.963 | 126.058 | -11.975% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 127.888 | 89.475 | +42.932% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 238.368 | 153.95 | +54.835% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 83.166 | 82.75 | +0.503% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 139.187 | 79.283 | +75.557% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 138.967 | 74.322 | +86.98% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 141.922 | 145.026 | -2.140% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 93.891 | 85.878 | +9.331% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 101.616 | 99.572 | +2.053% |
| check conversation status = open | 147.952 | 137.015 | +7.982% |
| check conversation status = resolved | 134.75 | 157.165 | -14.262% |
| toggle_status resolved | 1054.587 | 529.557 | +99.145% |
| update_last_seen | 106.329 | 117.038 | -9.150% |
'toggle_status resolved' transaction with weight '40.26%' has the highest value of ET in the group '1054.587'.
This means that this transaction can be viewed as a bottleneck factor.
'/api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me' transaction with weight '3.17%' has the lowest value of ET in the group '83.166'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '1268.05%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'toggle_status resolved' transaction with weight '40.26%' has the highest value of difference in the group '+99.145%'.
This means that this transaction can be viewed as a target for improvement.
'check conversation status = resolved' transaction with weight '5.14%' has the lowest value of difference in the group '-14.262%'.
The special notice can be given to the absolute value '113.41%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 159.231 | 138.639 | +14.853% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 143.88 | 123.444 | +16.555% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 294.067 | 163.917 | +79.4% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 107.03 | 133.032 | -19.546% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 158.791 | 83.028 | +91.25% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 175.609 | 114.306 | +53.631% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 203.842 | 248.897 | -18.102% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 102.129 | 99.889 | +2.242% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 111.907 | 118.861 | -5.851% |
| check conversation status = open | 213.383 | 145.824 | +46.329% |
| check conversation status = resolved | 136.4 | 164.774 | -17.220% |
| toggle_status resolved | 1124.53 | 617.1 | +82.228% |
| update_last_seen | 139.92 | 366.679 | -161.841% |
'toggle_status resolved' transaction with weight '36.62%' has the highest value of ET in the group '1124.53'.
This means that this transaction can be viewed as a bottleneck factor.
'/api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all' transaction with weight '3.33%' has the lowest value of ET in the group '102.129'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '1101.09%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/conversations/{conv_id}/labels' transaction with weight '5.17%' has the highest value of difference in the group '+91.25%'.
This means that this transaction can be viewed as a target for improvement.
'update_last_seen' transaction with weight '4.56%' has the lowest value of difference in the group '-61.841%'.
The special notice can be given to the absolute value '153.09%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 269.764 | 123.459 | +118.505% |
| Agent - Reply msg 2 | 171.516 | 125.622 | +36.533% |
| Agent - Reply msg 3 | 160.714 | 131.588 | +22.134% |
| Agent - Reply msg 4 | 166.84 | 148.229 | +12.556% |
| Agent - Reply msg 5 | 132.552 | 113.426 | +16.862% |
| Agent - Welcome msg | 231.804 | 111.256 | +108.352% |
'Agent - Reply msg 1' transaction with weight '23.81%' has the highest value of ET in the group '269.764'.
This means that this transaction can be viewed as a bottleneck factor.
'Agent - Reply msg 5' transaction with weight '11.70%' has the lowest value of ET in the group '132.552'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '203.52%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Agent - Reply msg 1' transaction with weight '23.81%' has the highest value of difference in the group '+118.505%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 4' transaction with weight '14.72%' has the lowest value of difference in the group '+12.556%'.
The '+' character indicates an increase in ET, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '105.95%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 491.423 | 265.581 | +85.037% |
| Agent - Reply msg 2 | 354.406 | 252.711 | +40.242% |
| Agent - Reply msg 3 | 261.322 | 256.168 | +2.012% |
| Agent - Reply msg 4 | 328.779 | 350.358 | -6.159% |
| Agent - Reply msg 5 | 222.399 | 245.073 | -9.252% |
| Agent - Welcome msg | 543.295 | 207.263 | +162.128% |
'Agent - Welcome msg' transaction with weight '24.68%' has the highest value of ET in the group '543.295'.
This means that this transaction can be viewed as a bottleneck factor.
'Agent - Reply msg 5' transaction with weight '10.10%' has the lowest value of ET in the group '222.399'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '244.29%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '24.68%' has the highest value of difference in the group '+162.128%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 5' transaction with weight '10.10%' has the lowest value of difference in the group '-9.252%'.
The special notice can be given to the absolute value '171.38%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 529.708 | 367.219 | +44.249% |
| Agent - Reply msg 2 | 480.185 | 288.286 | +66.565% |
| Agent - Reply msg 3 | 308.016 | 296.735 | +3.802% |
| Agent - Reply msg 4 | 401.178 | 511.742 | -21.605% |
| Agent - Reply msg 5 | 252.368 | 280.848 | -10.141% |
| Agent - Welcome msg | 642.125 | 249.375 | +157.494% |
'Agent - Welcome msg' transaction with weight '24.57%' has the highest value of ET in the group '642.125'.
This means that this transaction can be viewed as a bottleneck factor.
'Agent - Reply msg 5' transaction with weight '9.66%' has the lowest value of ET in the group '252.368'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '254.44%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '24.57%' has the highest value of difference in the group '+157.494%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 4' transaction with weight '15.35%' has the lowest value of difference in the group '-21.605%'.
The special notice can be given to the absolute value '179.10%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 138.388 | 125.946 | +9.879% |
| Bot - Entry msg | 61.273 | 56.471 | +8.503% |
| Bot - Language menu msg | 65.319 | 58.588 | +11.489% |
| Client - CSAT answer | 60.274 | 71.776 | -16.025% |
| Client - Text msg 1 | 58.715 | 49.848 | +17.788% |
| Client - Text msg 2 | 73.567 | 57.651 | +27.608% |
| Client - Text msg 3 | 61.829 | 53.789 | +14.947% |
| Client - Text msg 4 | 72.056 | 62.649 | +15.015% |
| Client - Text msg 5 | 56.885 | 50.009 | +13.75% |
'Bot - Agent request msg' transaction with weight '21.35%' has the highest value of ET in the group '138.388'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Client - Text msg 5' transaction with weight '8.77%' has the lowest value of ET in the group '56.885'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '243.28%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Client - Text msg 2' transaction with weight '11.35%' has the highest value of difference in the group '+27.608%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '9.30%' has the lowest value of difference in the group '-16.025%'.
The special notice can be given to the absolute value '43.63%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 150.788 | 138.171 | +9.131% |
| Bot - Entry msg | 65.843 | 59.688 | +10.312% |
| Bot - Language menu msg | 72.426 | 67.375 | +7.497% |
| Client - CSAT answer | 90.118 | 150.697 | -40.199% |
| Client - Text msg 1 | 87.291 | 74.697 | +16.86% |
| Client - Text msg 2 | 132.944 | 120.643 | +10.196% |
| Client - Text msg 3 | 97.961 | 86.842 | +12.804% |
| Client - Text msg 4 | 128.459 | 122.874 | +4.545% |
| Client - Text msg 5 | 79.566 | 73.864 | +7.72% |
'Bot - Agent request msg' transaction with weight '16.65%' has the highest value of ET in the group '150.788'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Bot - Entry msg' transaction with weight '7.27%' has the lowest value of ET in the group '65.843'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '229.01%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Client - Text msg 1' transaction with weight '9.64%' has the highest value of difference in the group '+16.86%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '9.95%' has the lowest value of difference in the group '-40.199%'.
The special notice can be given to the absolute value '57.06%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 174.063 | 151.583 | +14.83% |
| Bot - Entry msg | 74.981 | 107.958 | -30.546% |
| Bot - Language menu msg | 121.788 | 93.5 | +30.255% |
| Client - CSAT answer | 144.072 | 235.0 | -38.693% |
| Client - Text msg 1 | 92.22 | 90.194 | +2.246% |
| Client - Text msg 2 | 142.652 | 185.657 | -23.164% |
| Client - Text msg 3 | 122.366 | 103.935 | +17.733% |
| Client - Text msg 4 | 136.274 | 166.235 | -18.023% |
| Client - Text msg 5 | 80.56 | 84.0 | -4.095% |
'Bot - Agent request msg' transaction with weight '15.98%' has the highest value of ET in the group '174.063'.
But, this transaction's value is too small to be viewed as a bottleneck factor.
'Bot - Entry msg' transaction with weight '6.89%' has the lowest value of ET in the group '74.981'.
This means that this transaction can be viewed as the most lightweight transaction in the group.
The special notice can be given to the '232.14%' of the dispersion between maximum and minimum ET values.
Which indicates a lack of homogeneity in the transaction group.
'Bot - Language menu msg' transaction with weight '11.18%' has the highest value of difference in the group '+30.255%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '13.23%' has the lowest value of difference in the group '-38.693%'.
The special notice can be given to the absolute value '68.95%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/ | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/agents | 1.72 | 1.5 | +14.667% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 1.917 | 2.339 | -18.042% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 1.153 | 1.414 | -18.458% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/custom_filters?filter_type=conversation | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/dialogs/labels?dialogId[]=(dialog_id) | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/inbox_members | 2.58 | 1.5 | +72.0% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/inboxes | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/labels | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/notification_settings | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/notification_settings/global | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/notifications/unread_count | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/teams | 0.86 | 1.0 | -14.0% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 2.58 | 1.5 | +72.0% |
| /api/v1/notification_subscriptions | 0.86 | 1.0 | -14.0% |
| /api/v1/profile/availability | 0.86 | 1.0 | -14.0% |
| /app/login | 0.86 | 1.0 | -14.0% |
| /auth/active_providers | 0.86 | 1.0 | -14.0% |
| /auth/sign_in | 0.86 | 1.0 | -14.0% |
| /auth/validate_token | 0.86 | 1.0 | -14.0% |
| Agent - Reply msg 1 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 2 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 3 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 4 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 5 | 0.86 | 1.1 | -21.818% |
| Agent - Welcome msg | 0.86 | 1.1 | -21.818% |
| Bot - Agent request msg | 2.625 | 3.25 | -19.231% |
| Bot - Entry msg | 2.625 | 3.083 | -14.856% |
| Bot - Language menu msg | 2.625 | 3.25 | -19.231% |
| Client - CSAT answer | 0.86 | 1.1 | -21.818% |
| Client - Text msg 1 | 0.86 | 1.1 | -21.818% |
| Client - Text msg 2 | 0.86 | 1.1 | -21.818% |
| Client - Text msg 3 | 0.86 | 1.1 | -21.818% |
| Client - Text msg 4 | 0.86 | 1.1 | -21.818% |
| Client - Text msg 5 | 0.86 | 1.1 | -21.818% |
| check conversation status = open | 0.86 | 1.059 | -18.791% |
| check conversation status = resolved | 0.86 | 1.065 | -19.249% |
| host/ | 0.86 | 1.0 | -14.0% |
| toggle_status resolved | 0.86 | 1.1 | -21.818% |
'Bot - Agent request msg' transaction with weight '5.20%' has the highest value of requests per time bucket in the group '2.625'.
Thus, this transaction can be viewed as the most used one in at least one time bucket.
'/api/v1/accounts/(accountId)/conversations/(conv_id)' transaction with weight '1.70%' has the lowest value of requests per time bucket in the group '0.86'.
Thus, this transaction can be viewed as the least used one in at least one time bucket.
'/api/v1/accounts/{accountId}/inbox_members' transaction with weight '5.11%' has the highest value of difference in the group '+72.0%'.
This transaction can be viewed as example of most improvement.
'Agent - Reply msg 2' transaction with weight '1.70%' has the lowest value of difference in the group '-21.818%'.
This transaction can be viewed as a target for improvement.
The special notice can be given to the absolute value '93.82%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
Improvements or deteriorations in throughput of the respective transactions is result of these transactions decrease or increase of ET timings.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 2 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 3 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 4 | 0.86 | 1.1 | -21.818% |
| Agent - Reply msg 5 | 0.86 | 1.1 | -21.818% |
| Agent - Welcome msg | 0.86 | 1.1 | -21.818% |
'Agent - Reply msg 1' transaction with weight '16.67%' has the highest value of requests per time bucket in the group '0.86'.
Thus, this transaction can be viewed as the most used one in at least one time bucket.
'Agent - Reply msg 1' transaction with weight '16.67%' has the lowest value of ET in the group '0.86'.
Thus, this transaction can be viewed as the least used one in at least one time bucket.
'Agent - Reply msg 2' transaction with weight '16.67%' has the highest value of difference in the group '-21.818%'.
Where negative number shows degradation in the whole transaction group.
'Agent - Welcome msg' transaction with weight '16.67%' has the lowest value of difference in the group '-21.818%'.
This transaction can be viewed as a target for improvement.
Improvements or deteriorations in throughput of the respective transactions is result of these transactions decrease or increase of ET timings.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Client - Text msg 5 | 0.0 | 0.0 | 0% |
| Client - Text msg 4 | 0.0 | 0.0 | 0% |
| Client - Text msg 3 | 0.0 | 0.0 | 0% |
| Client - Text msg 2 | 0.0 | 0.0 | 0% |
| Client - Text msg 1 | 0.0 | 0.0 | 0% |
| Client - CSAT answer | 0.0 | 0.0 | 0% |
| Bot - Agent request msg | 0.0 | 0.0 | 0% |
| Bot - Entry msg | 0.0 | 0.0 | 0% |
| Bot - Language menu msg | 0.0 | 0.0 | 0% |
| Agent - Reply msg 1 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 2 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 3 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 4 | 0.0 | 0.0 | 0% |
| Agent - Reply msg 5 | 0.0 | 0.0 | 0% |
| Agent - Welcome msg | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/ | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/agents | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 0.0 | 0.0 | 0% |
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/dialogs/labels?dialogId[]=(dialog_id) | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/custom_filters?filter_type=conversation | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/inbox_members | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/inboxes | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/labels | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/notification_settings | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/notification_settings/global | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/notifications/unread_count | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/teams | 0.0 | 0.0 | 0% |
| /api/v1/notification_subscriptions | 0.0 | 0.0 | 0% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 0.0 | 0.0 | 0% |
| /api/v1/profile/availability | 0.0 | 0.0 | 0% |
| /app/login | 0.0 | 0.0 | 0% |
| /auth/validate_token | 0.0 | 0.0 | 0% |
| /auth/sign_in | 0.0 | 0.0 | 0% |
| /auth/active_providers | 0.0 | 0.0 | 0% |
| check conversation status = open | 0.0 | 0.0 | 0% |
| check conversation status = resolved | 0.0 | 0.0 | 0% |
| toggle_status resolved | 0.0 | 0.0 | 0% |
| update_last_seen | 0.0 | 0.0 | 0% |
| host/ | 0.0 | 0.0 | 0% |
| DB - Get last conversation id | 0.0 | 0.0 | 0% |
| DB - Get last contact id | 0.0 | 0.0 | 0% |
| DB - Get agents tokens | 0.0 | 0.0 | 0% |
| /brand-assets/logo-small.png | 0.0 | 0.0 | 0% |
No charts available.
No transaction errors were observed in both builds.
1.3.2 Spread by transaction
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/agents | 260.494 | 183.837 | +41.698% |
| /api/v1/accounts/{accountId}/inbox_members | 41.071 | 13.35 | +207.648% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 53.205 | 19.947 | +166.732% |
'/api/v1/accounts/{accountId}/agents' transaction with weight '73.43%' has the highest value of ET Spread in the group '260.494'.
This spread is '26049.40%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/api/v1/accounts/{accountId}/inbox_members' transaction with weight '11.58%' has the lowest value of ET Spread in the group with value '41.071'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '219.42' (or '634.25%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/inbox_members' transaction with weight '11.58%' has the highest value of difference in the group '+207.648%'.
This means that this transaction can be viewed as a target for improvement.
'/api/v1/accounts/{accountId}/agents' transaction with weight '73.43%' has the lowest value of difference in the group '+41.698%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '165.95%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /app/login | 0.0 | 0.0 | 0% |
| /auth/sign_in | 0.0 | 0.0 | 0% |
| /auth/validate_token | 0.0 | 0.0 | 0% |
| host/ | 0.0 | 0.0 | 0% |
'/app/login' transaction zero spread values in both builds suggests that it was executed only once per aggregation bucket.
'/auth/sign_in' transaction zero spread values in both builds suggests that it was executed only once per aggregation bucket.
'/auth/validate_token' transaction zero spread values in both builds suggests that it was executed only once per aggregation bucket.
'host/' transaction zero spread values in both builds suggests that it was executed only once per aggregation bucket.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 27.228 | 29.766 | -8.527% |
| Bot - Entry msg | 24.42 | 7.019 | +247.913% |
| Bot - Language menu msg | 19.356 | 17.642 | +9.715% |
'Bot - Agent request msg' transaction with weight '38.35%' has the highest value of ET Spread in the group '27.228'.
This spread is '2722.80%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Bot - Language menu msg' transaction with weight '27.26%' has the lowest value of ET Spread in the group with value '19.356'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '7.87' (or '140.67%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Bot - Entry msg' transaction with weight '34.39%' has the highest value of difference in the group '+247.913%'.
This means that this transaction can be viewed as a target for improvement.
'Bot - Agent request msg' transaction with weight '38.35%' has the lowest value of difference in the group '-8.527%'.
The special notice can be given to the absolute value '256.44%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 57.93 | 35.84 | +61.635% |
| Bot - Entry msg | 21.63 | 8.537 | +153.368% |
| Bot - Language menu msg | 18.287 | 17.034 | +7.356% |
'Bot - Agent request msg' transaction with weight '59.20%' has the highest value of ET Spread in the group '57.93'.
This spread is '5793.00%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Bot - Language menu msg' transaction with weight '18.69%' has the lowest value of ET Spread in the group with value '18.287'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '39.64' (or '316.78%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Bot - Entry msg' transaction with weight '22.11%' has the highest value of difference in the group '+153.368%'.
This means that this transaction can be viewed as a target for improvement.
'Bot - Language menu msg' transaction with weight '18.69%' has the lowest value of difference in the group '+7.356%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '146.01%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 61.23 | 39.921 | +34.802% |
| Bot - Entry msg | 22.91 | 11.798 | +48.503% |
| Bot - Language menu msg | 21.068 | 18.663 | +11.415% |
'Bot - Agent request msg' transaction with weight '58.20%' has the highest value of ET Spread in the group '61.23'.
This spread is '6123.00%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Bot - Language menu msg' transaction with weight '20.03%' has the lowest value of ET Spread in the group with value '21.068'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '40.16' (or '290.63%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Bot - Entry msg' transaction with weight '21.78%' has the highest value of difference in the group '+48.503%'.
This means that this transaction can be viewed as a target for improvement.
'Bot - Language menu msg' transaction with weight '20.03%' has the lowest value of difference in the group '+11.415%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '37.09%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/agents | 0.869 | 0.46 | +88.913% |
| /api/v1/accounts/{accountId}/inbox_members | 0.77 | 0.368 | +109.239% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 0.77 | 0.368 | +109.239% |
| /api/v1/accounts/{accountId}/inboxes | 0.341 | 0.271 | +25.83% |
| /api/v1/accounts/{accountId}/teams | 0.195 | 0.174 | +12.069% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 0.894 | 0.422 | +111.848% |
| /app/login | 0.3 | 0.191 | +57.068% |
| /auth/sign_in | 0.361 | 0.201 | +79.602% |
| /auth/validate_token | 0.237 | 0.173 | +36.994% |
| Bot - Agent request msg | 0.363 | 0.25 | +45.2% |
| Bot - Entry msg | 0.51 | 0.288 | +77.083% |
| Bot - Language menu msg | 0.471 | 0.29 | +62.414% |
| host/ | 0.281 | 0.281 | 0% |
'host/' transaction zero spread values in both builds suggests that it was executed only once per aggregation bucket.
'/api/v1/accounts/{accountId}/teams/{teamId}/team_members' transaction with weight '14.05%' has the highest value of requests per time bucket Spread in the group - '0.894'.
This can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/api/v1/accounts/{accountId}/teams' transaction with weight '3.07%' has the lowest value of requests per time bucket Spread in the group with value - '0.195'.
This transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '0.674' (or '345.641%') of dispersion between maximum and minimum requests per time bucket Spread values.
It indicates a lack of homogeneity in the group.
'/api/v1/accounts/{accountId}/teams/{teamId}/team_members' transaction with weight '14.05%' has the highest value of difference in the group - '+111.848%'.
This transaction can be viewed as a target for improvement.
'host/' transaction with weight '4.42%' has the lowest value of difference in the group '0.0%'.
'0.0%' as lowest value indicates an increase in Spread in all other requests, which is a negative factor that suggests a negative overall impact on the group.
The special notice can be given to the absolute value '111.85%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/agents | 0.0 | N/A | N/A |
The unequal number of data points (1 vs 0) in both builds suggests that some transaction(s) started earlier or finished later than aggregation bucket. This may require further investigation.
'/api/v1/accounts/{accountId}/agents' transaction zero spread values in both builds suggests that it was executed only once per aggreagation bucket.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /app/login | 0.0 | 0.0 | 0% |
| /auth/sign_in | 0.0 | 0.0 | 0% |
| /auth/validate_token | 0.0 | 0.0 | 0% |
| host/ | 0.0 | 0.0 | 0% |
'/app/login' transaction zero spread values in both builds suggests that it was executed only once per aggreagation bucket.
'/auth/sign_in' transaction zero spread values in both builds suggests that it was executed only once per aggreagation bucket.
'/auth/validate_token' transaction zero spread values in both builds suggests that it was executed only once per aggreagation bucket.
'host/' transaction zero spread values in both builds suggests that it was executed only once per aggreagation bucket.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/ | 26.491 | 24.495 | +7.535% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions | 15.73 | 8.281 | +47.355% |
| /api/v1/accounts/{accountId}/labels | 25.868 | 13.78 | +46.73% |
| /api/v1/accounts/{accountId}/notification_settings | 28.795 | 13.606 | +52.749% |
| /api/v1/accounts/{accountId}/notification_settings/global | 22.228 | 9.664 | +56.63% |
| /api/v1/profile/availability | 30.782 | 20.995 | +31.795% |
| /auth/active_providers | 22.228 | 10.622 | +52.213% |
| /brand-assets/logo-small.png | 10.065 | 6.825 | +32.191% |
'/api/v1/profile/availability' transaction with weight '16.89%' has the highest value of ET Spread in the group '30.782'.
This spread is '3078.20%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/brand-assets/logo-small.png' transaction with weight '5.52%' has the lowest value of ET Spread in the group with value '10.065'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '20.72' (or '305.83%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/notification_settings/global' transaction with weight '12.23%' has the highest value of difference in the group '+56.63%'.
This means that this transaction can be viewed as a target for improvement.
'/api/v1/accounts/{accountId}/' transaction with weight '14.54%' has the lowest value of difference in the group '+7.535%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '49.10%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 21.989 | 18.829 | +14.373% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 40.699 | 22.46 | +44.815% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 89.525 | 46.442 | +48.124% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 30.629 | 18.517 | +39.544% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 33.974 | 22.347 | +34.224% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 41.924 | 20.19 | +51.842% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 38.077 | 29.903 | +21.467% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 23.012 | 22.369 | +2.794% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 26.859 | 26.436 | +1.575% |
| check conversation status = open | 53.412 | 30.661 | +42.596% |
| check conversation status = resolved | 54.703 | 28.762 | +47.421% |
| toggle_status resolved | 246.833 | 70.25 | +351.363% |
| update_last_seen | 25.037 | 26.861 | -7.286% |
'toggle_status resolved' transaction with weight '33.97%' has the highest value of ET Spread in the group '246.833'.
This spread is '24683.30%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/api/v1/accounts/(accountId)/conversations/(conv_id)' transaction with weight '3.03%' has the lowest value of ET Spread in the group with value '21.989'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '224.84' (or '1122.53%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'toggle_status resolved' transaction with weight '33.97%' has the highest value of difference in the group '+351.363%'.
This means that this transaction can be viewed as a target for improvement.
'update_last_seen' transaction with weight '3.45%' has the lowest value of difference in the group '-7.286%'.
The special notice can be given to the absolute value '358.65%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 29.397 | 32.8 | -10.375% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 30.42 | 21.573 | +41.010% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 80.906 | 37.979 | +113.028% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 30.448 | 23.781 | +28.035% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 66.48 | 13.397 | +396.230% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 51.898 | 21.585 | +140.435% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 68.078 | 31.128 | +118.703% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 23.475 | 24.195 | -2.976% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 22.133 | 24.279 | -8.839% |
| check conversation status = open | 67.927 | 25.868 | +162.591% |
| check conversation status = resolved | 37.643 | 21.437 | +75.598% |
| toggle_status resolved | 405.09 | 111.625 | +262.903% |
| update_last_seen | 38.927 | 91.99 | -57.683% |
'toggle_status resolved' transaction with weight '42.51%' has the highest value of ET Spread in the group '405.09'.
This spread is '40509.00%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/api/v1/accounts/{accountId}/inbox_members/{inboxId}' transaction with weight '2.32%' has the lowest value of ET Spread in the group with value '22.133'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '382.96' (or '1830.25%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/conversations/{conv_id}/labels' transaction with weight '6.98%' has the highest value of difference in the group '+396.23%'.
This means that this transaction can be viewed as a target for improvement.
'update_last_seen' transaction with weight '4.09%' has the lowest value of difference in the group '-57.683%'.
The special notice can be given to the absolute value '453.91%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 93.657 | 24.677 | +279.532% |
| Agent - Reply msg 2 | 32.88 | 20.956 | +56.9% |
| Agent - Reply msg 3 | 58.019 | 28.944 | +100.453% |
| Agent - Reply msg 4 | 31.018 | 38.417 | -19.260% |
| Agent - Reply msg 5 | 50.337 | 27.076 | +85.91% |
| Agent - Welcome msg | 70.765 | 16.383 | +331.942% |
'Agent - Reply msg 1' transaction with weight '27.82%' has the highest value of ET Spread in the group '93.657'.
This spread is '9365.70%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Agent - Reply msg 4' transaction with weight '9.21%' has the lowest value of ET Spread in the group with value '31.018'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '62.64' (or '301.94%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '21.02%' has the highest value of difference in the group '+331.942%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 4' transaction with weight '9.21%' has the lowest value of difference in the group '-19.26%'.
The special notice can be given to the absolute value '351.20%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 101.814 | 76.145 | +33.711% |
| Agent - Reply msg 2 | 147.287 | 56.272 | +161.741% |
| Agent - Reply msg 3 | 100.051 | 49.394 | +102.557% |
| Agent - Reply msg 4 | 136.826 | 69.233 | +97.631% |
| Agent - Reply msg 5 | 54.565 | 47.502 | +14.869% |
| Agent - Welcome msg | 146.707 | 49.61 | +195.721% |
'Agent - Reply msg 2' transaction with weight '21.43%' has the highest value of ET Spread in the group '147.287'.
This spread is '14728.70%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Agent - Reply msg 5' transaction with weight '7.94%' has the lowest value of ET Spread in the group with value '54.565'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '92.72' (or '269.93%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '21.35%' has the highest value of difference in the group '+195.721%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 5' transaction with weight '7.94%' has the lowest value of difference in the group '+14.869%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '180.85%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 125.131 | 109.518 | +14.256% |
| Agent - Reply msg 2 | 154.678 | 77.559 | +99.433% |
| Agent - Reply msg 3 | 65.546 | 60.157 | +8.958% |
| Agent - Reply msg 4 | 142.383 | 76.774 | +85.457% |
| Agent - Reply msg 5 | 45.716 | 39.0 | +17.221% |
| Agent - Welcome msg | 169.893 | 34.619 | +390.751% |
'Agent - Welcome msg' transaction with weight '24.15%' has the highest value of ET Spread in the group '169.893'.
This spread is '16989.30%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Agent - Reply msg 5' transaction with weight '6.50%' has the lowest value of ET Spread in the group with value '45.716'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '124.18' (or '371.63%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '24.15%' has the highest value of difference in the group '+390.751%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 3' transaction with weight '9.32%' has the lowest value of difference in the group '+8.958%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '381.79%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 49.246 | 37.567 | +31.088% |
| Bot - Entry msg | 14.838 | 10.395 | +42.742% |
| Bot - Language menu msg | 16.381 | 15.364 | +6.619% |
| Client - CSAT answer | 20.29 | 13.891 | +46.066% |
| Client - Text msg 1 | 11.614 | 12.319 | -5.723% |
| Client - Text msg 2 | 26.549 | 8.368 | +217.268% |
| Client - Text msg 3 | 14.834 | 8.028 | +84.778% |
| Client - Text msg 4 | 14.205 | 15.932 | -10.840% |
| Client - Text msg 5 | 18.948 | 7.17 | +164.268% |
'Bot - Agent request msg' transaction with weight '26.35%' has the highest value of ET Spread in the group '49.246'.
This spread is '4924.60%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Client - Text msg 1' transaction with weight '6.21%' has the lowest value of ET Spread in the group with value '11.614'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '37.63' (or '424.02%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Client - Text msg 2' transaction with weight '14.20%' has the highest value of difference in the group '+217.268%'.
This means that this transaction can be viewed as a target for improvement.
'Client - Text msg 4' transaction with weight '7.60%' has the lowest value of difference in the group '-10.84%'.
The special notice can be given to the absolute value '228.11%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 58.296 | 36.85 | +58.198% |
| Bot - Entry msg | 25.679 | 9.622 | +166.878% |
| Bot - Language menu msg | 25.57 | 11.965 | +113.707% |
| Client - CSAT answer | 26.918 | 32.414 | -16.956% |
| Client - Text msg 1 | 29.573 | 15.329 | +92.922% |
| Client - Text msg 2 | 54.726 | 36.628 | +49.41% |
| Client - Text msg 3 | 28.939 | 25.86 | +11.906% |
| Client - Text msg 4 | 39.439 | 23.153 | +70.341% |
| Client - Text msg 5 | 26.878 | 12.203 | +120.257% |
'Bot - Agent request msg' transaction with weight '18.45%' has the highest value of ET Spread in the group '58.296'.
This spread is '5829.60%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Bot - Language menu msg' transaction with weight '8.09%' has the lowest value of ET Spread in the group with value '25.57'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '32.73' (or '227.99%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Bot - Entry msg' transaction with weight '8.13%' has the highest value of difference in the group '+166.878%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '8.52%' has the lowest value of difference in the group '-16.956%'.
The special notice can be given to the absolute value '183.83%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 59.883 | 38.68 | +35.407% |
| Bot - Entry msg | 26.824 | 15.11 | +43.670% |
| Bot - Language menu msg | 31.7 | 18.994 | +66.895% |
| Client - CSAT answer | 32.712 | 51.003 | -35.863 |
| Client - Text msg 1 | 17.419 | 22.218 | -21.600% |
| Client - Text msg 2 | 49.085 | 43.779 | +12.12% |
| Client - Text msg 3 | 44.089 | 28.742 | +53.396% |
| Client - Text msg 4 | 28.984 | 36.779 | -21.194% |
| Client - Text msg 5 | 19.129 | 24.845 | -23.007% |
'Bot - Agent request msg' transaction with weight '19.33%' has the highest value of ET Spread in the group '59.883'.
This spread is '5988.30%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Client - Text msg 1' transaction with weight '5.62%' has the lowest value of ET Spread in the group with value '17.419'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '42.46' (or '343.78%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Bot - Language menu msg' transaction with weight '10.23%' has the highest value of difference in the group '+66.895%'.
This means that this transaction can be viewed as a target for improvement.
'Client - CSAT answer' transaction with weight '10.56%' has the lowest value of difference in the group '-35.863%'.
The special notice can be given to the absolute value '102.76%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 0.266 | 0.224 | +18.75% |
| /api/v1/accounts/{accountId}/ | 0.346 | 0.298 | +16.107% |
| /api/v1/accounts/{accountId}/agents | 0.297 | 0.141 | +110.638% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 0.24 | 0.173 | +38.728% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 0.276 | 0.168 | +64.286% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 0.575 | 0.408 | +40.931% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 0.243 | 0.266 | -8.647% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 0.348 | 0.228 | +52.632% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 0.452 | 0.179 | +152.514% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions | 0.241 | 0.287 | -16.028% |
| /api/v1/accounts/{accountId}/custom_filters?filter_type=conversation | 0.159 | 0.278 | -42.806% |
| /api/v1/accounts/{accountId}/dialogs/labels?dialogId[]=(dialog_id) | 0.261 | 0.209 | +24.88% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 0.342 | 0.151 | +126.49% |
| /api/v1/accounts/{accountId}/inboxes | 0.291 | 0.171 | +70.175% |
| /api/v1/accounts/{accountId}/labels | 0.276 | 0.255 | +8.235% |
| /api/v1/accounts/{accountId}/notification_settings | 0.197 | 0.179 | +10.056% |
| /api/v1/accounts/{accountId}/notification_settings/global | 0.357 | 0.293 | +21.843% |
| /api/v1/accounts/{accountId}/notifications/unread_count | 0.319 | 0.257 | +24.125% |
| /api/v1/accounts/{accountId}/teams | 0.16 | 0.194 | -17.526% |
| /api/v1/notification_subscriptions | 0.223 | 0.159 | +40.252% |
| /api/v1/profile/availability | 0.181 | 0.295 | -38.644% |
| /app/login | 0.318 | 0.194 | +63.918% |
| /auth/active_providers | 0.184 | 0.165 | +11.515% |
| /auth/sign_in | 0.184 | 0.137 | +34.307% |
| /auth/validate_token | 0.301 | 0.165 | +82.424% |
| Agent - Reply msg 1 | 0.265 | 0.166 | +59.639% |
| Agent - Reply msg 2 | 0.197 | 0.271 | -27.306% |
| Agent - Reply msg 3 | 0.328 | 0.19 | +72.632% |
| Agent - Reply msg 4 | 0.336 | 0.153 | +119.608% |
| Agent - Reply msg 5 | 0.161 | 0.292 | -44.863% |
| Agent - Welcome msg | 0.248 | 0.227 | +9.251% |
| Bot - Agent request msg | 0.886 | 0.623 | +42.215% |
| Bot - Entry msg | 1.109 | 0.933 | +18.864% |
| Bot - Language menu msg | 0.851 | 0.47 | +81.064% |
| Client - CSAT answer | 0.291 | 0.245 | +18.776% |
| Client - Text msg 1 | 0.203 | 0.256 | -20.703% |
| Client - Text msg 2 | 0.169 | 0.154 | +9.74% |
| Client - Text msg 3 | 0.216 | 0.297 | -27.273 |
| Client - Text msg 4 | 0.307 | 0.282 | +8.865% |
| Client - Text msg 5 | 0.178 | 0.246 | -27.642% |
| check conversation status = open | 0.22 | 0.132 | +66.667% |
| check conversation status = resolved | 0.355 | 0.178 | +99.438% |
| host/ | 0.227 | 0.137 | +65.693% |
| toggle_status resolved | 0.303 | 0.168 | +80.357% |
'Bot - Entry msg' transaction with weight '7.99%' has the highest value of requests per time bucket Spread in the group - '1.109'.
This spread is '110.90%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/api/v1/accounts/{accountId}/custom_filters?filter_type=conversation' transaction with weight '1.14%' has the lowest value of requests per time bucket Spread in the group with value '0.159'.
This transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '0.949' (or '85.573%') of dispersion between maximum and minimum requests per time bucket Spread values.
It indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1' transaction with weight '3.25%' has the highest value of difference in the group - '+152.514%'.
This transaction can be viewed as a target for improvement.
'Agent - Reply msg 5' transaction with weight '1.16%' has the lowest value of difference in the group - '-44.863%'.
The special notice can be given to the absolute value '197.38%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 0.265 | 0.166 | +59.639% |
| Agent - Reply msg 2 | 0.197 | 0.271 | -27.306% |
| Agent - Reply msg 3 | 0.328 | 0.19 | +72.632% |
| Agent - Reply msg 4 | 0.336 | 0.153 | +119.608% |
| Agent - Reply msg 5 | 0.161 | 0.292 | -44.863% |
| Agent - Welcome msg | 0.248 | 0.227 | +9.251% |
'Agent - Reply msg 4' transaction with weight '21.89%' has the highest value of requests per time bucket Spread in the group - '0.336'.
This can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Agent - Reply msg 5' transaction with weight '10.49%' has the lowest value of requests per time bucket Spread in the group - '0.161'.
This transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '0.175' (or '52.083%') of dispersion between maximum and minimum requests per time bucket Spread values.
It indicates a lack of homogeneity in the group.
'Agent - Reply msg 4' transaction with weight '21.89%' has the highest value of difference in the group - '+119.608%'.
This transaction can be viewed as a target for improvement.
'Agent - Reply msg 5' transaction with weight '10.49%' has the lowest value of difference in the group - '-44.863%'.
The special notice can be given to the absolute value '164.47%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/agents | 260.494 | 183.837 | +41.698% |
| /api/v1/accounts/{accountId}/inbox_members | 41.071 | 13.35 | +207.648% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 53.205 | 19.947 | +166.732% |
The unequal number of data points (4 vs 3) in both builds suggests that some transaction(s) started earlier or finished later than aggregation bucket. This may require further investigation.
'/api/v1/accounts/{accountId}/agents' transaction with weight '73.43%' has the highest value of ET Spread in the group '260.494'.
This spread is '26049.40%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/api/v1/accounts/{accountId}/inbox_members' transaction with weight '11.58%' has the lowest value of ET Spread in the group with value '41.071'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '219.42' (or '634.25%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/inbox_members' transaction with weight '11.58%' has the highest value of difference in the group '+207.648%'.
This means that this transaction can be viewed as a target for improvement.
'/api/v1/accounts/{accountId}/agents' transaction with weight '73.43%' has the lowest value of difference in the group '+41.698%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '165.95%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /app/login | 0.0 | 0.0 | 0% |
| /auth/sign_in | 0.0 | 0.0 | 0% |
| /auth/validate_token | 0.0 | 0.0 | 0% |
| host/ | 0.0 | 0.0 | 0% |
'/app/login' transaction zero spread values in both builds suggests that it was executed only once per aggregation bucket.
'/auth/sign_in' transaction zero spread values in both builds suggests that it was executed only once per aggregation bucket.
'/auth/validate_token' transaction zero spread values in both builds suggests that it was executed only once per aggregation bucket.
'host/' transaction zero spread values in both builds suggests that it was executed only once per aggregation bucket.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/{accountId}/ | 26.491 | 24.495 | +8.149% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions | 15.73 | 8.281 | +89.953% |
| /api/v1/accounts/{accountId}/labels | 25.868 | 13.78 | +87.721% |
| /api/v1/accounts/{accountId}/notification_settings | 28.795 | 13.606 | +111.635% |
| /api/v1/accounts/{accountId}/notification_settings/global | 22.283 | 9.664 | +130.577% |
| /api/v1/profile/availability | 30.782 | 20.995 | +46.616% |
| /auth/active_providers | 22.228 | 10.622 | +109.264% |
| /brand-assets/logo-small.png | 10.065 | 6.825 | +47.473% |
'/api/v1/profile/availability' transaction with weight '16.89%' has the highest value of ET Spread in the group '30.782'.
This spread is '3078.20%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/brand-assets/logo-small.png' transaction with weight '5.52%' has the lowest value of ET Spread in the group with value '10.065'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '20.72' (or '305.83%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/notification_settings/global' transaction with weight '12.23%' has the highest value of difference in the group '+130.577%'.
This means that this transaction can be viewed as a target for improvement.
'/api/v1/accounts/{accountId}/' transaction with weight '14.54%' has the lowest value of difference in the group '+8.149%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '122.43%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 21.989 | 18.829 | +16.783% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 40.699 | 22.46 | +81.207% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 89.525 | 46.442 | +92.767% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 30.629 | 18.517 | +65.410% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 33.974 | 22.347 | +52.029% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 41.924 | 20.19 | +107.647% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 38.077 | 29.903 | +27.335% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 23.012 | 22.369 | +2.875% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 26.859 | 26.436 | +1.6% |
| check conversation status = open | 53.412 | 30.661 | +74.202% |
| check conversation status = resolved | 54.703 | 28.762 | +90.192% |
| toggle_status resolved | 246.833 | 70.25 | +251.364% |
| update_last_seen | 25.037 | 26.861 | -6.791% |
'toggle_status resolved' transaction with weight '33.97%' has the highest value of ET Spread in the group '246.833'.
This spread is '24683.30%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/api/v1/accounts/(accountId)/conversations/(conv_id)' transaction with weight '3.03%' has the lowest value of ET Spread in the group with value '21.989'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '224.84' (or '1122.53%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'toggle_status resolved' transaction with weight '33.97%' has the highest value of difference in the group '+251.364%'.
This means that this transaction can be viewed as a target for improvement.
'update_last_seen' transaction with weight '3.45%' has the lowest value of difference in the group '-6.791%'.
The special notice can be given to the absolute value '258.16%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 29.397 | 32.8 | -10.375% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 30.42 | 21.573 | +41.01% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 80.906 | 37.979 | +113.028% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 30.448 | 23.781 | +28.035% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 66.48 | 13.397 | +396.23% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 51.898 | 21.585 | +140.435% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 68.078 | 31.128 | +118.703% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions?filter=all | 23.475 | 24.195 | -2.976% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 22.133 | 24.279 | -8.839% |
| check conversation status = open | 67.927 | 25.868 | +162.591% |
| check conversation status = resolved | 37.643 | 21.437 | +75.598% |
| toggle_status resolved | 405.09 | 111.625 | +262.903% |
| update_last_seen | 38.927 | 91.99 | -57.683% |
'toggle_status resolved' transaction with weight '42.51%' has the highest value of ET Spread in the group '405.09'.
This spread is '40509.00%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/api/v1/accounts/{accountId}/inbox_members/{inboxId}' transaction with weight '2.32%' has the lowest value of ET Spread in the group with value '22.133'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '382.96' (or '1830.25%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/conversations/{conv_id}/labels' transaction with weight '6.98%' has the highest value of difference in the group '+396.23%'.
This means that this transaction can be viewed as a target for improvement.
'update_last_seen' transaction with weight '4.09%' has the lowest value of difference in the group '-57.683%'.
The special notice can be given to the absolute value '453.91%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 93.657 | 24.677 | +279.532% |
| Agent - Reply msg 2 | 32.88 | 20.956 | +56.900% |
| Agent - Reply msg 3 | 58.019 | 28.944 | +100.453% |
| Agent - Reply msg 4 | 31.018 | 38.417 | -19.260% |
| Agent - Reply msg 5 | 50.337 | 27.076 | +85.910% |
| Agent - Welcome msg | 70.765 | 16.383 | +331.942% |
The unequal number of data points (156 vs 155) in both builds suggests that some transaction(s) started earlier or finished later than aggregation bucket. This may require further investigation.
'Agent - Reply msg 1' transaction with weight '27.82%' has the highest value of ET Spread in the group '93.657'.
This spread is '9365.70%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Agent - Reply msg 4' transaction with weight '9.21%' has the lowest value of ET Spread in the group with value '31.018'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '62.64' (or '301.94%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '21.02%' has the highest value of difference in the group '+331.942%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 4' transaction with weight '9.21%' has the lowest value of difference in the group '-19.26%'.
The special notice can be given to the absolute value '351.20%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 101.814 | 76.145 | +33.711% |
| Agent - Reply msg 2 | 147.287 | 56.272 | +161.741% |
| Agent - Reply msg 3 | 100.051 | 49.394 | +102.557% |
| Agent - Reply msg 4 | 136.826 | 69.233 | +97.631% |
| Agent - Reply msg 5 | 54.565 | 47.502 | +14.869% |
| Agent - Welcome msg | 146.707 | 49.61 | +195.721% |
The unequal number of data points (156 vs 155) in both builds suggests that some transaction(s) started earlier or finished later than aggregation bucket. This may require further investigation.
"'Agent - Reply msg 2' transaction with weight '21.43%' has the highest value of ET Spread in the group '147.287'.
This spread is '14728.70%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Agent - Reply msg 5' transaction with weight '7.94%' has the lowest value of ET Spread in the group with value '54.565'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '92.72' (or '269.93%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '21.35%' has the highest value of difference in the group '+195.721%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 5' transaction with weight '7.94%' has the lowest value of difference in the group '+14.869%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '180.85%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 125.131 | 109.518 | +14.256% |
| Agent - Reply msg 2 | 154.678 | 77.559 | +99.433% |
| Agent - Reply msg 3 | 65.546 | 60.157 | +8.958% |
| Agent - Reply msg 4 | 142.383 | 76.774 | +85.457% |
| Agent - Reply msg 5 | 45.716 | 39.0 | +17.221% |
| Agent - Welcome msg | 169.893 | 34.619 | +390.751% |
'Agent - Welcome msg' transaction with weight '24.15%' has the highest value of ET Spread in the group '169.893'.
This spread is '16989.30%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Agent - Reply msg 5' transaction with weight '6.50%' has the lowest value of ET Spread in the group with value '45.716'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '124.18' (or '371.63%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Agent - Welcome msg' transaction with weight '24.15%' has the highest value of difference in the group '+390.751%'.
This means that this transaction can be viewed as a target for improvement.
'Agent - Reply msg 3' transaction with weight '9.32%' has the lowest value of difference in the group '+8.958%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '381.79%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 30.496 | 26.067 | +14.523% |
| Bot - Entry msg | 11.87 | 14.935 | -20.522% |
| Bot - Language menu msg | 26.502 | 17.231 | +53.804% |
| Client - CSAT answer | 22.773 | 13.746 | +65.67% |
| Client - Text msg 1 | 11.46 | 10.493 | +9.216% |
| Client - Text msg 2 | 17.028 | 8.165 | +108.549% |
| Client - Text msg 3 | 12.004 | 7.94 | +51.184% |
| Client - Text msg 4 | 18.595 | 16.169 | +15.004% |
| Client - Text msg 5 | 15.855 | 14.513 | +9.247% |
'Bot - Agent request msg' transaction with weight '18.31%' has the highest value of ET Spread in the group '30.496'.
This spread is '3049.60%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Client - Text msg 1' transaction with weight '6.88%' has the lowest value of ET Spread in the group with value '11.46'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '19.04' (or '266.11%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Client - Text msg 2' transaction with weight '10.22%' has the highest value of difference in the group '+108.549%'.
This means that this transaction can be viewed as a target for improvement.
'Bot - Entry msg' transaction with weight '7.13%' has the lowest value of difference in the group '-20.522%'.
The special notice can be given to the absolute value '129.07%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 46.816 | 30.025 | +35.866% |
| Bot - Entry msg | 16.724 | 15.083 | +10.88% |
| Bot - Language menu msg | 29.404 | 17.289 | +70.073% |
| Client - CSAT answer | 26.838 | 24.418 | +9.911% |
| Client - Text msg 1 | 33.8 | 13.043 | +159.143% |
| Client - Text msg 2 | 51.156 | 14.576 | +250.96% |
| Client - Text msg 3 | 20.59 | 19.439 | +5.921% |
| Client - Text msg 4 | 37.957 | 21.424 | +77.17% |
| Client - Text msg 5 | 20.11 | 11.023 | +82.437% |
'Client - Text msg 2' transaction with weight '18.05%' has the highest value of ET Spread in the group '51.156'.
This spread is '5115.60%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Bot - Entry msg' transaction with weight '5.90%' has the lowest value of ET Spread in the group with value '16.724'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '34.43' (or '305.88%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Client - Text msg 2' transaction with weight '18.05%' has the highest value of difference in the group '+250.96%'.
This means that this transaction can be viewed as a target for improvement.
'Client - Text msg 3' transaction with weight '7.27%' has the lowest value of difference in the group '+5.921%'.
The '+' character indicates an increase in Spread, which is a negative factor. This increase was observed in transaction with the lowest difference within the transaction group, suggesting a negative overall impact on the group.
The special notice can be given to the absolute value '245.04%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Bot - Agent request msg | 51.19 | 44.331 | +15.472% |
| Bot - Entry msg | 24.904 | 30.782 | -19.096% |
| Bot - Language menu msg | 32.509 | 21.984 | +47.876% |
| Client - CSAT answer | 37.396 | 44.966 | -16.835% |
| Client - Text msg 1 | 34.515 | 20.271 | +70.268% |
| Client - Text msg 2 | 36.382 | 39.177 | -7.134% |
| Client - Text msg 3 | 27.929 | 28.182 | -0.898% |
| Client - Text msg 4 | 53.345 | 23.216 | +129.777% |
| Client - Text msg 5 | 21.96 | 11.108 | +97.695% |
'Client - Text msg 4' transaction with weight '16.66%' has the highest value of ET Spread in the group '53.345'.
This spread is '5334.50%' of the transaction's variability.
And, this can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Client - Text msg 5' transaction with weight '6.86%' has the lowest value of ET Spread in the group with value '21.96'.
This means that this transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '31.39' (or '242.92%') of dispersion between maximum and minimum ET Spread values.
It indicates a lack of homogeneity in the transaction group.
'Client - Text msg 4' transaction with weight '16.66%' has the highest value of difference in the group '+129.777%'.
This means that this transaction can be viewed as a target for improvement.
'Bot - Entry msg' transaction with weight '7.78%' has the lowest value of difference in the group '-19.096%'.
The special notice can be given to the absolute value '148.87%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| /api/v1/accounts/(accountId)/conversations/(conv_id) | 0.187 | 0.19 | -1.579% |
| /api/v1/accounts/{accountId}/ | 0.276 | 0.242 | +14.05% |
| /api/v1/accounts/{accountId}/agents | 0.357 | 0.318 | +12.264% |
| /api/v1/accounts/{accountId}/contacts/(cont_id) | 0.329 | 0.268 | +22.761% |
| /api/v1/accounts/{accountId}/contacts/(cont_id)/conversations | 0.219 | 0.178 | +23.034% |
| /api/v1/accounts/{accountId}/conversations/meta?status=open&assignee_type=me | 0.574 | 0.55 | +4.364% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/labels | 0.345 | 0.132 | +161.364% |
| /api/v1/accounts/{accountId}/conversations/{conv_id}/messages?before={before_number} | 0.277 | 0.149 | +85.906% |
| /api/v1/accounts/{accountId}/conversations?status=open&assignee_type=me&page=1 | 0.261 | 0.256 | +1.953% |
| /api/v1/accounts/{accountId}/custom_attribute_definitions | 0.184 | 0.22 | -16.364% |
| /api/v1/accounts/{accountId}/custom_filters?filter_type=conversation | 0.35 | 0.228 | +53.509% |
| /api/v1/accounts/{accountId}/dialogs/labels?dialogId[]=(dialog_id) | 0.21 | 0.191 | +9.948% |
| /api/v1/accounts/{accountId}/inbox_members | 0.572 | 0.251 | +127.888% |
| /api/v1/accounts/{accountId}/inbox_members/{inboxId} | 0.305 | 0.287 | +6.272% |
| /api/v1/accounts/{accountId}/inboxes | 0.243 | 0.211 | +15.166% |
| /api/v1/accounts/{accountId}/labels | 0.168 | 0.215 | -21.860% |
| /api/v1/accounts/{accountId}/notification_settings | 0.3 | 0.26 | +15.385% |
| /api/v1/accounts/{accountId}/notification_settings/global | 0.17 | 0.129 | +31.783% |
| /api/v1/accounts/{accountId}/notifications/unread_count | 0.156 | 0.193 | -19.171% |
| /api/v1/accounts/{accountId}/teams | 0.209 | 0.155 | +34.839% |
| /api/v1/accounts/{accountId}/teams/{teamId}/team_members | 0.853 | 0.321 | +165.732% |
| /api/v1/notification_subscriptions | 0.232 | 0.231 | +0.433% |
| /api/v1/profile/availability | 0.328 | 0.219 | +49.772% |
| /app/login | 0.208 | 0.246 | -15.447% |
| /auth/active_providers | 0.171 | 0.172 | -0.585% |
| /auth/sign_in | 0.282 | 0.248 | +13.71% |
| /auth/validate_token | 0.215 | 0.239 | -10.042% |
| Agent - Reply msg 1 | 0.352 | 0.18 | +95.556% |
| Agent - Reply msg 2 | 0.35 | 0.184 | +90.217% |
| Agent - Reply msg 3 | 0.235 | 0.277 | -15.162% |
| Agent - Reply msg 4 | 0.178 | 0.222 | -19.820% |
| Agent - Reply msg 5 | 0.348 | 0.249 | +39.759% |
| Agent - Welcome msg | 0.267 | 0.307 | -13.029% |
| Bot - Agent request msg | 0.679 | 0.481 | +41.164% |
| Bot - Entry msg | 1.086 | 0.667 | +62.819% |
| Bot - Language menu msg | 0.859 | 0.76 | +13.026% |
| Client - CSAT answer | 0.301 | 0.252 | +19.444% |
| Client - Text msg 1 | 0.23 | 0.191 | +20.419% |
| Client - Text msg 2 | 0.197 | 0.268 | -26.493% |
| Client - Text msg 3 | 0.256 | 0.145 | +76.552% |
| Client - Text msg 4 | 0.325 | 0.197 | +64.975% |
| Client - Text msg 5 | 0.172 | 0.143 | +20.28% |
| check conversation status = open | 0.225 | 0.15 | +50.0% |
| check conversation status = resolved | 0.322 | 0.222 | +45.045% |
| host/ | 0.233 | 0.228 | +2.193% |
| toggle_status resolved | 0.199 | 0.302 | -34.106% |
'Bot - Entry msg' transaction with weight '7.34%' has the highest value of requests per time bucket Spread in the group - '1.086'.
This can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'/api/v1/accounts/{accountId}/notifications/unread_count' transaction with weight '1.05%' has the lowest value of requests per time bucket Spread in the group with value '0.156'.
This transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '0.93' (or '85.635%') of dispersion between maximum and minimum requests per time bucket Spread values.
It indicates a lack of homogeneity in the transaction group.
'/api/v1/accounts/{accountId}/teams/{teamId}/team_members' transaction with weight '5.77%' has the highest value of difference in the group '+165.732%'.
This transaction can be viewed as a target for improvement.
'toggle_status resolved' transaction with weight '1.35%' has the lowest value of difference in the group '-34.106%'.
The special notice can be given to the absolute value '199.84%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
| Transaction Name | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Agent - Reply msg 1 | 0.352 | 0.18 | +95.556% |
| Agent - Reply msg 2 | 0.35 | 0.184 | +90.217% |
| Agent - Reply msg 3 | 0.235 | 0.277 | -15.162% |
| Agent - Reply msg 4 | 0.178 | 0.222 | -19.820% |
| Agent - Reply msg 5 | 0.348 | 0.249 | +39.759% |
| Agent - Welcome msg | 0.267 | 0.307 | -13.029% |
'Agent - Reply msg 1' transaction with weight '20.35%' has the highest value of requests per time bucket Spread in the group - '0.352'.
This can be viewed as a volatility bottleneck factor that shows instability in the corresponding code block.
'Agent - Reply msg 4' transaction with weight '10.29%' has the lowest value of requests per time bucket Spread in the group with value '0.178'.
This transaction can be viewed as the least volatile in the group.
The special notice can be given to the value '0.174' (or '49.432%') of dispersion between maximum and minimum requests per time bucket Spread values.
It indicates a lack of homogeneity in the transaction group.
'Agent - Reply msg 1' transaction with weight '20.35%' has the highest value of difference in the group - '+95.556%'.
This transaction can be viewed as a target for improvement.
'Agent - Reply msg 4' transaction with weight '10.29%' has the lowest value of difference in the group - '-19.82%'.
The special notice can be given to the absolute value '115.38%' of dispersion between maximum and minimum difference values.
Such dispersion suggests that transaction performance improvements and deteriorations, that were made directly or indirectly, did make related system part(s) more unstable which require further investigation.
1.4 Resources consumption
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 9.992 | 7.982 | +25.182% |
| Mean | 7.559 | 5.957 | +26.893% |
| Minimum | 6.032 | 4.692 | +28.559% |
The 'Maximum' difference value '+25.182%' for 'Engine' shows colossal (25.182%) increase in 'CPU' volatility.
The 'Mean' difference value '+26.882%' for 'Engine' shows colossal (26.882%) increase in 'CPU' consumption.
The 'Minimum' difference value '+28.559%' for 'Engine' shows colossal (28.559%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 478.382 | 397.02 | +20.493% |
| Mean | 466.514 | 380.64 | +22.56% |
| Minimum | 448.809 | 354.434 | +26.627% |
The 'Maximum' difference value '+20.493%' for 'Engine' shows colossal (20.493%) increase in 'Memory' volatility.
The 'Mean' difference value '+22.56%' for 'Engine' shows colossal (22.56%) increase in 'Memory' consumption.
The 'Minimum' difference value '+26.627%' for 'Engine' shows colossal (26.627%) increase in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 0.824 | 1.152 | -28.472% |
| Mean | 0.789 | 0.866 | -8.937% |
| Minimum | 0.765 | 0.687 | +11.354% |
The 'Maximum' difference value '-28.472%' for 'Botflow' shows colossal (28.472%) decrease in 'CPU' volatility.
The 'Mean' difference value '-8.937%' for 'Botflow' shows massive (8.937%) decrease in 'CPU' consumption.
The 'Minimum' difference value '+11.354%' for 'Botflow' shows colossal (11.354%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 259.082 | 238.559 | +8.603% |
| Mean | 251.871 | 235.283 | +7.05% |
| Minimum | 246.969 | 230.043 | +7.358% |
The 'Maximum' difference value '+8.603%' for 'Botflow' shows massive (8.603%) increase in 'Memory' volatility.
The 'Mean' difference value '+7.05%' for 'Botflow' shows significant (7.05%) increase in 'Memory' consumption.
The 'Minimum' difference value '+7.358%' for 'Botflow' shows significant (7.358%) increase in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 0.001 | 0.001 | 0% |
| Mean | 0.001 | 0.001 | 0% |
| Minimum | 0.001 | 0.001 | 0% |
The 'Maximum' difference value '0.0%' for 'Ui' shows no changes in 'CPU' usage.
The 'Mean' difference value '0.0%' for 'Ui' shows no changes in 'CPU' usage.
The 'Minimum' difference value '0.0%' for 'Ui' shows no changes in 'CPU' usage.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 5.246 | 4.68 | +12.094% |
| Mean | 5.246 | 4.677 | +12.166% |
| Minimum | 5.246 | 4.672 | +12.286% |
The 'Maximum' difference value '+12.094%' for 'Ui' shows colossal (12.094%) increase in 'Memory' volatility.
The 'Mean' difference value '+12.17%' for 'Ui' shows colossal (12.17%) increase in 'Memory' consumption.
The 'Minimum' difference value '+12.286%' for 'Ui' shows colossal (12.286%) increase in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 0.683 | 0.437 | +56.293% |
| Mean | 0.587 | 0.419 | +40.095% |
| Minimum | 0.434 | 0.389 | +11.568% |
The 'Maximum' difference value '+56.293%' for 'Postgres' shows colossal (56.293%) increase in 'CPU' volatility.
The 'Mean' difference value '+40.305%' for 'Postgres' shows colossal (40.305%) increase in 'CPU' consumption.
The 'Minimum' difference value '+11.568%' for 'Postgres' shows colossal (11.568%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 2190.16 | 2494.297 | -12.193% |
| Mean | 2041.246 | 2482.188 | -17.764% |
| Minimum | 1948.174 | 2462.813 | -20.896% |
The 'Maximum' difference value '-12.193%' for 'Postgres' shows colossal (12.193%) decrease in 'Memory' volatility.
The 'Mean' difference value '-17.764%' for 'Postgres' shows colossal (17.764%) decrease in 'Memory' consumption.
The 'Minimum' difference value '-20.896%' for 'Postgres' shows colossal (20.896%) decrease in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 2.655 | 2.189 | +21.288% |
| Mean | 2.618 | 2.033 | +28.771% |
| Minimum | 2.558 | 1.935 | +32.196% |
The 'Maximum' difference value '+21.288%' for 'Redis' shows colossal (21.288%) increase in 'CPU' volatility.
The 'Mean' difference value '+28.771%' for 'Redis' shows colossal (28.771%) increase in 'CPU' consumption.
The 'Minimum' difference value '+32.196%' for 'Redis' shows colossal (32.196%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 36.343 | 38.016 | -4.401% |
| Mean | 36.119 | 37.792 | -4.427% |
| Minimum | 35.761 | 37.434 | -4.469% |
The 'Maximum' difference value '-4.401%' for 'Redis' shows visible (4.401%) decrease in 'Memory' volatility.
The 'Mean' difference value '-4.427%' for 'Redis' shows visible (4.427%) decrease in 'Memory' consumption.
The 'Minimum' difference value '-4.469%' for 'Redis' shows visible (4.469%) decrease in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 770.0 | 467.95 | +64.547% |
| Mean | 451.302 | 368.991 | +22.307% |
| Minimum | 9.992 | 7.982 | +25.182% |
The 'Maximum' difference value '+64.547%' for 'Engine' shows colossal (64.547%) increase in 'CPU' volatility.
The 'Mean' difference value '+22.307%' for 'Engine' shows colossal (22.307%) increase in 'CPU' consumption.
The 'Minimum' difference value '+25.182%' for 'Engine' shows colossal (25.182%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 1092.595 | 512.19 | +113.318% |
| Mean | 818.14 | 475.3 | +72.131% |
| Minimum | 478.382 | 397.02 | +20.493% |
The 'Maximum' difference value '+113.318%' for 'Engine' shows colossal (113.318%) increase in 'Memory' volatility.
The 'Mean' difference value '+72.131%' for 'Engine' shows colossal (72.131%) increase in 'Memory' consumption.
The 'Minimum' difference value '+20.493%' for 'Engine' shows colossal (20.493%) increase in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 234.985 | 126.996 | +85.033% |
| Mean | 120.458 | 82.444 | +46.108% |
| Minimum | 0.824 | 1.152 | -28.472% |
The 'Maximum' difference value '+85.033%' for 'Botflow' shows colossal (85.033%) increase in 'CPU' volatility.
The 'Mean' difference value '+46.108%' for 'Botflow' shows colossal (46.108%) increase in 'CPU' consumption.
The 'Minimum' difference value '-28.472%' for 'Botflow' shows colossal (28.472%) decrease in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 416.926 | 381.486 | +9.29% |
| Mean | 361.321 | 303.759 | +18.95% |
| Minimum | 259.082 | 232.952 | +11.217% |
The 'Maximum' difference value '+9.29%' for 'Botflow' shows massive (9.29%) increase in 'Memory' volatility.
The 'Mean' difference value '+18.95%' for 'Botflow' shows colossal (18.95%) increase in 'Memory' consumption.
The 'Minimum' difference value '+11.217%' for 'Botflow' shows colossal (11.217%) increase in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 0.097 | 0.063 | +53.968% |
| Mean | 0.048 | 0.027 | +75.132% |
| Minimum | 0.001 | 0.001 | 0% |
The 'Maximum' difference value '+53.968%' for 'Ui' shows colossal (53.968%) increase in 'CPU' volatility.
The 'Mean' difference value '+75.132%' for 'Ui' shows colossal (75.132%) increase in 'CPU' consumption.
The 'Minimum' difference value '+16.667%' for 'Ui' shows colossal (16.667%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 5.274 | 5.06 | +4.229% |
| Mean | 5.264 | 4.667 | +12.798% |
| Minimum | 5.246 | 4.241 | +23.697% |
The 'Maximum' difference value '+4.229%' for 'Ui' shows visible (4.229%) increase in 'Memory' volatility.
The 'Mean' difference value '+12.798%' for 'Ui' shows colossal (12.798%) increase in 'Memory' consumption.
The 'Minimum' difference value '+23.697%' for 'Ui' shows colossal (23.697%) increase in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 219.494 | 162.657 | +34.943% |
| Mean | 119.52 | 117.482 | +1.735% |
| Minimum | 0.434 | 0.389 | +11.568% |
The 'Maximum' difference value '+34.943%' for 'Postgres' shows colossal (34.943%) increase in 'CPU' volatility.
The 'Mean' difference value '+1.735%' for 'Postgres' shows changes within the statistical margin of error in 'CPU'.
The 'Minimum' difference value '+11.568%' for 'Postgres' shows colossal (11.568%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 2190.16 | 2494.297 | -12.193% |
| Mean | 1842.176 | 2389.513 | -22.906% |
| Minimum | 1775.748 | 2320.624 | -23.48% |
The 'Maximum' difference value '-12.193%' for 'Postgres' shows colossal (12.193%) decrease in 'Memory' volatility.
The 'Mean' difference value '-22.906%' for 'Postgres' shows colossal (22.906%) decrease in 'Memory' consumption.
The 'Minimum' difference value '-23.48%' for 'Postgres' shows colossal (23.48%) decrease in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 45.144 | 30.999 | +45.631% |
| Mean | 25.567 | 19.969 | +28.035% |
| Minimum | 2.558 | 2.189 | +16.857% |
The 'Maximum' difference value '+45.631%' for 'Redis' shows colossal (45.631%) increase in 'CPU' volatility.
The 'Mean' difference value '+28.035%' for 'Redis' shows colossal (28.035%) increase in 'CPU' consumption.
The 'Minimum' difference value '+16.857%' for 'Redis' shows colossal (16.857%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 39.343 | 40.06 | -1.79% |
| Mean | 38.371 | 39.634 | -3.188% |
| Minimum | 36.343 | 38.016 | -4.401% |
The 'Maximum' difference value '-1.79%' for 'Redis' shows changes within the statistical margin of error in 'Memory'.
The 'Mean' difference value '-3.188%' for 'Redis' shows visible (3.188%) decrease in 'Memory' consumption.
The 'Minimum' difference value '-4.401%' for 'Redis' shows visible (4.401%) decrease in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 770.0 | 467.95 | +64.547% |
| Mean | 440.227 | 356.918 | +23.341% |
| Minimum | 6.032 | 4.692 | +28.559% |
The 'Maximum' difference value '+64.547%' for 'Engine' shows colossal (64.547%) increase in 'CPU' volatility.
The 'Mean' difference value '+23.341%' for 'Engine' shows colossal (23.341%) increase in 'CPU' consumption.
The 'Minimum' difference value '+28.559%' for 'Engine' shows colossal (28.559%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 1092.595 | 512.19 | +113.318% |
| Mean | 809.343 | 472.108 | +71.432% |
| Minimum | 448.809 | 354.434 | +26.627% |
The 'Maximum' difference value '+113.318%' for 'Engine' shows colossal (113.318%) increase in 'Memory' volatility.
The 'Mean' difference value '+71.432%' for 'Engine' shows colossal (71.432%) increase in 'Memory' consumption.
The 'Minimum' difference value '+26.627%' for 'Engine' shows colossal (26.627%) increase in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 234.985 | 126.996 | +85.033% |
| Mean | 117.472 | 79.732 | +47.334% |
| Minimum | 0.765 | 0.687 | +11.354% |
The 'Maximum' difference value '+85.033%' for 'Botflow' shows colossal (85.033%) increase in 'CPU' volatility.
The 'Mean' difference value '+47.334%' for 'Botflow' shows colossal (47.334%) increase in 'CPU' consumption.
The 'Minimum' difference value '+11.354%' for 'Botflow' shows colossal (11.354%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 416.926 | 381.486 | +9.29% |
| Mean | 358.576 | 301.474 | +18.941% |
| Minimum | 246.969 | 230.043 | +7.358% |
The 'Maximum' difference value '+9.29%' for 'Botflow' shows massive (9.29%) increase in 'Memory' volatility.
The 'Mean' difference value '+18.941%' for 'Botflow' shows colossal (18.941%) increase in 'Memory' consumption.
The 'Minimum' difference value '+7.358%' for 'Botflow' shows significant (7.358%) increase in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 0.097 | 0.063 | +53.968% |
| Mean | 0.047 | 0.027 | +77.03% |
| Minimum | 0.001 | 0.001 | 0% |
The 'Maximum' difference value '+53.968%' for 'Ui' shows colossal (53.968%) increase in 'CPU' volatility.
The 'Mean' difference value '+77.03%' for 'Ui' shows colossal (77.03%) increase in 'CPU' consumption.
The 'Minimum' difference value '0.0%' for 'Ui' shows no changes in 'CPU' usage.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 5.274 | 5.06 | +4.229% |
| Mean | 5.263 | 4.667 | +12.781% |
| Minimum | 5.246 | 4.241 | +23.697% |
The 'Maximum' difference value '+4.229%' for 'Ui' shows visible (4.229%) increase in 'Memory' volatility.
The 'Mean' difference value '+12.781%' for 'Ui' shows colossal (12.781%) increase in 'Memory' consumption.
The 'Minimum' difference value '+23.697%' for 'Ui' shows colossal (23.697%) increase in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 219.494 | 162.657 | +34.943% |
| Mean | 116.553 | 113.591 | +2.608% |
| Minimum | 0.434 | 0.389 | +11.568% |
The 'Maximum' difference value '+34.943%' for 'Postgres' shows colossal (34.943%) increase in 'CPU' volatility.
The 'Mean' difference value '+2.608%' for 'Postgres' shows visible (2.608%) increase in 'CPU' consumption.
The 'Minimum' difference value '+11.568%' for 'Postgres' shows colossal (11.568%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 2190.16 | 2494.297 | -12.193% |
| Mean | 1846.833 | 2392.56 | -22.809% |
| Minimum | 1775.748 | 2320.624 | -23.48% |
The 'Maximum' difference value '-12.193%' for 'Postgres' shows colossal (12.193%) decrease in 'Memory' volatility.
The 'Mean' difference value '-22.809%' for 'Postgres' shows colossal (22.809%) decrease in 'Memory' consumption.
The 'Minimum' difference value '-23.48%' for 'Postgres' shows colossal (23.48%) decrease in 'Memory' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 45.144 | 30.999 | +45.631% |
| Mean | 24.995 | 19.372 | +29.023% |
| Minimum | 2.558 | 1.935 | +32.196% |
The 'Maximum' difference value '+45.631%' for 'Redis' shows colossal (45.631%) increase in 'CPU' volatility.
The 'Mean' difference value '+29.023%' for 'Redis' shows colossal (29.023%) increase in 'CPU' consumption.
The 'Minimum' difference value '+32.196%' for 'Redis' shows colossal (32.196%) increase in 'CPU' minimum consumption.
| Type | Build_v2 | Build_v1 | Difference |
|---|---|---|---|
| Maximum | 39.343 | 40.06 | -1.79% |
| Mean | 38.314 | 39.572 | -3.18% |
| Minimum | 35.761 | 37.434 | -4.469% |
The 'Maximum' difference value '-1.79%' for 'Redis' shows changes within the statistical margin of error in 'Memory'.
The 'Mean' difference value '-3.18%' for 'Redis' shows visible (3.18%) decrease in 'Memory' consumption.
The 'Minimum' difference value '-4.469%' for 'Redis' shows visible (4.469%) decrease in 'Memory' minimum consumption.
1.5 Test Anomalies
RampUp: No material runtime anomaly is indicated. The observed increase in activity and database connections follows the expected ramp-up behavior, while setup-only metrics remain concentrated in the startup portion of the test.
MaxLoad: Build_v2 shows several transient CPU spikes on Engine, including an excursion to approximately 674.9 around 00:05:10 and another to approximately 520.1 around 00:06:15. Both return toward the surrounding level, so the pattern is more consistent with short-lived processing bursts than with sustained CPU saturation.
MaxLoad: Build_v2 also shows a transient Engine memory peak of approximately 911.7 around 00:18:10, above the adjacent observations. The series does not collapse afterward, so this is best treated as a localized memory excursion rather than evidence of a failure or restart.
MaxLoad: The Agent Messages time series contains repeated sharp oscillations, with the maximum-handling-time series reaching approximately 552.3 around 00:14:30 before falling back on the next interval. The repeated pattern suggests intermittent variability rather than a single sustained degradation event.
MaxLoad / WholeRun: The Agent Messages spread series contains short-lived dispersion spikes, including an excursion to approximately 28.9 around 00:32:15 followed by a much lower value in the next bucket. This indicates intermittent inconsistency in message handling that is worth monitoring, particularly because messaging is a core user activity.
MaxLoad / WholeRun: Database connections show transient peaks in Build_v2, with a maximum of approximately 116 around 00:02:05. The series subsequently falls rather than remaining elevated, so there is no clear evidence of connection accumulation or a persistent leak from the available data.
All periods: No pod restart, error-rate increase, or zero-resource interruption is indicated in the available report data. The observed anomalies are therefore limited to transient performance/resource excursions rather than explicit stability failures.
2. Stability meta metrics
2.1 Agent activity
2.2 Database connections
Ending Conclusions
Verdict: NO-GO - Build_v2 should not be deployed to clients in its current state.
Overall Assessment: Across the full test execution, Build_v2 demonstrates broad performance degradation compared with Build_v1. The most important customer-facing operations take longer to complete, overall request throughput is lower, and performance consistency has deteriorated across several areas. The degradation is not isolated to a single operation, which makes the current build unsuitable for client-facing deployment without further improvement.
Principal Regressions:
- Agent communication is materially slower. Agent message handling increased by 50.374% for mean execution time, while the 90th-percentile execution time increased by 39.595%. This indicates that agents are likely to experience slower message processing during normal use.
- Workflow processing is slower. Workflow Actions 90th-percentile execution time increased by 39.556%, increasing the time required to perform conversation-related operations.
- Request capacity is reduced. Overall request throughput decreased by 10.586%, while Agent Message throughput decreased by 17.861%. This means Build_v2 processes fewer requests within the same tested workload.
- Some individual operations show substantially larger regressions. The largest deterioration is concentrated in selected operations rather than being uniform across the entire application. Examples include the agent creation operation, which increased by 103.860%, and several conversation workflow operations with substantially higher execution times.
Stability and Resource Concerns: Build_v2 also consumes more resources in several important components. Engine memory increased by 71.432% on average, while Engine CPU increased by 23.341%. Botflow CPU increased by 47.334% on average, and Redis CPU increased by 29.023%. At the same time, PostgreSQL memory consumption decreased by 22.809% on average, indicating that the resource increase is not uniform across the system. No pod restarts were recorded for either build, so the observed degradation is not accompanied by evidence of application crashes during the test.
Important Consistency Concerns: Build_v2 shows a substantial increase in variability across multiple performance areas. For example, Agent Message mean spread increased by 99.941%, while Client Message mean spread increased by 41.505%. Several individual messaging and workflow operations show even larger increases in spread. This means the slower performance is also less predictable, which can make the user experience inconsistent.
Important Improvements: Not all measurements deteriorated. Client Message maximum execution time improved by 10.598%, and PostgreSQL memory consumption decreased materially. These improvements, however, do not compensate for the broader degradation in agent-facing processing, workflow performance, throughput, and consistency.
Stability Events: No critical runtime instability was identified during the test execution. The absence of pod restarts or observed error growth is positive, but it does not offset the performance and efficiency regressions identified above.
Recommendation: Do not promote Build_v2 to a client-facing environment in its current form. The build should first undergo performance optimization focused on agent messaging, workflow processing, overall request capacity, and the components with materially higher resource consumption. A repeat performance comparison should then be performed to confirm that the principal regressions have been reduced before the build is reconsidered for deployment.
Please remember: a few slight changes in a few performance tests do accumulate into one colossal difference. Therefore, please make sure to consult previous reports.