From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8A756A0547; Wed, 12 Oct 2022 10:03:39 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7A99E42E6C; Wed, 12 Oct 2022 10:03:39 +0200 (CEST) Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by mails.dpdk.org (Postfix) with ESMTP id 3D33242D86 for ; Wed, 12 Oct 2022 10:03:37 +0200 (CEST) Received: from dggpeml500024.china.huawei.com (unknown [172.30.72.57]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4MnQ5c1VpKzlXZj; Wed, 12 Oct 2022 15:59:00 +0800 (CST) Received: from [10.67.100.224] (10.67.100.224) by dggpeml500024.china.huawei.com (7.185.36.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.31; Wed, 12 Oct 2022 16:03:34 +0800 Subject: Re: [PATCH v8 9/9] app/test: add memarea to malloc-perf-autotest To: Dmitry Kozlyuk CC: , , , , , , References: <20220721044648.6817-1-fengchengwen@huawei.com> <20221011121720.2657-1-fengchengwen@huawei.com> <20221011121720.2657-10-fengchengwen@huawei.com> <20221011185840.01ef6f78@sovereign> From: fengchengwen Message-ID: <4364579e-9256-0b93-003f-2d903bfc8d68@huawei.com> Date: Wed, 12 Oct 2022 16:03:34 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 MIME-Version: 1.0 In-Reply-To: <20221011185840.01ef6f78@sovereign> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.67.100.224] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To dggpeml500024.china.huawei.com (7.185.36.10) X-CFilter-Loop: Reflected X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi Dmitry, On 2022/10/11 23:58, Dmitry Kozlyuk wrote: > 2022-10-11 12:17 (UTC+0000), Chengwen Feng: >> This patch adds memarea to malloc_perf_autotest. >> >> Test platform: Kunpeng920 >> Test command: dpdk-test -a 0000:7d:00.3 -l 10-12 >> Test result: >> USER1: Performance: rte_memarea >> USER1: Size (B) Runs Alloc (us) Free (us) Total (us) memset (us) >> USER1: 64 10000 0.03 0.03 0.06 0.01 >> USER1: 128 10000 0.02 0.03 0.05 0.01 >> USER1: 1024 10000 0.03 0.05 0.07 0.20 >> USER1: 4096 10000 0.03 0.05 0.07 0.34 >> USER1: 65536 10000 0.10 0.08 0.18 2.14 >> USER1: 1048576 644 0.10 0.04 0.14 29.07 >> USER1: 2097152 322 0.10 0.04 0.14 57.50 >> USER1: 4194304 161 0.12 0.04 0.15 114.50 >> USER1: 16777216 40 0.11 0.04 0.15 456.09 >> USER1: 1073741824 Interrupted: out of memory. [1] >> >> Compared with rte_malloc: >> USER1: Performance: rte_malloc >> USER1: Size (B) Runs Alloc (us) Free (us) Total (us) memset (us) >> USER1: 64 10000 0.14 0.07 0.21 0.01 >> USER1: 128 10000 0.10 0.05 0.15 0.01 >> USER1: 1024 10000 0.11 0.18 0.29 0.21 >> USER1: 4096 10000 0.13 0.39 0.53 0.35 >> USER1: 65536 10000 0.17 2.27 2.44 2.15 >> USER1: 1048576 10000 37.21 71.63 108.84 29.08 >> USER1: 2097152 10000 8831.15 160.02 8991.17 63.52 >> USER1: 4194304 10000 47131.88 413.75 47545.62 173.79 >> USER1: 16777216 4221 119604.60 2209.73 121814.34 964.42 >> USER1: 1073741824 31 335058.32 223369.31 558427.63 62440.87 >> >> [1] The total-size of the memarea is restricted to avoid creation >> failed. > > This is not a fair comparison: > rte_malloc time includes obtaining memory from the system. Yes, but I want to keep this patch, at least we know the different. > I think that memarea should have a dedicated benchmark, > because eventually it will be interesting to compare memarea > with different sources and algorithms. It may take a long time to reach a benchmark that everyone agrees with. I will try after this patch set upstreamed. > It will be also possible to add DPDK allocator to the comparison > by running it for an isolated heap that doesn't grow. > (In some distant future it would be cool to make DPDK allocator pluggable!) > Some shared code between this benchmark and the new one can be factored out. > . >