Abstract-Network Function Virtualization (NFV) provides higher flexibility for network operators and reduces the complexity in network service deployment. Using NFV, Virtual Network Functions (VNF) can be located in various network nodes and chained together in a Service Chain (SC) to provide a specific service. Consolidating multiple VNFs in a smaller number of locations would allow to decrease capital expenditures. However, excessive consolidation of VNFs might cause additional latency penalties due to processing-resource sharing, and this is undesirable, as SCs are bounded by service-specific latency requirements. In this paper, we identify two different types of penalties (referred as "costs") related to the processingresource sharing among multiple VNFs: the context switching costs and the upscaling costs. Context switching costs arise when multiple CPU processes (e.g., supporting different VNFs) share the same CPU and thus repeated loading/saving of their context is required. Upscaling costs are incurred by VNFs requiring multi-core implementations, since they suffer a penalty due to the load-balancing needs among CPU cores. These costs affect how the chained VNFs are placed in the network to meet the performance requirement of the SCs. We evaluate their impact while considering SCs with different bandwidth and latency requirements in a scenario of VNF consolidation.
Savi et al. REF considered two penalties include context switching costs (causing by repeated context loading/saving on the same CPU) and upscaling costs (causing by load-balancing needs of VNFs among multiple CPU cores).
Impact of Processing-Resource Sharing on the Placement of Chained Virtual Network Functions
ArXiv
ArXiv
Computer Science