Re: [IPFIX] AD Review of draft-ietf-ipfix-export-per-sctp-stream-02 -> impact on performance and capacity
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 17 June 2009 10:24 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: ipfix@core3.amsl.com
Delivered-To: ipfix@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 10B063A686C for <ipfix@core3.amsl.com>; Wed, 17 Jun 2009 03:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.444
X-Spam-Level:
X-Spam-Status: No, score=-2.444 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kPVw897rW+6n for <ipfix@core3.amsl.com>; Wed, 17 Jun 2009 03:24:48 -0700 (PDT)
Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id 543B03A6E26 for <ipfix@ietf.org>; Wed, 17 Jun 2009 03:24:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,235,1243828800"; d="scan'208";a="164537416"
Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 17 Jun 2009 06:24:09 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 17 Jun 2009 06:24:08 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 17 Jun 2009 12:24:04 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A04017D2D8F@307622ANEX5.global.avaya.com>
In-Reply-To: <4A3805EC.3010702@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [IPFIX] AD Review of draft-ietf-ipfix-export-per-sctp-stream-02 -> impact on performance and capacity
Thread-Index: AcnuxEy748CZTm4LTNiT682ZDhUxoAAb++Hg
References: <EDC652A26FB23C4EB6384A4584434A0401790AFE@307622ANEX5.global.avaya.com> <4A3805EC.3010702@cisco.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Benoit Claise <bclaise@cisco.com>
Cc: "Peter Lei (peterlei)" <peterlei@cisco.com>, Michael Tuexen <tuexen@fh-muenster.de>, IETF IPFIX Working Group <ipfix@ietf.org>
Subject: Re: [IPFIX] AD Review of draft-ietf-ipfix-export-per-sctp-stream-02 -> impact on performance and capacity
X-BeenThere: ipfix@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IPFIX WG discussion list <ipfix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipfix>
List-Post: <mailto:ipfix@ietf.org>
List-Help: <mailto:ipfix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipfix>, <mailto:ipfix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2009 10:24:49 -0000
Hi Benoit, Yes, this is the type of information that I was looking for. My reading of your answer is that the impact of adding SCTP streams in an existing session versus opening a new SCTP session is minor, with a possible plus of efficiency at setup time. Processing overhead and message overhead may potentially be a problem, and care should be exercised in deployment in order to understand the effects. Can we add corresponding text on this? Thanks and Regards, Dan > -----Original Message----- > From: Benoit Claise [mailto:bclaise@cisco.com] > Sent: Tuesday, June 16, 2009 11:52 PM > To: Romascanu, Dan (Dan) > Cc: IETF IPFIX Working Group; Randall Stewart; Peter Lei > (peterlei); Michael Tuexen > Subject: Re: [IPFIX] AD Review of > draft-ietf-ipfix-export-per-sctp-stream-02 -> impact on > performance and capacity > > Dan, > > Please find below the AD review for > > draft-ietf-ipfix-export-per-sctp-stream-02. The document is mature > > enough to go to IETF Last Call. Unless there are any > special comments > > or concerns I will send it to IETF Last Call by tomorrow. > > > > Please consider the comments below together with the other > IETF Last > > Call comments. The comments are divided into Technical and Editorial > > > > T1. There is not information concerning the impact on > performance and > > capacity of the reporting and collecting processes. Should > we expect > > any considerable impact on performance and/or capacity? If any > > implementation experience is available I would suggest that > we record > > it. > > > Collecting information from the authors of > draft-stewart-tsvwg-sctpstrrst and > draft-ietf-ipfix-export-per-sctp-stream-02, here are the conclusions: > * We were not too sure what is meant by "performance and > capacity" in this context. > * If the question is about: What's the impact of additional > SCTP streams in an existing session versus opening a new SCTP > session? The impact is > minor: > - You have of course a message exchange to add the streams. > - You end up adding 16-24 bytes per stream. > - It is more lightweight to set up additional streams > compared to setting up a new association. > The only thing that comes into my mind is throughput which > * If the question is about the throughput that could be > impaired by processing overhead and message overhead. > - With respect of processing overhead, I have no idea how the > utilization of a large number of streams influences the > performance of the SCTP socket. I could imagine that a lot of > state information must be stored. > - With respect of message overhead, we can say that the fact > that we discourage multiplexing templates and data records of > different template ids may lead to a larger message overhead. > If the data record rate is low for a specific template, the > exporting process might not be able to optimally fill the > IPFIX messages. Hence, we have more overhead due to > additional IPFIX message headers and SCTP chunk headers. > > Is this what you have in mind? > > Regards, Benoit. > >
- [IPFIX] AD Review of draft-ietf-ipfix-export-per-… Romascanu, Dan (Dan)
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Benoit Claise
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Romascanu, Dan (Dan)
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Benoit Claise
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Romascanu, Dan (Dan)
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Juergen Schoenwaelder
- Re: [IPFIX] AD Review ofdraft-ietf-ipfix-export-p… Romascanu, Dan (Dan)
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Gerhard Muenz
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Michael Tuexen
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Benoit Claise
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Romascanu, Dan (Dan)
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Benoit Claise
- Re: [IPFIX] AD Review of draft-ietf-ipfix-export-… Romascanu, Dan (Dan)