Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

PatchDevicesE2E duration (s)Fragment Query duration (s)Service duration (s)Object Size (MB)Object Size #FragmentsGraph

1) Baseline

https://gerrit.onap.org/r/c/cps/+/133482

1,00011.8<0.1 *11.740120.386,000

2,00028.5<0.1 *28.4010.7172,000
5,00087.0<0.1 *86.8141,7430,000
10,000201.0<0.1*201.0083.3860,000

2)

https://gerrit.onap.org/r/c/cps/+/133511/2**

1,0000.50.20.30.386,000

2,0001.00.40.60.7172,000
5,0002.51.11.41.7430,000
10,0007.0 2.94.03.3860,000
1,0003.01.31.70.386,000

2,0005.52.33.20.7172,000
5,00011.05.45.61.7430,000
10,00025.411.713.63.3860,000

...

Query: cps/api/v1/dataspaces/openroadm/anchors/owb-msa221-anchor/node?xpath=/openroadm-devices/openroadm-device[@device-id='C201-7-13A-5A1']&include-descendants=true

Patch

...

: https://gerrit.onap.org/r/c/cps/+/133511/12

ThreadsE2E duration (s)Succes RatioFragment Query duration (s)
10.082100%0.2
20.091100%0.1
30.120100%0.1
50.3100%0.2
100.399.9%0.3
200.599.5%0.5
501.099.4%1.0
1002.399.7%2.3
2007.699.7%6.2
50017.141.4%13.8
1,00015.3 (many connection errors)26.0%11.9

Graphs:

  1. Average E2E Execution Time
  2. Internal Method Counts (total)

Image Added

Observations

  1. From 10 Parallel request (of 10 sequential request) the client can't always connect and we see time out error (succes ratio <100%)
    1. Sequential request are fired faster than actual responses so from DB perspective they are almost parallel request as well 
  2. Database probably already become bottleneck with 2 threads, effectively firening a total of 20 call very quickly. Its know that the DB connection pool/internal will slow down from 12 or more 'parallel' request

Graphs:

  1. Average E2E Execution Time
  2. Internal Method Counts (total)

Image Removed

Observations:

Data sheets

...

View file
nameCpsPerformance.xlsx
height250
View file
nameperformanceTest.zip
height250