[bmwg] Review of draft-dcn-bmwg-containerized-infra-10
Gabor LENCSE <lencse@hit.bme.hu> Sat, 06 May 2023 19:05 UTC
Return-Path: <lencse@hit.bme.hu>
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 CFDE6C14F75F for <bmwg@ietfa.amsl.com>; Sat, 6 May 2023 12:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mBOvbpiJFLwT for <bmwg@ietfa.amsl.com>; Sat, 6 May 2023 12:05:25 -0700 (PDT)
Received: from frogstar.hit.bme.hu (frogstar.hit.bme.hu [IPv6:2001:738:2001:4020::2c]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52277C14EB1E for <bmwg@ietf.org>; Sat, 6 May 2023 12:05:24 -0700 (PDT)
Received: from [192.168.1.144] (host-79-121-41-70.kabelnet.hu [79.121.41.70]) (authenticated bits=0) by frogstar.hit.bme.hu (8.17.1/8.17.1) with ESMTPSA id 346J5APp061835 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for <bmwg@ietf.org>; Sat, 6 May 2023 21:05:16 +0200 (CEST) (envelope-from lencse@hit.bme.hu)
X-Authentication-Warning: frogstar.hit.bme.hu: Host host-79-121-41-70.kabelnet.hu [79.121.41.70] claimed to be [192.168.1.144]
Content-Type: multipart/alternative; boundary="------------UdXZKGRFlfV8sfhvo9RS6l7p"
Message-ID: <2d0ac37d-3a27-63c9-4a15-3999a3d62f84@hit.bme.hu>
Date: Sat, 06 May 2023 21:05:05 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.10.1
Content-Language: en-US
To: "bmwg@ietf.org" <bmwg@ietf.org>
From: Gabor LENCSE <lencse@hit.bme.hu>
X-Virus-Scanned: clamav-milter 0.103.8 at frogstar.hit.bme.hu
X-Virus-Status: Clean
Received-SPF: pass (frogstar.hit.bme.hu: authenticated connection) receiver=frogstar.hit.bme.hu; client-ip=79.121.41.70; helo=[192.168.1.144]; envelope-from=lencse@hit.bme.hu; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.11;
X-DCC--Metrics: frogstar.hit.bme.hu; whitelist
X-Scanned-By: MIMEDefang 2.86 on 152.66.248.44
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/HMya-RHd7jgNV9NAx6lImbrPQj4>
Subject: [bmwg] Review of draft-dcn-bmwg-containerized-infra-10
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.39
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 06 May 2023 19:05:26 -0000
Dear Authors and BMWG, I have read the main text of draft-dcn-bmwg-containerized-infra-10 and quickly gone through its appendix, too. My impression is that this is a useful document and gives important insight of what aspects to consider when benchmarking various parts of containerized infrastructure. Special thanks for Section 3. It gives an essential introduction for those who do bechmarking but not really engaged in various containerization solutions. I think you could add some more details and you should definitely add references. (It uses a lot of technical terms, vendor and product names, etc. without references. E.g., SRIOV, eBPF, MACVLAN/IPVLAN, Docker, CRI-O, containerd, Calicom, Flannel, just to mention a few.) I saw that references were later provided for some of them, but they should be provided at the first occurrence. I cannot judge the correctness and/or completeness of the information in Section 4 as I am not an expert of the field. At least it seems to be reasonable to me. :-) A few critical comments: Section 4.2.2 Hugepages In the containerized infrastructure, the container is isolated at the application level, and administrators can set huge pages more granular level (e.g., Kubernetes allows to use of*512M bytes huge pages* for the container as default values). I do not know Kubernets, but I use hugepages with DPDK. Intel CPUs usually support only two sizes: 2MB and 1GB. Current practice is to use 1GB hugepage size, 2MB is just for very old CPUs that do not support 1GB. In Figure 12: Test Results: +--------------------+---------------------+-------------+ | Model | NUMA Mode (pinning)| Result(Gbps)| +--------------------+---------------------+-------------+ | | N/A | 3.1 | | Maximum Line Rate |---------------------+-------------+ | | same NUMA | 9.8 | +--------------------+---------------------+-------------+ However, I did not find the applied frame size, thus regarding the various line rate in Gbps, it is not clear whether they were achieved with what frame size (e.g., 64 byte or 1518 byte). I have not found mentioning any IP version in the draft. I suspect that IPv4 was used for all tests. However, I think that since 2017, the publication date of RFC 8200, IPv6 should not be just neglected. All in all, I think this draft is useful and I will support its adoption. I am aware that saying so implies the implicit promise of another, more through review in the future. :-) Best regards, Gábor
- [bmwg] Review of draft-dcn-bmwg-containerized-inf… Gabor LENCSE
- Re: [bmwg] Review of draft-dcn-bmwg-containerized… Vratko Polak -X (vrpolak - PANTHEON TECH SRO at Cisco)
- Re: [bmwg] Review of draft-dcn-bmwg-containerized… Minh Ngoc Tran
- Re: [bmwg] Review of draft-dcn-bmwg-containerized… Minh Ngoc Tran
- Re: [bmwg] Review of draft-dcn-bmwg-containerized… Minh Ngoc Tran