[dpdk-dev] Performance - linking against DPDK shared vs static libraries

Kavanagh, Mark B mark.b.kavanagh at intel.com
Wed Jul 23 23:43:49 CEST 2014



-----Original Message-----
From: Antti Kantee [mailto:pooka at fixup.fi] 
Sent: Wednesday, July 23, 2014 5:37 PM
To: Kavanagh, Mark B; dev at dpdk.org
Subject: Re: [dpdk-dev] Performance - linking against DPDK shared vs static libraries

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

It's actually the former, and I agree with your assertion regarding the constraint! 
I take it from your response then that the performance drop when using shared libraries is expected behavior?
--------------------------------------------------------------
Intel Shannon Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
Business address: Dromore House, East Park, Shannon, Co. Clare

This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.




More information about the dev mailing list