Skip to content

Performance Evaluation

Jump to bottom
Mario Teixeira Lemes edited this page Jan 30, 2024 · 76 revisions

General description

We perform the following performance evaluation of intent layer:

  1. Impact of execution time of intent framework elements;
  2. Impact of number of virtual network functions;
  3. Impact of slice redeployment.

1. Execution time

We first consider the overall slice intent execution time (translating, onboarding and instantiation), measured as the time from when a vertical requests an intent to the time when network instance is created at OSM. In this evaluation, we fixed the number of virtual functions to 2. Then, 10 trials have been performed and then the average value of the execution time has been evaluated. As shown in Fig. 1, the instantiation time within OSM is the predominant factor in the overall execution time, accounting for roughly 93%. Additionally, onboarding descriptors contribute approximately 6%, while the translation time is insignificantly small.

2. Impact of number of Virtual Network Functions (VNFs)

We have generated 5 different NSDs characterized by an increasing number of VFs, ranging from 2 to 6, to verify the impact of number of VNFs. For each case, 10 trials have been performed and then the average value of the overall slice instantiation time has been evaluated. Fig. 2 illustrates a linear increase in the overall instantiation time as the number of VFs (Virtual Functions) rises. This behavior primarily stems from the nature of OSM, which manages the sequential creation and configuration of the VNFDs (Virtual Network Function Descriptors) that form the NSD (Network Service Descriptor). OSM process these descriptors in the order of their appearance within the descriptor, leading to the observed correlation between the number of VFs and the instantiation time.

3. Impact of slice redeployment

In case of service degradations, may be necessary the slice redeployment. As a preliminary implementation, our intent translator sends a Terminate command to OSM to stop execution of the slice and a Delete command to delete the network instance. After, it deploys the slice again considering the initial requirements (number of VFs) of the intent. In this evaluation, we fixed the number of virtual functions to 2. After the intent is instantiated, we started the slice redeployment task. Then, 10 trials have been performed and then the average value of the execution time has been evaluated. Fig. 3 illustrates that the most of the time (62.20%) is used to re-setup of the slice, while to terminate and delete an slice is used approximately 1/3 of the overall time.

4. Hardware/software used in tests

  • OSM (Virtual Machine in GCP):

    • CPU: 4vCPU AMD64;
    • RAM: 16GB;
    • Hard drive: 500GB;
    • OS Version: Ubuntu 22.04 jammy;
    • OSM version: 15.0.

  • OpenStack (Virtual Machine in GCP):

    • CPU: 4vCPU AMD64;
    • RAM: 16GB;
    • Hard drive: 500GB;
    • OS Version: Ubuntu 22.04 jammy
    • OpenStack version: 6.4.0

  • Local Machine:

    • CPU: 10vCPU M1 ARM64;
    • RAM: 16GB;
    • Hard drive: 500GB;
    • OS Version: Sonoma 14.2.1.

Clone this wiki locally