Data Center Benchmarking Methodology
draft-ietf-bmwg-dcbench-methodology-04

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12
• 13
• 14
• 15
• 16
• 17
• 18

Internet Engineering Task Force                               L. Avramov
Internet-Draft, Intended status: Informational                    Google
Expires October 29,2017                                          J. Rapp
April 27, 2017                                                    VMware

                  Data Center Benchmarking Methodology
                 draft-ietf-bmwg-dcbench-methodology-04

Abstract

   The purpose of this informational document is to establish test and
   evaluation methodology and measurement techniques for physical
   network equipment in the data center. 

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF). Note that other groups may also distribute working
   documents as Internet-Drafts. The list of current Internet-Drafts is
   at http://datatracker.ietf.org/drafts/current.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time. It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://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.
 

Avramov & Rapp          Expires October 29, 2017                [Page 1]
Internet-Draft    Data Center Benchmarking Methodology    April 27, 2017

 

Avramov & Rapp          Expires October 29, 2017                [Page 2]
Internet-Draft    Data Center Benchmarking Methodology    April 27, 2017

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  5
     1.2. Methodology format and repeatability recommendation . . . .  5
   2. Line Rate Testing . . . . . . . . . . . . . . . . . . . . . . .  5
     2.1 Objective  . . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.2 Methodology  . . . . . . . . . . . . . . . . . . . . . . . .  5
     2.3 Reporting Format . . . . . . . . . . . . . . . . . . . . . .  6
   3. Buffering Testing . . . . . . . . . . . . . . . . . . . . . . .  7
     3.1 Objective  . . . . . . . . . . . . . . . . . . . . . . . . .  7
     3.2 Methodology  . . . . . . . . . . . . . . . . . . . . . . . .  7
     3.3 Reporting format . . . . . . . . . . . . . . . . . . . . . . 10
   4 Microburst Testing . . . . . . . . . . . . . . . . . . . . . . . 11
     4.1 Objective  . . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.2 Methodology  . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.3 Reporting Format . . . . . . . . . . . . . . . . . . . . . . 11
   5. Head of Line Blocking . . . . . . . . . . . . . . . . . . . . . 12
     5.1 Objective  . . . . . . . . . . . . . . . . . . . . . . . . . 12
     5.2 Methodology  . . . . . . . . . . . . . . . . . . . . . . . . 12
     5.3 Reporting Format . . . . . . . . . . . . . . . . . . . . . . 13
   6. Incast Stateful and Stateless Traffic . . . . . . . . . . . . . 14
     6.1 Objective  . . . . . . . . . . . . . . . . . . . . . . . . . 14
     6.2 Methodology  . . . . . . . . . . . . . . . . . . . . . . . . 14
     6.3 Reporting Format . . . . . . . . . . . . . . . . . . . . . . 15
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 15
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 16
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 17
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 17
     9.2.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17

1.  Introduction

   Traffic patterns in the data center are not uniform and are
   constantly changing. They are dictated by the nature and variety of
   applications utilized in the data center. It can be largely east-west
   traffic flows in one data center and north-south in another, while
   some may combine both. Traffic patterns can be bursty in nature and