From: Antti Kantee <pooka@fixup.fi>
To: "Kavanagh, Mark B" <mark.b.kavanagh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Performance - linking against DPDK shared vs static libraries
Date: Wed, 23 Jul 2014 16:37:26 +0000 [thread overview]
Message-ID: <53CFE4C6.7080506@fixup.fi> (raw)
In-Reply-To: <DC5AD7FA266D86499789B1BCAEC715F846BA3C50@IRSMSX105.ger.corp.intel.com>
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
next prev parent reply other threads:[~2014-07-23 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 15:58 Kavanagh, Mark B
2014-07-23 16:37 ` Antti Kantee [this message]
2014-07-23 21:43 ` Kavanagh, Mark B
2014-07-23 21:56 ` Matthew Hall
2014-07-24 14:02 ` Kavanagh, Mark B
2014-07-23 18:08 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53CFE4C6.7080506@fixup.fi \
--to=pooka@fixup.fi \
--cc=dev@dpdk.org \
--cc=mark.b.kavanagh@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).