...
<graph grafana memory & CPU SDC>
Results
5 // onboarding
criteria \ Serie | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | Average |
---|---|---|---|---|---|---|---|---|---|---|---|
Success rate (%) | 100 | 100 | 100 | 100 | 100 | 80 | 100 | 100 | 100 | 100 | 98 |
Min duration | |||||||||||
Max duration | |||||||||||
Mean duration | |||||||||||
Average duration | |||||||||||
Comments/Errros |
<graph min/max/mean/average = f(serie)
10 // onboarding
criteria \ Serie | 1 | 2 | 3 | 4 | 5 | Average |
---|---|---|---|---|---|---|
Success rate (%) | 100 | 100 | 100 | 100 | 100 |
Min duration | ||||||
Max duration | ||||||
Mean duration | ||||||
Average duration | ||||||
Comments/Errros |
<graph min/max/mean/average = f(serie)
...
<pour toutes les séries durée =f(time)>
Conclusions
ONAP Guilin is able to support 10 parallel onboard, which is what we do expect.
...
The creation of resources is linear. It means that on serie 10, 9 services have been already created. We could have expected a linear increase of the onboarding duration because the client used for test list several times the services.So the more services in SDC, the bigger the list is. So globally the SDC resources increase continuously because we cannot delete them but it has no direct impact on the onboarding duration. The duration evolution is not linear and the duration may depend on the cluster status.
The more // processing we have, the slower the onboarding this.