stence with legacy and interoperability among multi- vendor implementations. Service Models: When required, an operator may use NFV infrastructure which is operated by other operators. Performance Indicators of Network Function Virtualization It is possible to create a number of services and applications on flexible network architectures using NFV as a platform. The lack of proper software architecture on servers with the transferal to new generation architecture leads to loss of competitive advantages and time-to-market with the consequences of performance issues. With this, equivalent or better performance can be realized using virtualization as with legacy physical equipment. The usage of hypervisors, virtual switches ad virtual machines for cloud application foundation results into addition of layer of software overhead and associated complexity. (Yang et al., 2016) Hypervisors, virtual switches and virtual machines building the cloud application foundation add layers of software overhead and associated bottlenecks. There are some common NFV performance bottlenecks in designing the physical appliances and these bottlenecks can even multiply when migrating to virtualization. As a result, transition from VM to VM communications lead to expansion of performance issue. (LeBlan, 2014) To bypass NFV performance bottlenecks before there occurrence, packet processing software are highly applicable in software transition with technology. The evaluation of packet processing software requires certain metrics that enables cost-effective value proposition and smooth transition to future requirements. These metrics includes: Equivalent physical and virtual performance. Transparency. Downloaded 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 Virtualizing Network Functions in Software-Defined Networks No major changes required to OS, hypervisor, virtual switch, and management. Accessibility across multi-vendor processors, hardware platforms and NIC. Typical Performance 3-4 Gbps per CPU core assumin