...
| Initial CPU time | Final CPU time | Total CPU used during test | Average CPU per ONSETrequest | Initial CPU% | Initial Memory% | Final CPU% | Final Memory% |
|---|---|---|---|---|---|---|---|
| 00:3602:553300 | 01:4356:2808 | 393 6815 ms | 9.8 ms | 9.4% | 4.4% | 92.3% | 8.9% |
Memory Utilization
| Code Block |
|---|
Number of young garbage collections used during the test: 14681506 Avg. Young garbage collection time: ~5.8 ms per collection Total number of Full garbage collection: 35 Avg. Full garbage collection time: ~112 ms per collection S0C S1C S0U S1U EC EU OC OU MC MU CCSC CCSU YGC YGCT FGC FGCT GCT 204852736.0 204849664.0 17713.7 0.0 704246784.0 68096.0 59110.372845.7 432640699392.0 8611661080.68 7334478336.0 7184976078.43 83209472.0 78019004.24 32124 21.033559 3 0.337584 2.370143 256027648.0 153627648.0 24017.9 0.0 1088293888.0 9318462859.0 82890.4 432640699392.0 143366168780.10 7334482944.0 7188280562.95 83209472.0 78049027.86 17891530 1053.564013 35 0.3371.076 1054.901088 |
Performance Metrics
No. | Metric | Description | Result | Comments |
|---|---|---|---|---|
| 4 | Maximum Simultaneous Executions | Measure the maximum number of simultaneous policy executions that can be achieved whilst maintaining system stability and resource utilization | 10 | DMaaP connection limitations prevented the test from running more than 10 simultaneous threads/ONSETs |
| 5 | Multi-Threaded Response Time | Measure the execution time for onset and abatement in each use case when multiple threads are injecting ONSET events simultaneously | vCPE - 18 ms vFirewall - 55 ms vDNS - 9 ms VOLTE - 9 ms | |
| 6 | Multi Threaded CPU Usage | CPU Usage for each use case when multiple threads are injecting ONSET events simultaneously | 9.8 ms | |
| 7 | Multi Threaded Memory Usage | Memory Usage for each use case when multiple threads are injecting ONSET events simultaneously |