From: "Catalin(ux) M. BOIE" <catab@embedromix.ro>
To: "David Miller" <davem@davemloft.net>
Cc: jmack@wm7d.net, netdev@vger.kernel.org, lvs-devel@vger.kernel.org
Subject: Re: [PATCH] IPVS: Allow boot time change of hash size.
Date: Tue, 2 Dec 2008 16:16:04 -0700 (MST) [thread overview]
Message-ID: <49597.86.34.32.157.1228259764.squirrel@mail.embedromix.ro> (raw)
In-Reply-To: <20081202.145129.06176881.davem@davemloft.net>
> From: "Catalin(ux) M. BOIE" <catab@embedromix.ro>
> Date: Tue, 2 Dec 2008 08:34:22 -0700 (MST)
>
>> Hello, Joe!
>>
>> > On Fri, 28 Nov 2008, Catalin(ux) M. BOIE wrote:
>> >
>> >> Hello, Joe!
>> >>
>> >> No, I did not measure it, but, I read the help text:
>> > .
>> > .
>> >> The help is wrong or I am missing something?
>> >
>> > there's a bit somewhere else in the same section saying not
>> > to change the hash size unless you know more than we do :-)
>>
>> Where, exactly?
>>
>> So, should I not change it at all even if I have a great number of
>> simultaneously connections?
Hello, David!
> You should only ever change something like this if you actually
> observe a specific performance problem.
I have a need, I didn't wake up some day and I dreamed to change this.
I have a gateway with LVS and I have 4 web servers behind.
I saw the help text at that option and I saw that I could raise the limit.
> This is the part that is driving everybody crazy about your
> report. You seem to be changing this without having observed
> a measurable performance problem first, and then tracked it down
> specifically to this hash table's size.
I was looking for anything that could get me past of 88.000 request per
seconds.
The help text told me to raise that value if I have big number of
connections. I just needed an easy way to test.
> You seem to want to change it because it seems to you like that is
> what should be done. You don't really know if it even matters or not
> for your workload.
Without easy testing (boot time change not compile time change) is hard to
tell if it helps me or not.
Anyway, if the help text is wrong, let's correct it.
If it is correct, let's allow changing that value at runtime, so people
can easy juggle with it.
Do you agree, David?
Thank you.
--
Catalin(ux) M. BOIE
http://kernel.embedromix.ro/
next prev parent reply other threads:[~2008-12-02 23:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 13:36 [PATCH] IPVS: Allow boot time change of hash size Catalin(ux) M. BOIE
2008-11-26 14:40 ` Joseph Mack NA3T
2008-11-26 23:27 ` David Miller
2008-11-27 7:05 ` Catalin(ux) M. BOIE
2008-11-27 7:37 ` David Miller
2008-11-27 6:58 ` Catalin(ux) M. BOIE
2008-11-27 15:58 ` Joseph Mack NA3T
2008-11-28 8:49 ` Catalin(ux) M. BOIE
2008-11-28 14:55 ` Joseph Mack NA3T
2008-12-02 15:34 ` Catalin(ux) M. BOIE
2008-12-02 22:51 ` David Miller
2008-12-02 23:16 ` Catalin(ux) M. BOIE [this message]
2008-12-03 0:37 ` David Miller
2009-12-28 18:49 ` Mark Bergsma
2009-12-29 1:34 ` Simon Horman
2010-01-04 13:57 ` Patrick McHardy
2010-01-04 23:24 ` Simon Horman
2010-01-05 11:02 ` Mark Bergsma
2010-01-06 15:25 ` Catalin(ux) M. BOIE
2010-01-05 0:20 ` Simon Horman
2010-01-05 4:56 ` Patrick McHardy
2008-12-03 21:11 ` Graeme Fowler
2008-12-04 7:47 ` Catalin(ux) M. BOIE
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=49597.86.34.32.157.1228259764.squirrel@mail.embedromix.ro \
--to=catab@embedromix.ro \
--cc=davem@davemloft.net \
--cc=jmack@wm7d.net \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.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).