Re: [bmwg] I-D Action: draft-ietf-bmwg-ca-bench-meth-01.txt

Ilya Varlashkin <ilya@nobulus.com> Mon, 12 March 2012 23:15 UTC

Return-Path: <ilya@nobulus.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70A6521F8A6D for <bmwg@ietfa.amsl.com>; Mon, 12 Mar 2012 16:15:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d9ZSAxabTyJ7 for <bmwg@ietfa.amsl.com>; Mon, 12 Mar 2012 16:15:46 -0700 (PDT)
Received: from nobulus.com (nobulus.com [IPv6:2001:6f8:892:6ff::11:152]) by ietfa.amsl.com (Postfix) with ESMTP id B5E0721F8ABD for <bmwg@ietf.org>; Mon, 12 Mar 2012 16:15:44 -0700 (PDT)
Received: from nobulus.com (localhost [127.0.0.1]) by nobulus.com (Postfix) with ESMTP id 00D7E1749F; Tue, 13 Mar 2012 00:15:43 +0100 (CET)
X-Virus-Scanned: amavisd-new at nobulus.com
Received: from nobulus.com ([127.0.0.1]) by nobulus.com (nobulus.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8Gc5EiS1Yt4g; Tue, 13 Mar 2012 00:15:41 +0100 (CET)
Received: from [IPv6:2001:6f8:893:ffff:225:4bff:fea6:3684] (unknown [IPv6:2001:6f8:893:ffff:225:4bff:fea6:3684]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by nobulus.com (Postfix) with ESMTPSA id E0CD2172BE; Tue, 13 Mar 2012 00:15:40 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Ilya Varlashkin <ilya@nobulus.com>
In-Reply-To: <CB83BC6B.ADAF%mhamilton@breakingpoint.com>
Date: Tue, 13 Mar 2012 00:15:35 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <73D3A52E-2CE5-4991-A84B-408F0334444B@nobulus.com>
References: <CB83BC6B.ADAF%mhamilton@breakingpoint.com>
To: Mike Hamilton <mhamilton@breakingpoint.com>
X-Mailer: Apple Mail (2.1084)
Cc: "bmwg@ietf.org" <bmwg@ietf.org>
Subject: Re: [bmwg] I-D Action: draft-ietf-bmwg-ca-bench-meth-01.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bmwg>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2012 23:15:46 -0000

On Mar 12, 2012, at 20:56 , Mike Hamilton wrote:

>> 9. With regard to Section 3.7.1, the range of IP addresses noted in RFC
>> 2544 covers
>> only 128K addresses. 128K addresses is unlikely to stress the forwarding
>> tables
>> of many devices available today. Further, they are all unicast addresses.
>> What if
>> we wish to test using multicast flows (e.g., RTP video)? It seems
>> unnecessary to
>> restrict users of this draft to the RFC 2544 IP address range.
> With the suggestion from Al, RFC 1918 private address space may also
> be used.  This has been added to the draft.
> 

I suspect that if DUT is not older than 15 years, then it's quite likely that its forwarding plane stress depends not on number of IP addresses but on the depth of lookup (length of the key prefix) and number of such lookups. As long as search key is flushed from CPU cache, then a million lookups with only dozen addresses is probably as good as million lookups of unique addresses.

/iLya