From: Dmitry Vyal <dmitryvyal-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Robert Sanford <rsanford-mDvk1qcdE6VWk0Htik3J/w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: How to fight forwarding performance regression on large mempool sizes.
Date: Fri, 20 Sep 2013 10:48:03 +0400 [thread overview]
Message-ID: <523BEFA3.4070209@gmail.com> (raw)
In-Reply-To: <CAFmpvUNzbi7zsAOHeaR5KpX_OBpa_g-TLDr5FYmddqGGAX9pSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 09/19/2013 11:39 PM, Robert Sanford wrote:
> Hi Dmitry,
>
> The biggest drop-off seems to be from size 128K to 256K. Are you using
> 1GB huge pages already (rather than 2MB)?
>
> I would think that it would not use over 1GB until you ask for 512K
> mbufs or more.
>
Hi Robert,
Yes, I've been using 1GB pages for a while. My L3 cache is 20MB and
mbufs are 2240 bytes of size. So something strange indeed happens then
we move from ~200MB to ~400MB. Any ideas?
Regards,
Dmitry
next prev parent reply other threads:[~2013-09-20 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 7:50 How to fight forwarding performance regression on large mempool sizes Dmitry Vyal
[not found] ` <523AACC9.8010304-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-19 19:39 ` Robert Sanford
[not found] ` <CAFmpvUNzbi7zsAOHeaR5KpX_OBpa_g-TLDr5FYmddqGGAX9pSA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-19 19:43 ` Venkatesan, Venky
[not found] ` <1FD9B82B8BF2CF418D9A1000154491D973F4AEAE-P5GAC/sN6hlcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-09-20 6:50 ` Dmitry Vyal
2013-09-20 6:48 ` Dmitry Vyal [this message]
[not found] ` <523BEFA3.4070209-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-20 14:41 ` Robert Sanford
2013-09-20 15:34 ` Robert Sanford
[not found] ` <CAFmpvUNEtcM8TtHJhqShRggDKRT3Y0vAY9aiG=28aV9NomQRgA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-09-22 19:03 ` Dmitry Vyal
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=523BEFA3.4070209@gmail.com \
--to=dmitryvyal-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=rsanford-mDvk1qcdE6VWk0Htik3J/w@public.gmane.org \
/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).