Internet Engineering Task Force (IETF) M. Tahhan
Request for Comments: 8204 B. O'Mahony
Category: Informational Intel
ISSN: 2070-1721 A. Morton
AT&T Labs
September 2017
Internet Engineering Task Force (IETF) M. Tahhan
Request for Comments: 8204 B. O'Mahony
Category: Informational Intel
ISSN: 2070-1721 A. Morton
AT&T Labs
September 2017
Benchmarking Virtual Switches in the Open Platform for NFV (OPNFV)
在NFV开放平台（OPNFV）中对虚拟交换机进行基准测试
Abstract
摘要
This memo describes the contributions of the Open Platform for NFV (OPNFV) project on Virtual Switch Performance (VSPERF), particularly in the areas of test setups and configuration parameters for the system under test. This project has extended the current and completed work of the Benchmarking Methodology Working Group in the IETF and references existing literature. The Benchmarking Methodology Working Group has traditionally conducted laboratory characterization of dedicated physical implementations of internetworking functions. Therefore, this memo describes the additional considerations when virtual switches are implemented on general-purpose hardware. The expanded tests and benchmarks are also influenced by the OPNFV mission to support virtualization of the "telco" infrastructure.
本备忘录描述了NFV开放平台（OPNFV）项目对虚拟交换机性能（VSPERF）的贡献，特别是在测试设置和被测系统的配置参数方面。本项目扩展了IETF中基准方法工作组当前和已完成的工作，并参考了现有文献。基准方法工作组传统上对网络互连功能的专用物理实现进行实验室表征。因此，本备忘录描述了在通用硬件上实现虚拟交换机时的其他注意事项。扩展的测试和基准也受到OPNFV任务的影响，以支持“电信”基础设施的虚拟化。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8204.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8204.
Copyright Notice
版权公告
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2017 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(https://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
1.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4
2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Benchmarking Considerations . . . . . . . . . . . . . . . . . 5
3.1. Comparison with Physical Network Functions . . . . . . . 5
3.2. Continued Emphasis on Black-Box Benchmarks . . . . . . . 6
3.3. New Configuration Parameters . . . . . . . . . . . . . . 6
3.4. Flow Classification . . . . . . . . . . . . . . . . . . . 8
3.5. Benchmarks Using Baselines with Resource Isolation . . . 9
4. VSPERF Specification Summary . . . . . . . . . . . . . . . . 11
5. 3x3 Matrix Coverage . . . . . . . . . . . . . . . . . . . . . 18
5.1. Speed of Activation . . . . . . . . . . . . . . . . . . . 19
5.2. Accuracy of Activation . . . . . . . . . . . . . . . . . 19
5.3. Reliability of Activation . . . . . . . . . . . . . . . . 19
5.4. Scale of Activation . . . . . . . . . . . . . . . . . . . 19
5.5. Speed of Operation . . . . . . . . . . . . . . . . . . . 19
5.6. Accuracy of Operation . . . . . . . . . . . . . . . . . . 19
5.7. Reliability of Operation . . . . . . . . . . . . . . . . 20
5.8. Scalability of Operation . . . . . . . . . . . . . . . . 20
5.9. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 20
6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.1. Normative References . . . . . . . . . . . . . . . . . . 21
7.2. Informative References . . . . . . . . . . . . . . . . . 22
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
1.2. Abbreviations . . . . . . . . . . . . . . . . . . . . . . 4
2. Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Benchmarking Considerations . . . . . . . . . . . . . . . . . 5
3.1. Comparison with Physical Network Functions . . . . . . . 5
3.2. Continued Emphasis on Black-Box Benchmarks . . . . . . . 6
3.3. New Configuration Parameters . . . . . . . . . . . . . . 6
3.4. Flow Classification . . . . . . . . . . . . . . . . . . . 8
3.5. Benchmarks Using Baselines with Resource Isolation . . . 9
4. VSPERF Specification Summary . . . . . . . . . . . . . . . . 11
5. 3x3 Matrix Coverage . . . . . . . . . . . . . . . . . . . . . 18
5.1. Speed of Activation . . . . . . . . . . . . . . . . . . . 19
5.2. Accuracy of Activation . . . . . . . . . . . . . . . . . 19
5.3. Reliability of Activation . . . . . . . . . . . . . . . . 19
5.4. Scale of Activation . . . . . . . . . . . . . . . . . . . 19
5.5. Speed of Operation . . . . . . . . . . . . . . . . . . . 19
5.6. Accuracy of Operation . . . . . . . . . . . . . . . . . . 19
5.7. Reliability of Operation . . . . . . . . . . . . . . . . 20
5.8. Scalability of Operation . . . . . . . . . . . . . . . . 20
5.9. Summary . . . . . . . . . . . . . . . . . . . . . . . . . 20
6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
7.1. Normative References . . . . . . . . . . . . . . . . . . 21
7.2. Informative References . . . . . . . . . . . . . . . . . 22
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
The Benchmarking Methodology Working Group (BMWG) has traditionally conducted laboratory characterization of dedicated physical implementations of internetworking functions. The black-box benchmarks of throughput, latency, forwarding rates, and others have served our industry for many years. Now, Network Function Virtualization (NFV) has the goal of transforming how internetwork functions are implemented and therefore has garnered much attention.
基准方法工作组（BMWG）传统上对网络互连功能的专用物理实现进行实验室表征。吞吐量、延迟、转发速率等黑匣子基准多年来一直服务于我们的行业。现在，网络功能虚拟化（NFV）的目标是改变网络功能的实现方式，因此受到了广泛关注。
A virtual switch (vSwitch) is an important aspect of the NFV infrastructure; it provides connectivity between and among physical network functions and virtual network functions. As a result, there are many vSwitch benchmarking efforts but few specifications to guide the many new test design choices. This is a complex problem and an industry-wide work in progress. In the future, several of BMWG's fundamental specifications will likely be updated as more testing experience helps to form consensus around new methodologies, and BMWG should continue to collaborate with all organizations that share the same goal.
虚拟交换机（vSwitch）是NFV基础设施的一个重要方面；它提供物理网络功能和虚拟网络功能之间的连接。因此，有许多vSwitch基准测试工作，但很少有规范来指导许多新的测试设计选择。这是一个复杂的问题，也是整个行业正在进行的工作。未来，随着更多的测试经验有助于就新方法达成共识，BMWG的一些基本规范可能会更新，BMWG应继续与所有具有相同目标的组织合作。
This memo describes the contributions of the Open Platform for NFV (OPNFV) project on Virtual Switch Performance (VSPERF) characterization through the Danube 3.0 (fourth) release [DanubeRel] to the chartered work of the BMWG (with stable references to their test descriptions). This project has extended the current and completed work of the BMWG IETF and references existing literature. For example, the most often referenced RFC is [RFC2544] (which depends on [RFC1242]), so the foundation of the benchmarking work in OPNFV is common and strong. The recommended extensions are specifically in the areas of test setups and configuration parameters for the system under test.
本备忘录描述了开放式NFV平台（OPNFV）项目通过多瑙河3.0（第四版）发行版[DanubeRel]对BMWG特许工作的虚拟交换机性能（VSPERF）表征的贡献（稳定参考其测试说明）。该项目扩展了BMWG IETF当前和已完成的工作，并参考了现有文献。例如，最常引用的RFC是[RFC2544 ]（这取决于[RFC1242]），因此在OPNFV中基准测试工作的基础是通用的和强的。建议的扩展特别适用于被测系统的测试设置和配置参数领域。
See [VSPERFhome] for more background and the OPNFV website for general information [OPNFV].
有关更多背景信息，请参见[VSPERFhome]，有关一般信息，请参见OPNFV网站[OPNFV]。
The authors note that OPNFV distinguishes itself from other open source compute and networking projects through its emphasis on existing "telco" services as opposed to cloud computing. There are many ways in which telco requirements have different emphasis on performance dimensions when compared to cloud computing: support for and transfer of isochronous media streams is one example.
作者指出，OPNFV与其他开源计算和网络项目不同，它强调现有的“电信”服务，而不是云计算。与云计算相比，电信公司的要求在许多方面对性能维度的重视程度有所不同：支持和传输等时媒体流就是一个例子。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”在所有大写字母出现时（如图所示）应按照BCP 14[RFC2119][RFC8174]所述进行解释。
For the purposes of this document, the following abbreviations apply:
在本文件中，以下缩写词适用：
ACK Acknowledge ACPI Advanced Configuration and Power Interface BIOS Basic Input Output System BMWG Benchmarking Methodology Working Group CPDP Control Plane Data Plane CPU Central Processing Unit DIMM Dual In-line Memory Module DPDK Data Plane Development Kit DUT Device Under Test GRUB Grand Unified Bootloader ID Identification IMIX Internet Mix IP Internet Protocol IPPM IP Performance Metrics LAN Local Area Network LTD Level Test Design NFV Network Functions Virtualization NIC Network Interface Card NUMA Non-uniform Memory Access OPNFV Open Platform for NFV OS Operating System PCI Peripheral Component Interconnect PDV Packet Delay Variation SR/IOV Single Root / Input Output Virtualization SUT System Under Test TCP Transmission Control Protocol TSO TCP Segment Offload UDP User Datagram Protocol VM Virtual Machine VNF Virtualised Network Function VSPERF OPNFV vSwitch Performance Project
ACK确认ACPI高级配置和电源接口BIOS基本输入输出系统BMWG基准测试方法工作组CPDP控制平面数据平面CPU中央处理单元DIMM双列直插式内存模块DPDK数据平面开发工具包DUT待测设备GRUB Grand Unified Bootloader ID Identification IMIX Internet MixIP Internet协议IPPM IP性能指标LAN局域网有限公司级别测试设计NFV网络功能虚拟化NIC网络接口卡NUMA非统一内存访问OPNFV开放平台NFV操作系统PCI外围组件互连PDV包延迟变化SR/IOV单根/输入输出虚拟化SUT测试中的系统TCP传输控制协议TSO TCP段卸载UDP用户数据报协议VM虚拟机VNF虚拟化网络功能VSPERF OPNFV vSwitch性能项目
The primary purpose and scope of the memo is to describe key aspects of vSwitch benchmarking, particularly in the areas of test setups and configuration parameters for the system under test, and extend the body of extensive BMWG literature and experience. Initial feedback indicates that many of these extensions may be applicable beyond this memo's current scope (to hardware switches in the NFV infrastructure and to virtual routers, for example). Additionally, this memo serves as a vehicle to include more detail and relevant commentary from BMWG and other open source communities under BMWG's chartered work to characterize the NFV infrastructure.
备忘录的主要目的和范围是描述vSwitch基准测试的关键方面，特别是在测试设置和被测系统的配置参数方面，并扩展BMWG的大量文献和经验。初步反馈表明，这些扩展中的许多可能超出了本备忘录的当前范围（例如，NFV基础设施中的硬件交换机和虚拟路由器）。此外，本备忘录还作为一种工具，包括BMWG和其他开源社区在BMWG特许工作下对NFV基础设施进行描述的更多细节和相关评论。
The benchmarking covered in this memo should be applicable to many types of vSwitches and remain vSwitch agnostic to a great degree. There has been no attempt to track and test all features of any specific vSwitch implementation.
本备忘录中涵盖的基准测试应适用于多种类型的vSwitch，并在很大程度上保持vSwitch不可知性。没有人试图跟踪和测试任何特定vSwitch实现的所有功能。
This section highlights some specific considerations (from [RFC8172]) related to benchmarks for virtual switches. The OPNFV project is sharing its present view on these areas as they develop their specifications in the Level Test Design (LTD) document as defined by [IEEE829].
本节重点介绍与虚拟交换机基准测试相关的一些具体注意事项（来自[RFC8172]）。OPNFV项目在[IEEE829]定义的水平测试设计（有限公司）文件中制定规范时，正在分享其对这些领域的当前观点。
To compare the performance of virtual designs and implementations with their physical counterparts, identical benchmarks are needed. BMWG has developed specifications for many physical network functions. The BMWG has recommended reusing existing benchmarks and methods in [RFC8172], and the OPNFV LTD expands on them as described here. A key configuration aspect for vSwitches is the number of parallel CPU cores required to achieve comparable performance with a given physical device or whether some limit of scale will be reached before the vSwitch can achieve the comparable performance level.
为了将虚拟设计和实现的性能与物理设计和实现的性能进行比较，需要相同的基准测试。BMWG已经为许多物理网络功能制定了规范。BMWG建议重用[RFC8172]中的现有基准和方法，OPNFV有限公司在此基础上进行了扩展。vSwitch的一个关键配置方面是，为实现与给定物理设备的可比性能，需要并行CPU核的数量，或者在vSwitch达到可比性能水平之前，是否会达到一定的规模限制。
It's unlikely that the virtual switch will be the only application running on the SUT, so CPU utilization, cache utilization, and memory footprint should also be recorded for the virtual implementations of internetworking functions. However, internally measured metrics such as these are not benchmarks; they may be useful for the audience (e.g., operations) to know and may also be useful if there is a problem encountered during testing.
虚拟交换机不太可能是在SUT上运行的唯一应用程序，因此还应记录互连功能的虚拟实现的CPU利用率、缓存利用率和内存占用。然而，像这样的内部测量指标不是基准；它们可能有助于让受众（如操作人员）了解，并且在测试过程中遇到问题时也可能有用。
Benchmark comparability between virtual and physical/hardware implementations of equivalent functions will likely place more detailed and exact requirements on the "testing systems" (in terms of stream generation, algorithms to search for maximum values, and their configurations). This is another area for standards development to appreciate; however, this is a topic for a future document.
等效功能的虚拟和物理/硬件实现之间的基准可比性可能会对“测试系统”提出更详细和准确的要求（在流生成、搜索最大值的算法及其配置方面）。这是另一个需要标准开发的领域；但是，这是未来文档的主题。
External observations remain essential as the basis for benchmarks. Internal observations with a fixed specification and interpretation will be provided in parallel to assist the development of operations procedures when the technology is deployed.
外部观察仍然是基准的基础。将同时提供具有固定规范和解释的内部观察，以协助在部署技术时制定操作程序。
A key consideration when conducting any sort of benchmark is trying to ensure the consistency and repeatability of test results. When benchmarking the performance of a vSwitch, there are many factors that can affect the consistency of results; one key factor is matching the various hardware and software details of the SUT. This section lists some of the many new parameters that this project believes are critical to report in order to achieve repeatability.
在进行任何类型的基准测试时，一个关键考虑因素是确保测试结果的一致性和可重复性。在对vSwitch的性能进行基准测试时，有许多因素会影响结果的一致性；一个关键因素是匹配SUT的各种硬件和软件细节。本节列出了许多新参数中的一些，本项目认为这些参数对于实现可重复性至关重要。
It has been the goal of the project to produce repeatable results, and a large set of the parameters believed to be critical is provided so that the benchmarking community can better appreciate the increase in configuration complexity inherent in this work. The parameter set below is assumed sufficient for the infrastructure in use by the VSPERF project to obtain repeatable results from test to test.
项目的目标是产生可重复的结果，并提供了大量被认为是关键的参数，以便基准测试社区能够更好地理解这项工作中固有的配置复杂性的增加。假设下面的参数集足以使VSPERF项目使用的基础结构从一个测试到另一个测试获得可重复的结果。
Hardware details (platform, processor, memory, and network) including:
硬件详细信息（平台、处理器、内存和网络），包括：
o BIOS version, release date, and any configurations that were modified
o BIOS版本、发布日期和任何已修改的配置
o Power management at all levels (ACPI sleep states, processor package, OS, etc.)
o 各级电源管理（ACPI睡眠状态、处理器包、操作系统等）
o CPU microcode level
o CPU微码级
o Number of enabled cores
o 启用的核心数
o Number of cores used for the test
o 用于测试的芯数
o Memory information (type and size)
o 内存信息（类型和大小）
o Memory DIMM configurations (quad rank performance may not be the same as dual rank) in size, frequency, and slot locations
o 内存DIMM配置（四列性能可能不同于双列）的大小、频率和插槽位置
o Number of physical NICs and their details (manufacturer, versions, type, and the PCI slot they are plugged into)
o 物理NIC的数量及其详细信息（制造商、版本、类型以及它们插入的PCI插槽）
o NIC interrupt configuration (and any special features in use)
o NIC中断配置（以及使用中的任何特殊功能）
o PCI configuration parameters (payload size, early ACK option, etc.)
o PCI配置参数（有效负载大小、早期确认选项等）
Software details including:
软件详细信息包括：
o OS RunLevel
o 操作系统运行级
o OS version (for host and VNF)
o 操作系统版本（适用于主机和VNF）
o Kernel version (for host and VNF)
o 内核版本（用于主机和VNF）
o GRUB boot parameters (for host and VNF)
o GRUB引导参数（用于主机和VNF）
o Hypervisor details (type and version)
o 虚拟机监控程序详细信息（类型和版本）
o Selected vSwitch, version number, or commit ID used
o 使用选定的vSwitch、版本号或提交ID
o vSwitch launch command line if it has been parameterized
o vSwitch启动命令行（如果已参数化）
o Memory allocation to the vSwitch
o 向vSwitch分配内存
o Which NUMA node it is using and how many memory channels
o 它正在使用哪个NUMA节点以及有多少个内存通道
o DPDK or any other software dependency version number or commit ID used
o DPDK或使用的任何其他软件依赖项版本号或提交ID
o Memory allocation to a VM - if it's from Hugepages/elsewhere
o 向VM分配内存-如果它来自Hugepages/其他地方
o VM storage type - snapshot, independent persistent, independent non-persistent
o VM存储类型-快照、独立持久、独立非持久
o Number of VMs
o 虚拟机数量
o Number of virtual NICs (vNICs) - versions, type, and driver
o 虚拟NIC（VNIC）的数量-版本、类型和驱动程序
o Number of virtual CPUs and their core affinity on the host
o 主机上的虚拟CPU数量及其核心关联性
o Number of vNICs and their interrupt configurations
o VNIC的数量及其中断配置
o Thread affinitization for the applications (including the vSwitch itself) on the host
o 主机上应用程序（包括vSwitch本身）的线程亲缘关系
o Details of resource isolation, such as CPUs designated for Host/ Kernel (isolcpu) and CPUs designated for specific processes (taskset).
o 资源隔离的详细信息，例如为主机/内核指定的CPU（isolcpu）和为特定进程指定的CPU（任务集）。
Test traffic information:
测试交通信息：
o Test duration
o 测试持续时间
o Number of flows
o 流量数量
o Traffic type - UDP, TCP, and others
o 流量类型-UDP、TCP和其他
o Frame Sizes - fixed or IMIX [RFC6985] (note that with [IEEE802.1ac], frames may be longer than 1500 bytes and up to 2000 bytes)
o 帧大小-固定或IMIX[RFC6985]（请注意，对于[IEEE802.1ac]，帧的长度可能超过1500字节，最多可达2000字节）
o Deployment Scenario - defines the communications path in the SUT
o 部署场景-定义SUT中的通信路径
Virtual switches group packets into flows by processing and matching particular packet or frame header information, or by matching packets based on the input ports. Thus, a flow can be thought of as a sequence of packets that have the same set of header field values or have arrived on the same physical or logical port. Performance results can vary based on the parameters the vSwitch uses to match for a flow. The recommended flow classification parameters for any vSwitch performance tests are: the input port (physical or logical), the source MAC address, the destination MAC address, the source IP address, the destination IP address, and the Ethernet protocol type field (although classification may take place on other fields, such as source and destination transport port numbers). It is essential to increase the flow timeout time on a vSwitch before conducting any performance tests that do not intend to measure the flow setup time (see Section 3 of [RFC2889]). Normally, the first packet of a particular stream will install the flow in the virtual switch, which introduces additional latency; subsequent packets of the same flow are not subject to this latency if the flow is already installed on the vSwitch.
虚拟交换机通过处理和匹配特定的数据包或帧头信息，或根据输入端口匹配数据包，将数据包分组到流中。因此，可以将流视为具有相同的报头字段值集或到达相同物理或逻辑端口的数据包序列。性能结果可能因vSwitch用于匹配流的参数而异。任何vSwitch性能测试的建议流量分类参数为：输入端口（物理或逻辑）、源MAC地址、目标MAC地址、源IP地址、目标IP地址和以太网协议类型字段（虽然可能会在其他字段上进行分类，如源和目标传输端口号）。在进行任何不打算测量流量设置时间的性能测试之前，必须增加vSwitch上的流量超时时间（请参阅[RFC2889]第3节）。通常，特定流的第一个数据包将在虚拟交换机中安装该流，这会引入额外的延迟；如果该流已安装在vSwitch上，则相同流的后续数据包不受此延迟的影响。
This outline describes the measurement of baselines with isolated resources at a high level, which is the intended approach at this time.
本大纲描述了在高水平上使用孤立资源测量基线，这是目前的预期方法。
1. Baselines:
1. 基线：
* Optional: Benchmark platform forwarding capability without a vSwitch or VNF for at least 72 hours (serves as a means of platform validation and a means to obtain the base performance for the platform in terms of its maximum forwarding rate and latency).
* 可选：在不使用vSwitch或VNF的情况下，至少72小时的基准平台转发能力（作为平台验证的一种手段，以及从最大转发速率和延迟方面获得平台基本性能的一种手段）。
__
+--------------------------------------------------+ |
| +------------------------------------------+ | |
| | | | |
| | Simple Forwarding App | | Host
| | | | |
| +------------------------------------------+ | |
| | NIC | | |
+---+------------------------------------------+---+ __|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
__
+--------------------------------------------------+ |
| +------------------------------------------+ | |
| | | | |
| | Simple Forwarding App | | Host
| | | | |
| +------------------------------------------+ | |
| | NIC | | |
+---+------------------------------------------+---+ __|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
Figure 1: Benchmark Platform Forwarding Capability
图1：基准平台转发能力
* Benchmark VNF forwarding capability with direct connectivity (vSwitch bypass, e.g., SR/IOV) for at least 72 hours (serves as a means of VNF validation and a means to obtain the base performance for the VNF in terms of its maximum forwarding rate and latency). The metrics gathered from this test will serve as a key comparison point for vSwitch bypass technologies performance and vSwitch performance.
* 具有直接连接（vSwitch bypass，例如SR/IOV）的基准VNF转发能力至少72小时（作为VNF验证的一种手段，以及在最大转发速率和延迟方面获得VNF基本性能的一种手段）。从该测试中收集的指标将作为vSwitch bypass technologies性能和vSwitch性能的关键比较点。
__
+--------------------------------------------------+ __ |
| +------------------------------------------+ | | |
| | | | Host/ |
| | VNF | | Guest |
| | | | | |
| +------------------------------------------+ | __| |
| | Passthrough/SR-IOV | | Host
| +------------------------------------------+ | |
| | NIC | | |
+---+------------------------------------------+---+ __|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
__
+--------------------------------------------------+ __ |
| +------------------------------------------+ | | |
| | | | Host/ |
| | VNF | | Guest |
| | | | | |
| +------------------------------------------+ | __| |
| | Passthrough/SR-IOV | | Host
| +------------------------------------------+ | |
| | NIC | | |
+---+------------------------------------------+---+ __|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
Figure 2: Benchmark VNF Forwarding Capability
图2：基准VNF转发能力
* Benchmarking with isolated resources alone and with other resources (both hardware and software) disabled; for example, vSwitch and VM are SUT.
* 单独使用隔离资源和禁用其他资源（硬件和软件）进行基准测试；例如，vSwitch和VM是SUT。
* Benchmarking with isolated resources alone, thus leaving some resources unused.
* 仅使用孤立的资源进行基准测试，从而留下一些未使用的资源。
* Benchmarking with isolated resources and all resources occupied.
* 使用孤立的资源和占用的所有资源进行基准测试。
2. Next Steps:
2. 下一步：
* Limited sharing
* 有限分享
* Production scenarios
* 生产场景
* Stressful scenarios
* 压力情景
The overall specification in preparation is referred to as a Level Test Design (LTD) document, which will contain a suite of performance tests. The base performance tests in the LTD are based on the pre-existing specifications developed by the BMWG to test the performance of physical switches. These specifications include:
编制中的总体规范称为水平测试设计（LTD）文件，其中包含一套性能测试。有限公司的基本性能测试基于BMWG制定的现有规范，以测试物理交换机的性能。这些规格包括：
o Benchmarking Methodology for Network Interconnect Devices [RFC2544]
o 网络互连设备的基准测试方法[RFC2544]
o Benchmarking Methodology for LAN Switching [RFC2889]
o 局域网交换的基准测试方法[RFC2889]
o Device Reset Characterization [RFC6201]
o 器件复位特性[RFC6201]
o Packet Delay Variation Applicability Statement [RFC5481]
o 数据包延迟变化适用性声明[RFC5481]
The two most recent RFCs above ([RFC6201] and [RFC5481]) are being applied in benchmarking for the first time and represent a development challenge for test equipment developers. Fortunately, many members of the testing system community have engaged on the VSPERF project, including an open source test system.
上述两个最新的RFC（[RFC6201]和[RFC5481]）首次应用于基准测试，这对测试设备开发人员来说是一个开发挑战。幸运的是，测试系统社区的许多成员都参与了VSPERF项目，包括一个开源测试系统。
In addition to this, the LTD also reuses the terminology defined by:
除此之外，有限公司还重复使用以下术语：
o Benchmarking Terminology for LAN Switching Devices [RFC2285]
o 局域网交换设备的基准术语[RFC2285]
It is recommended that these references be included in future benchmarking specifications:
建议在未来的基准规范中包括这些参考：
o Methodology for IP Multicast Benchmarking [RFC3918]
o IP多播基准测试方法[RFC3918]
o Packet Reordering Metrics [RFC4737]
o 数据包重新排序度量[RFC4737]
As one might expect, the most fundamental internetworking characteristics of throughput and latency remain important when the switch is virtualized, and these benchmarks figure prominently in the specification.
正如人们所期望的，当交换机被虚拟化时，吞吐量和延迟的最基本的网络互连特性仍然很重要，这些基准在规范中占有重要地位。
When considering characteristics important to "telco" network functions, additional performance metrics are needed. In this case, the project specifications have referenced metrics from the IETF IP Performance Metrics (IPPM) literature. This means that the latency test described in [RFC2544] is replaced by measurement of a metric derived from IPPM's [RFC7679], where a set of statistical summaries will be provided (mean, max, min, and percentiles). Further metrics planned to be benchmarked include packet delay variation as defined by [RFC5481], reordering, burst behaviour, DUT availability, DUT
在考虑对“电信”网络功能很重要的特征时，需要额外的性能指标。在这种情况下，项目规范引用了IETF IP性能指标（IPPM）文献中的指标。这意味着[RFC2544]中描述的延迟测试被IPPM[RFC7679]中衍生的度量所取代，其中将提供一组统计摘要（平均值、最大值、最小值和百分位数）。计划进行基准测试的其他指标包括[RFC5481]定义的数据包延迟变化、重新排序、突发行为、DUT可用性、DUT
capacity, and packet loss in long-term testing at the throughput level, where some low level of background loss may be present and characterized.
吞吐量水平的长期测试中的容量和数据包丢失，其中可能存在并表征一些低水平的背景丢失。
Tests have been designed to collect the metrics below:
测试旨在收集以下指标：
o Throughput tests are designed to measure the maximum forwarding rate (in frames per second, fps) and bit rate (in Mbps) for a constant load (as defined by [RFC1242]) without traffic loss.
o 吞吐量测试旨在测量恒定负载（如[RFC1242]所定义）下无流量损失的最大转发速率（以帧/秒为单位，fps）和比特率（以Mbps为单位）。
o Packet and frame-delay distribution tests are designed to measure the average minimum and maximum packet (and/or frame) delay for constant loads.
o 分组和帧延迟分布测试旨在测量恒定负载下的平均最小和最大分组（和/或帧）延迟。
o Packet delay tests are designed to understand latency distribution for different packet sizes and to uncover outliers over an extended test run.
o 数据包延迟测试旨在了解不同数据包大小的延迟分布，并在扩展测试运行中发现异常值。
o Scalability tests are designed to understand how the virtual switch performs with an increasing number of flows, number of active ports, configuration complexity of the forwarding logic, etc.
o 可伸缩性测试旨在了解虚拟交换机在流数量、活动端口数量、转发逻辑的配置复杂性等不断增加的情况下的性能。
o Stream performance tests (with TCP or UDP) are designed to measure bulk data transfer performance, i.e., how fast systems can send and receive data through the switch.
o 流性能测试（使用TCP或UDP）旨在测量批量数据传输性能，即系统通过交换机发送和接收数据的速度。
o Control-path and data-path coupling tests are designed to understand how closely the data path and the control path are coupled, as well as the effect of this coupling on the performance of the DUT (for example, delay of the initial packet of a flow).
o 控制路径和数据路径耦合测试旨在了解数据路径和控制路径的耦合程度，以及这种耦合对DUT性能的影响（例如，流的初始数据包的延迟）。
o CPU and memory consumption tests are designed to understand the virtual switch's footprint on the system and are conducted as auxiliary measurements with the benchmarks above. They include CPU utilization, cache utilization, and memory footprint.
o CPU和内存消耗测试旨在了解虚拟交换机在系统上的占地面积，并使用上述基准进行辅助测量。它们包括CPU利用率、缓存利用率和内存占用。
o The so-called "soak" tests, where the selected test is conducted over a long period of time (with an ideal duration of 24 hours but only long enough to determine that stability issues exist when found; there is no requirement to continue a test when a DUT exhibits instability over time). The key performance characteristics and benchmarks for a DUT are determined (using short duration tests) prior to conducting soak tests. The purpose of soak tests is to capture transient changes in performance, which may occur due to infrequent processes, memory leaks, or the low-probability coincidence of two or more processes. The stability of the DUT is the paramount consideration, so
o 所谓的“浸泡”试验，其中所选试验在较长时间内进行（理想持续时间为24小时，但仅足以确定发现时存在稳定性问题；当DUT随时间呈现不稳定性时，无需继续进行试验）。在进行静置试验之前，确定DUT的关键性能特征和基准（使用短时试验）。浸泡测试的目的是捕获性能的瞬时变化，这可能是由于不频繁的进程、内存泄漏或两个或多个进程的低概率重合引起的。DUT的稳定性是首要考虑因素，因此
performance must be evaluated periodically during continuous testing, and this results in use of frame rate metrics [RFC2889] instead of throughput [RFC2544] (which requires stopping traffic to allow time for all traffic to exit internal queues), for example.
例如，在连续测试期间，必须定期评估性能，这会导致使用帧速率指标[RFC2889]而不是吞吐量[RFC2544]（这需要停止流量以允许所有流量有时间退出内部队列）。
Additional test specification development should include:
其他测试规范的制定应包括：
o Request/response performance tests (with TCP or UDP), which measure the transaction rate through the switch.
o 请求/响应性能测试（使用TCP或UDP），通过交换机测量事务速率。
o Noisy neighbor tests, in order to understand the effects of resource sharing on the performance of a virtual switch.
o 噪声邻居测试，以了解资源共享对虚拟交换机性能的影响。
o Tests derived from examination of ETSI NFV Draft GS IFA003 requirements [IFA003] on characterization of acceleration technologies applied to vSwitches.
o 根据ETSI NFV草案GS IFA003要求[IFA003]对应用于VSwitch的加速技术特性的检查得出的试验。
The flexibility of deployment of a virtual switch within a network means that it is necessary to characterize the performance of a vSwitch in various deployment scenarios. The deployment scenarios under consideration are shown in the following figures:
在网络中部署虚拟交换机的灵活性意味着有必要描述vSwitch在各种部署场景中的性能。正在考虑的部署方案如下图所示：
__
+--------------------------------------------------+ |
| +--------------------+ | |
| | | | |
| | v | | Host
| +--------------+ +--------------+ | |
| | PHY Port | vSwitch | PHY Port | | |
+---+--------------+------------+--------------+---+ __|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
__
+--------------------------------------------------+ |
| +--------------------+ | |
| | | | |
| | v | | Host
| +--------------+ +--------------+ | |
| | PHY Port | vSwitch | PHY Port | | |
+---+--------------+------------+--------------+---+ __|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
Figure 3: Physical Port to Virtual Switch to Physical Port
图3：物理端口到虚拟交换机到物理端口
__
+---------------------------------------------------+ |
| | |
| +-------------------------------------------+ | |
| | Application | | |
| +-------------------------------------------+ | |
| ^ : | |
| | | | | Guest
| : v | |
| +---------------+ +---------------+ | |
| | Logical Port 0| | Logical Port 1| | |
+---+---------------+-----------+---------------+---+ __|
^ :
| |
: v __
+---+---------------+----------+---------------+---+ |
| | Logical Port 0| | Logical Port 1| | |
| +---------------+ +---------------+ | |
| ^ : | |
| | | | | Host
| : v | |
| +--------------+ +--------------+ | |
| | PHY Port | vSwitch | PHY Port | | |
+---+--------------+------------+--------------+---+ __|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
__
+---------------------------------------------------+ |
| | |
| +-------------------------------------------+ | |
| | Application | | |
| +-------------------------------------------+ | |
| ^ : | |
| | | | | Guest
| : v | |
| +---------------+ +---------------+ | |
| | Logical Port 0| | Logical Port 1| | |
+---+---------------+-----------+---------------+---+ __|
^ :
| |
: v __
+---+---------------+----------+---------------+---+ |
| | Logical Port 0| | Logical Port 1| | |
| +---------------+ +---------------+ | |
| ^ : | |
| | | | | Host
| : v | |
| +--------------+ +--------------+ | |
| | PHY Port | vSwitch | PHY Port | | |
+---+--------------+------------+--------------+---+ __|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
Figure 4: Physical Port to Virtual Switch to VNF to Virtual Switch to Physical Port
图4：物理端口到虚拟交换机到VNF到虚拟交换机到物理端口
__
+----------------------+ +----------------------+ |
| Guest 1 | | Guest 2 | |
| +---------------+ | | +---------------+ | |
| | Application | | | | Application | | |
| +---------------+ | | +---------------+ | |
| ^ | | | ^ | | |
| | v | | | v | | Guests
| +---------------+ | | +---------------+ | |
| | Logical Ports | | | | Logical Ports | | |
| | 0 1 | | | | 0 1 | | |
+---+---------------+--+ +---+---------------+--+__|
^ : ^ :
| | | |
: v : v _
+---+---------------+---------+---------------+--+ |
| | 0 1 | | 3 4 | | |
| | Logical Ports | | Logical Ports | | |
| +---------------+ +---------------+ | |
| ^ | ^ | | | Host
| | \-----------------/ v | |
| +--------------+ +--------------+ | |
| | PHY Ports | vSwitch | PHY Ports | | |
+---+--------------+----------+--------------+---+_|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
__
+----------------------+ +----------------------+ |
| Guest 1 | | Guest 2 | |
| +---------------+ | | +---------------+ | |
| | Application | | | | Application | | |
| +---------------+ | | +---------------+ | |
| ^ | | | ^ | | |
| | v | | | v | | Guests
| +---------------+ | | +---------------+ | |
| | Logical Ports | | | | Logical Ports | | |
| | 0 1 | | | | 0 1 | | |
+---+---------------+--+ +---+---------------+--+__|
^ : ^ :
| | | |
: v : v _
+---+---------------+---------+---------------+--+ |
| | 0 1 | | 3 4 | | |
| | Logical Ports | | Logical Ports | | |
| +---------------+ +---------------+ | |
| ^ | ^ | | | Host
| | \-----------------/ v | |
| +--------------+ +--------------+ | |
| | PHY Ports | vSwitch | PHY Ports | | |
+---+--------------+----------+--------------+---+_|
^ :
| |
: v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
Figure 5: Physical Port to Virtual Switch to VNF to Virtual Switch to VNF to Virtual Switch to Physical Port
图5：物理端口到虚拟交换机到VNF到虚拟交换机到VNF到虚拟交换机到物理端口
__
+---------------------------------------------------+ |
| | |
| +-------------------------------------------+ | |
| | Application | | |
| +-------------------------------------------+ | |
| ^ | |
| | | | Guest
| : | |
| +---------------+ | |
| | Logical Port 0| | |
+---+---------------+-------------------------------+ __|
^
|
: __
+---+---------------+------------------------------+ |
| | Logical Port 0| | |
| +---------------+ | |
| ^ | |
| | | | Host
| : | |
| +--------------+ | |
| | PHY Port | vSwitch | |
+---+--------------+------------ -------------- ---+ __|
^
|
:
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
__
+---------------------------------------------------+ |
| | |
| +-------------------------------------------+ | |
| | Application | | |
| +-------------------------------------------+ | |
| ^ | |
| | | | Guest
| : | |
| +---------------+ | |
| | Logical Port 0| | |
+---+---------------+-------------------------------+ __|
^
|
: __
+---+---------------+------------------------------+ |
| | Logical Port 0| | |
| +---------------+ | |
| ^ | |
| | | | Host
| : | |
| +--------------+ | |
| | PHY Port | vSwitch | |
+---+--------------+------------ -------------- ---+ __|
^
|
:
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
Figure 6: Physical Port to Virtual Switch to VNF
图6：虚拟交换机到VNF的物理端口
__
+---------------------------------------------------+ |
| | |
| +-------------------------------------------+ | |
| | Application | | |
| +-------------------------------------------+ | |
| : | |
| | | | Guest
| v | |
| +---------------+ | |
| | Logical Port | | |
+-------------------------------+---------------+---+ __|
:
|
v __
+------------------------------+---------------+---+ |
| | Logical Port | | |
| +---------------+ | |
| : | |
| | | | Host
| v | |
| +--------------+ | |
| vSwitch | PHY Port | | |
+-------------------------------+--------------+---+ __|
:
|
v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
__
+---------------------------------------------------+ |
| | |
| +-------------------------------------------+ | |
| | Application | | |
| +-------------------------------------------+ | |
| : | |
| | | | Guest
| v | |
| +---------------+ | |
| | Logical Port | | |
+-------------------------------+---------------+---+ __|
:
|
v __
+------------------------------+---------------+---+ |
| | Logical Port | | |
| +---------------+ | |
| : | |
| | | | Host
| v | |
| +--------------+ | |
| vSwitch | PHY Port | | |
+-------------------------------+--------------+---+ __|
:
|
v
+--------------------------------------------------+
| |
| Traffic Generator |
| |
+--------------------------------------------------+
Figure 7: VNF to Virtual Switch to Physical Port
图7:VNF到虚拟交换机到物理端口
__
+----------------------+ +----------------------+ |
| Guest 1 | | Guest 2 | |
| +---------------+ | | +---------------+ | |
| | Application | | | | Application | | |
| +---------------+ | | +---------------+ | |
| | | | ^ | |
| v | | | | | Guests
| +---------------+ | | +---------------+ | |
| | Logical Ports | | | | Logical Ports | | |
| | 0 | | | | 0 | | |
+---+---------------+--+ +---+---------------+--+__|
: ^
| |
v : _
+---+---------------+---------+---------------+--+ |
| | 1 | | 1 | | |
| | Logical Ports | | Logical Ports | | |
| +---------------+ +---------------+ | |
| | ^ | | Host
| \-----------------/ | |
| | |
| vSwitch | |
+------------------------------------------------+_|
__
+----------------------+ +----------------------+ |
| Guest 1 | | Guest 2 | |
| +---------------+ | | +---------------+ | |
| | Application | | | | Application | | |
| +---------------+ | | +---------------+ | |
| | | | ^ | |
| v | | | | | Guests
| +---------------+ | | +---------------+ | |
| | Logical Ports | | | | Logical Ports | | |
| | 0 | | | | 0 | | |
+---+---------------+--+ +---+---------------+--+__|
: ^
| |
v : _
+---+---------------+---------+---------------+--+ |
| | 1 | | 1 | | |
| | Logical Ports | | Logical Ports | | |
| +---------------+ +---------------+ | |
| | ^ | | Host
| \-----------------/ | |
| | |
| vSwitch | |
+------------------------------------------------+_|
Figure 8: VNF to Virtual Switch to VNF
图8:VNF到虚拟交换机到VNF
A set of deployment scenario figures is available on the VSPERF "Test Methodology" wiki page [TestTopo].
VSPERF“测试方法”wiki页面[TestTopo]上提供了一组部署场景图。
This section organizes the many existing test specifications into the "3x3" matrix (introduced in [RFC8172]). Because the LTD specification ID names are quite long, this section is organized into lists for each occupied cell of the matrix (not all are occupied; also, the matrix has grown to 3x4 to accommodate scale metrics when displaying the coverage of many metrics/benchmarks). The current version of the LTD specification is available; see [LTD].
本节将许多现有测试规范组织到“3x3”矩阵中（在[RFC8172]中介绍）。由于LTD规范ID名称相当长，因此本节被组织为矩阵中每个占用单元的列表（并非所有单元都被占用；此外，矩阵已增长到3x4，以在显示许多度量/基准的覆盖范围时容纳比例度量）。有限公司规范的当前版本可用；见[有限公司]。
The tests listed below assess the activation of paths in the data plane rather than the control plane.
下面列出的测试评估数据平面而非控制平面中路径的激活。
A complete list of tests with short summaries is available on the VSPERF "LTD Test Spec Overview" wiki page [LTDoverV].
VSPERF“LTD测试规范概述”维基页面[LTDoverV]上提供了完整的测试列表和简短摘要。
o Activation.RFC2889.AddressLearningRate
o Activation.RFC2889.AddressLearningRate
o PacketLatency.InitialPacketProcessingLatency
o PacketLatency.InitialPacketProcessingLatency
o CPDP.Coupling.Flow.Addition
o CPDP.Coupling.Flow.Addition
o Throughput.RFC2544.SystemRecoveryTime
o 吞吐量.RFC2544.SystemRecoveryTime
o Throughput.RFC2544.ResetTime
o 吞吐量.RFC2544.ResetTime
o Activation.RFC2889.AddressCachingCapacity
o Activation.RFC2889.AddressCachingCapacity
o Throughput.RFC2544.PacketLossRate
o 吞吐量.RFC2544.PacketLossRate
o Stress.RFC2544.0PacketLoss
o Stress.RFC2544.0包装损耗
o Throughput.RFC2544.PacketLossRateFrameModification
o 吞吐量.RFC2544.packetlossrateframedition
o Throughput.RFC2544.BackToBackFrames
o 吞吐量.RFC2544.BackToBackFrames
o Throughput.RFC2889.MaxForwardingRate
o 吞吐量.RFC2889.MaxForwardingRate
o Throughput.RFC2889.ForwardPressure
o 吞吐量。RFC2889。前向压力
o Throughput.RFC2889.BroadcastFrameForwarding
o 吞吐量.RFC2889.BroadcastFrameForwarding
o Throughput.RFC2544.WorstN-BestN
o 吞吐量.RFC2544.WorstN-BestN
o Throughput.Overlay.Network.<tech>.RFC2544.PacketLossRatio
o 吞吐量.Overlay.Network.<tech>.RFC2544.PacketLossRatio
o Throughput.RFC2889.ErrorFramesFiltering
o 吞吐量.RFC2889.ErrorFramesFiltering
o Throughput.RFC2544.Profile
o 吞吐量.RFC2544.Profile
o Throughput.RFC2889.Soak
o 吞吐量.RFC2889.0
o Throughput.RFC2889.SoakFrameModification
o 吞吐量.RFC2889.SoakFrameModification
o PacketDelayVariation.RFC3393.Soak
o PacketDelayVariation.RFC3393.0
o Scalability.RFC2544.0PacketLoss
o 可扩展性。RFC2544.0 PacketLoss
o MemoryBandwidth.RFC2544.0PacketLoss.Scalability
o MemoryBandwidth.RFC2544.0 packetLoss.Scalability
o Scalability.VNF.RFC2544.PacketLossProfile
o Scalability.VNF.RFC2544.PacketLossProfile
o Scalability.VNF.RFC2544.PacketLossRatio
o Scalability.VNF.RFC2544.PacketLossRatio
|---------------------------------------------------------------------|
| | | | | |
| | SPEED | ACCURACY | RELIABILITY | SCALE |
| | | | | |
|---------------------------------------------------------------------|
| | | | | |
| Activation | X | X | X | X |
| | | | | |
|---------------------------------------------------------------------|
| | | | | |
| Operation | X | X | X | X |
| | | | | |
|---------------------------------------------------------------------|
| | | | | |
| De-activation| | | | |
| | | | | |
|---------------------------------------------------------------------|
|---------------------------------------------------------------------|
| | | | | |
| | SPEED | ACCURACY | RELIABILITY | SCALE |
| | | | | |
|---------------------------------------------------------------------|
| | | | | |
| Activation | X | X | X | X |
| | | | | |
|---------------------------------------------------------------------|
| | | | | |
| Operation | X | X | X | X |
| | | | | |
|---------------------------------------------------------------------|
| | | | | |
| De-activation| | | | |
| | | | | |
|---------------------------------------------------------------------|
Benchmarking activities as described in this memo are limited to technology characterization of a Device Under Test/System Under Test (DUT/SUT) using controlled stimuli in a laboratory environment with dedicated address space and the constraints specified in the sections above.
本备忘录中所述的基准测试活动仅限于在具有专用地址空间的实验室环境中，使用受控刺激和上述章节中规定的约束条件，对被测设备/被测系统（DUT/SUT）进行技术表征。
The benchmarking network topology will be an independent test setup and MUST NOT be connected to devices that may forward the test traffic into a production network or misroute traffic to the test management network.
基准网络拓扑将是一个独立的测试设置，不得连接到可能将测试流量转发到生产网络或将流量错误路由到测试管理网络的设备。
Further, benchmarking is performed on a "black-box" basis and relies solely on measurements observable external to the DUT/SUT.
此外，基准测试是在“黑盒”基础上进行的，仅依赖于DUT/SUT外部可观察到的测量。
Special capabilities SHOULD NOT exist in the DUT/SUT specifically for benchmarking purposes. Any implications for network security arising from the DUT/SUT SHOULD be identical in the lab and in production networks.
DUT/SUT中不应存在专门用于基准测试的特殊能力。DUT/SUT对网络安全的任何影响应在实验室和生产网络中相同。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<https://www.rfc-editor.org/info/rfc2119>.
[RFC2285] Mandeville, R., "Benchmarking Terminology for LAN Switching Devices", RFC 2285, DOI 10.17487/RFC2285, February 1998, <https://www.rfc-editor.org/info/rfc2285>.
[RFC2285]Mandeville，R.，“局域网交换设备的基准术语”，RFC 2285，DOI 10.17487/RFC2285，1998年2月<https://www.rfc-editor.org/info/rfc2285>.
[RFC2544] Bradner, S. and J. McQuaid, "Benchmarking Methodology for Network Interconnect Devices", RFC 2544, DOI 10.17487/RFC2544, March 1999, <https://www.rfc-editor.org/info/rfc2544>.
[RFC2544]Bradner，S.和J.McQuaid，“网络互连设备的基准测试方法”，RFC 2544，DOI 10.17487/RFC2544，1999年3月<https://www.rfc-editor.org/info/rfc2544>.
[RFC2889] Mandeville, R. and J. Perser, "Benchmarking Methodology for LAN Switching Devices", RFC 2889, DOI 10.17487/RFC2889, August 2000, <https://www.rfc-editor.org/info/rfc2889>.
[RFC2889]Mandeville，R.和J.Perser，“局域网交换设备的基准测试方法”，RFC 2889，DOI 10.17487/RFC2889，2000年8月<https://www.rfc-editor.org/info/rfc2889>.
[RFC3918] Stopp, D. and B. Hickman, "Methodology for IP Multicast Benchmarking", RFC 3918, DOI 10.17487/RFC3918, October 2004, <https://www.rfc-editor.org/info/rfc3918>.
[RFC3918]Stopp，D.和B.Hickman，“IP多播基准测试方法”，RFC 3918，DOI 10.17487/RFC3918，2004年10月<https://www.rfc-editor.org/info/rfc3918>.
[RFC4737] Morton, A., Ciavattone, L., Ramachandran, G., Shalunov, S., and J. Perser, "Packet Reordering Metrics", RFC 4737, DOI 10.17487/RFC4737, November 2006, <https://www.rfc-editor.org/info/rfc4737>.
[RFC4737]Morton，A.，Ciavattone，L.，Ramachandran，G.，Shalunov，S.，和J.Perser，“数据包重新排序度量”，RFC 4737，DOI 10.17487/RFC4737，2006年11月<https://www.rfc-editor.org/info/rfc4737>.
[RFC6201] Asati, R., Pignataro, C., Calabria, F., and C. Olvera, "Device Reset Characterization", RFC 6201, DOI 10.17487/RFC6201, March 2011, <https://www.rfc-editor.org/info/rfc6201>.
[RFC6201]Asati，R.，Pignataro，C.，Calabria，F.，和C.Olvera，“设备重置特征”，RFC 6201，DOI 10.17487/RFC6201，2011年3月<https://www.rfc-editor.org/info/rfc6201>.
[RFC6985] Morton, A., "IMIX Genome: Specification of Variable Packet Sizes for Additional Testing", RFC 6985, DOI 10.17487/RFC6985, July 2013, <https://www.rfc-editor.org/info/rfc6985>.
[RFC6985]Morton，A.，“IMIX基因组：用于附加测试的可变数据包大小规范”，RFC 6985，DOI 10.17487/RFC6985，2013年7月<https://www.rfc-editor.org/info/rfc6985>.
[RFC7679] Almes, G., Kalidindi, S., Zekauskas, M., and A. Morton, Ed., "A One-Way Delay Metric for IP Performance Metrics (IPPM)", STD 81, RFC 7679, DOI 10.17487/RFC7679, January 2016, <https://www.rfc-editor.org/info/rfc7679>.
[RFC7679]Almes，G.，Kalidini，S.，Zekauskas，M.，和A.Morton，Ed.，“IP性能度量（IPPM）的单向延迟度量”，STD 81，RFC 7679，DOI 10.17487/RFC7679，2016年1月<https://www.rfc-editor.org/info/rfc7679>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8174]Leiba，B.，“RFC 2119关键词中大写与小写的歧义”，BCP 14，RFC 8174，DOI 10.17487/RFC8174，2017年5月<https://www.rfc-editor.org/info/rfc8174>.
[BENCHMARK-METHOD] Huang, L., Ed., Rong, G., Ed., Mandeville, B., and B. Hickman, "Benchmarking Methodology for Virtualization Network Performance", Work in Progress, draft-huang-bmwg-virtual-network-performance-03, July 2017.
[BENCHMARK-METHOD]Huang，L.，Ed.，Rong，G.，Ed.，Mandeville，B.，和B.Hickman，“虚拟化网络性能的基准测试方法”，正在进行的工作，草稿-Huang-bmwg-virtual-Network-Performance-032017年7月。
[DanubeRel] OPNFV, "Danube", <https://wiki.opnfv.org/display/SWREL/Danube>.
[多瑙河]OPNFV，“多瑙河”<https://wiki.opnfv.org/display/SWREL/Danube>.
[IEEE802.1ac] IEEE, "IEEE Standard for Local and metropolitan area networks -- Media Access Control (MAC) Service Definition", IEEE 802.1AC-2016, DOI 10.1109/IEEESTD.2017.7875381, 2016, <https://standards.ieee.org/findstds/ standard/802.1AC-2016.html>.
[IEEE802.1ac]IEEE，“局域网和城域网的IEEE标准——媒体访问控制（MAC）服务定义”，IEEE 802.1ac-2016，DOI 10.1109/IEEESTD.2017.7875381，2016<https://standards.ieee.org/findstds/ 标准/802.1AC-2016.html>。
[IEEE829] IEEE, "IEEE Standard for Software and System Test Documentation", IEEE 829-2008, DOI 10.1109/IEEESTD.2008.4578383, <http://ieeexplore.ieee.org/document/4578383/>.
[IEEE829]IEEE，“IEEE软件和系统测试文档标准”，IEEE 829-2008，DOI 10.1109/IEEESTD.2008.4578383<http://ieeexplore.ieee.org/document/4578383/>.
[IFA003] ETSI, "Network Functions Virtualisation (NFV); Acceleration Technologies; vSwitch Benchmarking and Acceleration Specification", ETSI GS NFV-IFA 003 V2.1.1, April 2016, <http://www.etsi.org/deliver/etsi_gs/ NFV-IFA/001_099/003/02.01.01_60/ gs_NFV-IFA003v020101p.pdf>.
[IFA003]ETSI，“网络功能虚拟化（NFV）；加速技术；vSwitch基准测试和加速规范”，ETSI GS NFV-IFA 003 V2.1.11916年4月<http://www.etsi.org/deliver/etsi_gs/ NFV-IFA/001\U 099/003/02.01.01\U 60/gs\U NFV-IFA003v020101p.pdf>。
[LTD] Tahhan, M., "VSPERF Level Test Design (LTD)", <http://docs.opnfv.org/en/stable-danube/ submodules/vswitchperf/docs/testing/developer/ requirements/vswitchperf_ltd.html#>.
[LTD]Takhan，M.，“VSPERF水平测试设计（有限公司）”<http://docs.opnfv.org/en/stable-danube/ 子模块/vswitchperf/docs/testing/developer/requirements/vswitchperf_ltd.html。
[LTDoverV] Morton, A., "LTD Test Spec Overview", <https://wiki.opnfv.org/display/vsperf/ LTD+Test+Spec+Overview>.
[LTDoverV]莫顿，A.，“有限公司测试规范概述”<https://wiki.opnfv.org/display/vsperf/ 有限公司+测试+规范+概述>。
[OPNFV] OPNFV, "OPNFV", <https://www.opnfv.org/>.
[OPNFV]OPNFV，“OPNFV”<https://www.opnfv.org/>.
[RFC1242] Bradner, S., "Benchmarking Terminology for Network Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242, July 1991, <https://www.rfc-editor.org/info/rfc1242>.
[RFC1242]Bradner，S.，“网络互连设备的基准术语”，RFC 1242，DOI 10.17487/RFC1242，1991年7月<https://www.rfc-editor.org/info/rfc1242>.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation Applicability Statement", RFC 5481, DOI 10.17487/RFC5481, March 2009, <https://www.rfc-editor.org/info/rfc5481>.
[RFC5481]Morton，A.和B.Claise，“数据包延迟变化适用性声明”，RFC 5481，DOI 10.17487/RFC5481，2009年3月<https://www.rfc-editor.org/info/rfc5481>.
[RFC8172] Morton, A., "Considerations for Benchmarking Virtual Network Functions and Their Infrastructure", RFC 8172, DOI 10.17487/RFC8172, July 2017, <https://www.rfc-editor.org/info/rfc8172>.
[RFC8172]Morton，A.“对虚拟网络功能及其基础设施进行基准测试的注意事项”，RFC 8172，DOI 10.17487/RFC8172，2017年7月<https://www.rfc-editor.org/info/rfc8172>.
[TestTopo] Snyder, E., "Test Methodology", <https://wiki.opnfv.org/display/vsperf/Test+Methodology>.
[TestTopo]Snyder，E.，“测试方法学”<https://wiki.opnfv.org/display/vsperf/Test+方法学>。
[VSPERFhome] Tahhan, M., "VSPERF Home", <https://wiki.opnfv.org/display/vsperf/VSperf+Home>.
[VSPERFhome]塔汉，M.，“VSPERF Home”<https://wiki.opnfv.org/display/vsperf/VSperf+主页>。
Acknowledgements
致谢
The authors appreciate and acknowledge comments from Scott Bradner, Marius Georgescu, Ramki Krishnan, Doug Montgomery, Martin Klozik, Christian Trautman, Benoit Claise, and others for their reviews.
作者赞赏并感谢斯科特·布拉德纳、马吕斯·乔治斯库、拉姆基·克里希南、道格·蒙哥马利、马丁·科洛齐克、克里斯蒂安·特劳特曼、贝诺伊特·克莱斯和其他人的评论。
We also acknowledge the early work in [BENCHMARK-METHOD] and useful discussion with the authors.
我们还感谢[BENCHMARK-METHOD]的早期工作以及与作者的有益讨论。
Authors' Addresses
作者地址
Maryam Tahhan Intel
玛丽亚姆·塔汉·因特尔
Email: maryam.tahhan@intel.com
Email: maryam.tahhan@intel.com
Billy O'Mahony Intel
比利·奥马奥尼·因特尔
Email: billy.o.mahony@intel.com
Email: billy.o.mahony@intel.com
Al Morton AT&T Labs 200 Laurel Avenue South Middletown, NJ 07748 United States of America
美国新泽西州劳雷尔大道南米德尔顿200号阿尔莫顿AT&T实验室，邮编：07748
Phone: +1 732 420 1571
Fax: +1 732 368 1192
Email: acmorton@att.com
Phone: +1 732 420 1571
Fax: +1 732 368 1192
Email: acmorton@att.com