draft-ietf-bmwg-vswitch-opnfv-00.txt   draft-ietf-bmwg-vswitch-opnfv-01.txt 
Network Working Group M. Tahhan Network Working Group M. Tahhan
Internet-Draft B. O'Mahony Internet-Draft B. O'Mahony
Intended status: Informational Intel Intended status: Informational Intel
Expires: January 9, 2017 A. Morton Expires: April 17, 2017 A. Morton
AT&T Labs AT&T Labs
July 8, 2016 October 14, 2016
Benchmarking Virtual Switches in OPNFV Benchmarking Virtual Switches in OPNFV
draft-ietf-bmwg-vswitch-opnfv-00 draft-ietf-bmwg-vswitch-opnfv-01
Abstract Abstract
This memo describes the progress of the Open Platform for NFV (OPNFV) This memo describes the progress of the Open Platform for NFV (OPNFV)
project on virtual switch performance "VSWITCHPERF". This project project on virtual switch performance "VSWITCHPERF". This project
intends to build on the current and completed work of the intends to build on the current and completed work of the
Benchmarking Methodology Working Group in IETF, by referencing Benchmarking Methodology Working Group in IETF, by referencing
existing literature. The Benchmarking Methodology Working Group has existing literature. The Benchmarking Methodology Working Group has
traditionally conducted laboratory characterization of dedicated traditionally conducted laboratory characterization of dedicated
physical implementations of internetworking functions. Therefore, physical implementations of internetworking functions. Therefore,
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 9, 2017. This Internet-Draft will expire on April 17, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 4, line 9 skipping to change at page 4, line 9
literature and experience, and describe the extensions needed for literature and experience, and describe the extensions needed for
benchmarking virtual switches. Inital feedback indicates that many benchmarking virtual switches. Inital feedback indicates that many
of these extensions may be applicable beyond the current scope (to of these extensions may be applicable beyond the current scope (to
hardware switches in the NFV Infrastructure and to virtual routers, hardware switches in the NFV Infrastructure and to virtual routers,
for example). Additionally, this memo serves as a vehicle to include for example). Additionally, this memo serves as a vehicle to include
more detail and commentary from BMWG and other Open Source more detail and commentary from BMWG and other Open Source
communities, under BMWG's chartered work to characterize the NFV communities, under BMWG's chartered work to characterize the NFV
Infrastructure (a virtual switch is an important aspect of that Infrastructure (a virtual switch is an important aspect of that
infrastructure). infrastructure).
The benchmarking covered in this memo should be applicable to many
types of vswitches, and remain vswitch-agnostic to great degree.
There has been no attempt to track and test all features of any
specific vswitch implementation.
3. Benchmarking Considerations 3. Benchmarking Considerations
This section highlights some specific considerations (from This section highlights some specific considerations (from
[I-D.ietf-bmwg-virtual-net])related to Benchmarks for virtual [I-D.ietf-bmwg-virtual-net])related to Benchmarks for virtual
switches. The OPNFV project is sharing its present view on these switches. The OPNFV project is sharing its present view on these
areas, as they develop their specifications in the Level Test Design areas, as they develop their specifications in the Level Test Design
(LTD) document. (LTD) document.
3.1. Comparison with Physical Network Functions 3.1. Comparison with Physical Network Functions
skipping to change at page 10, line 32 skipping to change at page 10, line 32
the effect of this coupling on the performance of the DUT the effect of this coupling on the performance of the DUT
(example: delay of the initial packet of a flow). (example: delay of the initial packet of a flow).
o CPU and Memory Consumption Tests to understand the virtual o CPU and Memory Consumption Tests to understand the virtual
switch's footprint on the system, usually conducted as auxiliary switch's footprint on the system, usually conducted as auxiliary
measurements with benchmarks above. They include: CPU measurements with benchmarks above. They include: CPU
utilization, Cache utilization and Memory footprint. utilization, Cache utilization and Memory footprint.
o The so-called "Soak" tests, where the selected test is conducted 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, over a long period of time (with an ideal duration of 24 hours,
and at least 6 hours). The purpose of soak tests is to capture but only long enough to determine that stability issues exist when
transient changes in performance which may occur due to infrequent found; there is no requirement to continue a test when a DUT
processes or the low probability coincidence of two or more exhibits instability over time). The key performance
processes. The performance must be evaluated periodically during characteristics and benchmarks for a DUT are determined (using
continuous testing, and this results in use of [RFC2889] Frame short duration tests) prior to conducting soak tests. The purpose
Rate metrics instead of [RFC2544] Throughput (which requires of soak tests is to capture transient changes in performance which
stopping traffic to allow time for all traffic to exit internal may occur due to infrequent processes, memory leaks, or the low
queues). probability coincidence of two or more processes. The stability
of the DUT is the paramount consideration, so performance must be
evaluated periodically during continuous testing, and this results
in use of [RFC2889] Frame Rate metrics instead of [RFC2544]
Throughput (which requires stopping traffic to allow time for all
traffic to exit internal queues), for example.
Future/planned test specs include: Future/planned test specs include:
o Request/Response Performance Tests (TCP, UDP) which measure the o Request/Response Performance Tests (TCP, UDP) which measure the
transaction rate through the switch. transaction rate through the switch.
o Noisy Neighbour Tests, to understand the effects of resource o Noisy Neighbour Tests, to understand the effects of resource
sharing on the performance of a virtual switch. sharing on the performance of a virtual switch.
o Tests derived from examination of ETSI NFV Draft GS IFA003 o Tests derived from examination of ETSI NFV Draft GS IFA003
skipping to change at page 21, line 19 skipping to change at page 21, line 19
[I-D.huang-bmwg-virtual-network-performance] [I-D.huang-bmwg-virtual-network-performance]
Huang, L., Rong, G., Mandeville, B., and B. Hickman, Huang, L., Rong, G., Mandeville, B., and B. Hickman,
"Benchmarking Methodology for Virtualization Network "Benchmarking Methodology for Virtualization Network
Performance", draft-huang-bmwg-virtual-network- Performance", draft-huang-bmwg-virtual-network-
performance-01 (work in progress), April 2015. performance-01 (work in progress), April 2015.
[I-D.ietf-bmwg-virtual-net] [I-D.ietf-bmwg-virtual-net]
Morton, A., "Considerations for Benchmarking Virtual Morton, A., "Considerations for Benchmarking Virtual
Network Functions and Their Infrastructure", draft-ietf- Network Functions and Their Infrastructure", draft-ietf-
bmwg-virtual-net-03 (work in progress), June 2016. bmwg-virtual-net-04 (work in progress), August 2016.
[IFA003] "https://docbox.etsi.org/ISG/NFV/Open/Drafts/ [IFA003] "https://docbox.etsi.org/ISG/NFV/Open/Drafts/
IFA003_Acceleration_-_vSwitch_Spec/". IFA003_Acceleration_-_vSwitch_Spec/".
[LTD] "LTD Test Specification [LTD] "LTD Test Specification
http://artifacts.opnfv.org/vswitchperf/docs/requirements/ http://artifacts.opnfv.org/vswitchperf/brahmaputra/docs/
index.html". requirements/index.html".
[LTDoverV] [LTDoverV]
"LTD Test Spec Overview https://wiki.opnfv.org/wiki/ "LTD Test Spec Overview https://wiki.opnfv.org/wiki/
vswitchperf_test_spec_review". vswitchperf_test_spec_review".
[RFC1242] Bradner, S., "Benchmarking Terminology for Network [RFC1242] Bradner, S., "Benchmarking Terminology for Network
Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242, Interconnection Devices", RFC 1242, DOI 10.17487/RFC1242,
July 1991, <http://www.rfc-editor.org/info/rfc1242>. July 1991, <http://www.rfc-editor.org/info/rfc1242>.
[RFC5481] Morton, A. and B. Claise, "Packet Delay Variation [RFC5481] Morton, A. and B. Claise, "Packet Delay Variation
 End of changes. 8 change blocks. 
15 lines changed or deleted 25 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/