From mboxrd@z Thu Jan 1 00:00:00 1970 From: Antti Kantee Subject: Re: Performance - linking against DPDK shared vs static libraries Date: Wed, 23 Jul 2014 16:37:26 +0000 Message-ID: <53CFE4C6.7080506@fixup.fi> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: "Kavanagh, Mark B" , "dev-VfR2kkLFssw@public.gmane.org" Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On 23/07/14 15:58, Kavanagh, Mark B wrote: > Hi, > > I build a switching application, which links against DPDK shared libraries; when I run the application, I see throughput of X. I then build the application again, except this time I link against DPDK shared libraries, having modified the application's build parameters appropriately. In this case, I see a performance drop of around .04%, which given the high throughput of the application is significant. > > Is such performance degradation to be expected when using DPDK shared libraries, and if not, are there any best-known methods for preventing performance degradation, assuming that I may be constrained to using shared libraries going forward? Do you mean .04% or 4%? I would be more inclined to believe the latter. Shared libraries are inherently slower due to indirection from PIC, and being required to use them seems like a silly constraint in the context of high-performance computing. - antti