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 E4D1BA00C3; Mon, 17 Jan 2022 16:47:50 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4C12B41238; Mon, 17 Jan 2022 16:47:50 +0100 (CET) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id 563554122E for ; Mon, 17 Jan 2022 16:47:49 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1642434469; x=1673970469; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=0KpwdvekPf/0NyczCeQyNqZTTm+qMV2liGSe7GcJOLE=; b=hAK5lGmfNjfy5IaIXn0M9ODH05hfje0iwFBOr7Qy6R542+TqVjfdBVY2 oVMGkwXEtx468XH9iNc0y4PL4YWyfdA8BdqawVRuTSGUKzQc58Xbtm0yK 2HeifSCjKojQyThvN/4jES/WWZA7jEHdyeirFn3lgs8kn4BuTonAMMllO pKFdh5IbkHvNITa2cbXc3+flHa+D+jrjzYlaaOHzAr+GWVBGcSwy9xHeD opIFI25mtO1DQYEFQeqm9xKiiyhxUZsHNdc0OpaJJfOgAm/O26lkbz+d3 DsLjg0W5aYmbUdBFS1lbYqiI2a+JR+ki46NFOXj2dpyvLkLqQ/AOOw/Ol w==; X-IronPort-AV: E=McAfee;i="6200,9189,10229"; a="244605763" X-IronPort-AV: E=Sophos;i="5.88,295,1635231600"; d="scan'208";a="244605763" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jan 2022 07:47:48 -0800 X-IronPort-AV: E=Sophos;i="5.88,295,1635231600"; d="scan'208";a="476690710" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.26.87]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 17 Jan 2022 07:47:45 -0800 Date: Mon, 17 Jan 2022 15:47:41 +0000 From: Bruce Richardson To: Dmitry Kozlyuk Cc: dev@dpdk.org, Aaron Conole , Viacheslav Ovsiienko Subject: Re: [PATCH v1 2/6] app/test: add allocator performance benchmark Message-ID: References: <20211230143744.3550098-1-dkozlyuk@nvidia.com> <20220117080801.481568-1-dkozlyuk@nvidia.com> <20220117080801.481568-3-dkozlyuk@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220117080801.481568-3-dkozlyuk@nvidia.com> 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 On Mon, Jan 17, 2022 at 10:07:57AM +0200, Dmitry Kozlyuk wrote: > Memory allocator performance is crucial to applications that deal > with large amount of memory or allocate frequently. DPDK allocator > performance is affected by EAL options, API used and, at least, > allocation size. New autotest is intended to be run with different > EAL options. It measures performance with a range of sizes > for dirrerent APIs: rte_malloc, rte_zmalloc, and rte_memzone_reserve. > > Work distribution between allocation and deallocation depends on EAL > options. The test prints both times and total time to ease comparison. > > Memory can be filled with zeroes at different points of allocation path, > but it always takes considerable fraction of overall timing. This is why > the test measures filling speed and prints how long clearing takes > for each size as a reference (for rte_memzone_reserve estimations > are printed). > > Signed-off-by: Dmitry Kozlyuk > Reviewed-by: Viacheslav Ovsiienko > --- What is the expected running time of this test? When I tried it out on my machine it appears to hang after the following output: USER1: 4096 10000 3.44 1.11 4.56 0.67 USER1: 65536 10000 21.85 14.75 36.60 9.38 USER1: 1048576 10000 481.40 329.96 811.36 147.62