IETF Logo Mail Archive

Re: [core] CoAP for high throughput applications

"Fossati, Thomas (Nokia - GB)" <thomas.fossati@nokia.com> Tue, 05 April 2016 20:27 UTC

Return-Path: <thomas.fossati@nokia.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB9A12D63A for <core@ietfa.amsl.com>; Tue, 5 Apr 2016 13:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9ym7sKd4MOt for <core@ietfa.amsl.com>; Tue, 5 Apr 2016 13:27:01 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF96D12D159 for <core@ietf.org>; Tue, 5 Apr 2016 13:27:01 -0700 (PDT)
Received: from fr712umx3.dmz.alcatel-lucent.com (unknown [135.245.210.42]) by Websense Email Security Gateway with ESMTPS id B2F32D0ED12FA; Tue, 5 Apr 2016 20:26:56 +0000 (GMT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (fr711usmtp1.zeu.alcatel-lucent.com [135.239.2.122]) by fr712umx3.dmz.alcatel-lucent.com (GMO-o) with ESMTP id u35KQxNV004113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 5 Apr 2016 20:27:00 GMT
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id u35KQxcx014537 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Apr 2016 22:26:59 +0200
Received: from FR711WXCHMBA08.zeu.alcatel-lucent.com ([169.254.4.8]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Tue, 5 Apr 2016 22:26:59 +0200
From: "Fossati, Thomas (Nokia - GB)" <thomas.fossati@nokia.com>
To: EXT Kovatsch Matthias <kovatsch@inf.ethz.ch>, EXT Carsten Bormann <cabo@tzi.org>
Thread-Topic: [core] CoAP for high throughput applications
Thread-Index: AQHRjr76eON/nMwwHUq4G5ODCqR3Gp96QgsA///UMQCAAX3f4P//7ZCA
Date: Tue, 05 Apr 2016 20:26:58 +0000
Message-ID: <D3299DFC.62D69%thomas.fossati@alcatel-lucent.com>
References: <D32866D3.62C58%thomas.fossati@alcatel-lucent.com> <5702E93E.3030005@tzi.org> <D328743C.62C97%thomas.fossati@alcatel-lucent.com> <55877B3AFB359744BA0F2140E36F52B54F186325@MBX110.d.ethz.ch>
In-Reply-To: <55877B3AFB359744BA0F2140E36F52B54F186325@MBX110.d.ethz.ch>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.2.160219
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1035EAB487E9594B92E7999AAD3B5249@exchange.lucent.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/qD9PgQbDJ4E5c0cjJzPzFs6_g6o>
Cc: "core@ietf.org" <core@ietf.org>
Subject: Re: [core] CoAP for high throughput applications
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 20:27:04 -0000

On 05/04/2016 13:38, "EXT Kovatsch  Matthias" <kovatsch@inf.ethz.ch> wrote:
>>I haven't re-done the maths, but the CoAP spec has a slightly lower
>>number:
>> 
>>   "[...] The Message ID
>>    is compact; its 16-bit size enables up to about 250 messages per
>>    second from one endpoint to another with default protocol
>>    parameters.)"
>
>This only limits the number of messages between two endpoints. A server
>can receive this rate from an arbitrary number of clients. I think this
>was the scenario for this LURK box, no?

My target is for a *single* edge server to send around 20K transactions
per second to the LURK box.

>In case you really need to send a higher rate of requests from a client,
>it could use multiple ports.

So, assuming we can't do anything at the CoAP layer, the number of
ephemeral ports that are available on the client is the limiting factor
here.  IIRC, on Linux that number is roughly 30K, which means that a
dedicated box could do >7M transactions per second?  That's quite a lot.

v2.23.0 | Report a Bug | By Email