From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 666112030 for ; Wed, 13 Dec 2017 12:11:12 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EC9F020B44; Wed, 13 Dec 2017 06:11:11 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 13 Dec 2017 06:11:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=rsSyhLCiS5GeXwxByRPwr7IcxQ mAClwfG9YEQbSVSGw=; b=PDN63QMGxi3Vxe5kGuN/VZKcMvpukmJB/S7uB/23g9 +N801OIEJ1rMHHqapm8J3QpfJx4jXRZd3hJjatuU7QKrONpvlxpzbOpW1OVYRXV+ z6XqXN1typ/RxOQCyr3l7TW2bODCePCA2RpOsWsTPo2vXBVxOyO7ufCpqFc3+YZd Q= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=rsSyhL CiS5GeXwxByRPwr7IcxQmAClwfG9YEQbSVSGw=; b=KghW88lZcGCq3uqs8JwgvG ndMe2KMiYFX+/GjmzztidFxQE7qHbGw5ho7mOxpwjWJYfZYaHBD43GoMM0TtIyN9 CNNN+s6uF83c/E1LZ9KIZPmK4cVqquXlbAh3IK6ZFr01igsB0tvr2qKefNcXdEHm Zmkp2Velijv+OP8qVf7ZvC/LcFexYDHE+AHzYB36OIFJOJjCyI1SDE3kebnfcQ/1 Heyqdmi1jiDTKq89zelCt7HMBGyFJXB9TSFdsb7j+/lQf6AzMlPLAsdHcwFE4TKf 0vuxX8vaLZLCcAfLulyaKD4f+K7kDhbYHM4AvSZKy2dzwgqARWuYb9e1XYwNZV+g == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id A104324600; Wed, 13 Dec 2017 06:11:11 -0500 (EST) From: Thomas Monjalon To: Anand Prasad Cc: users@dpdk.org Date: Wed, 13 Dec 2017 12:11:10 +0100 Message-ID: <4438207.qMLY8BktU0@xps> In-Reply-To: <401616826.3643255.1513152888444@mail.yahoo.com> References: <401616826.3643255.1513152888444.ref@mail.yahoo.com> <401616826.3643255.1513152888444@mail.yahoo.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-users] DPDK Performance tips X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Dec 2017 11:11:12 -0000 13/12/2017 09:14, Anand Prasad: > Hi Dpdk team, > Can anyone please share tips to get better DPDK performance? I have tried to run DPDK test applications on various PC configurations with different CPU Speeds, RAM Size/Speed and and PCIex16 2nd and 3rd generation connections... but I don't get very consistent results. > The same test application does not behave similarly on 2 PC's with same hardware configuration.But general observation is that, performance is better on Intel motherboard with 3rd generation PCIe slot. When tried on Gigabyte motherboard (even with higher CPU and RAM speeds), performance was very poor. > The performance issue I am facing is the Packet Drop issue on the Rx side. > Two PC's with exactly same hardware configuration, one PC drops packets after few hours, but in the other PC I don't observe packet drop > Highly appreciate a quick response > Regards,Anand Prasad This is very complicate because it really depends on the hardware. Managing performance requires a very good knowledge of the hardware. You can find some basic advices in this guide for some Intel hardware: http://dpdk.org/doc/guides/linux_gsg/nic_perf_intel_platform.html You will also find some informations in the drivers guide. Example: http://dpdk.org/doc/guides/nics/mlx5.html#performance-tuning