From: Eliezer Croitoru <eliezer@ngtech.co.il>
To: "Humberto Jucá" <betolj@gmail.com>, netfilter@vger.kernel.org
Subject: Re: A question about routing cache (for load balancing).
Date: Thu, 07 Nov 2013 18:52:52 +0200 [thread overview]
Message-ID: <527BC564.1000008@ngtech.co.il> (raw)
In-Reply-To: <CACuyg26oOJY7puRHkH9ZZC5QM--H=EBvZuAGk34WxBTS2mNzpQ@mail.gmail.com>
On 11/07/2013 12:26 PM, Humberto Jucá wrote:
> Hi,
>
> The cache control for load balance can be done with:
By load balance I am talking about Route load balance.
>
> 1. scheduled flush (to remove old entries)
> /proc/sys/net/ipv4/route/gc_interval
OK so every 60 secs remove the old entries?
>
> 2. Lifetime of each learned route
> /proc/sys/net/ipv4/route/gc_timeout
which I should see using "ip route show cache" ?
>
> If you want a aggressive load balance
> echo 1 > /proc/sys/net/ipv4/route/gc_interval
> echo 1 > /proc/sys/net/ipv4/route/gc_timeout
Agrressive load balance? how exactly?
we are talking about route which will have series issues with that.
>
> But the ideal is not to change the gc_timeout.
> You certainly have problems with https.
I will have.. but not just with https but with any tcp protocol that
dont like the packets to be sent 1 to 1 host and 2 to 2 host and 3 to
host 3.
>
> I tend to set gc_interval with 1 and a higher value for gc_timeout.
I will try to ask about it more in the netdev later.
Thanks,
Eliezer
next prev parent reply other threads:[~2013-11-07 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 1:55 A question about routing cache (for load balancing) Eliezer Croitoru
2013-11-07 10:26 ` Humberto Jucá
2013-11-07 16:52 ` Eliezer Croitoru [this message]
2013-11-07 20:59 ` Humberto Jucá
2013-11-07 22:03 ` Eliezer Croitoru
2013-11-07 22:39 ` Neal Murphy
2013-11-07 23:53 ` Humberto Jucá
2013-11-08 0:02 ` Humberto Jucá
2013-11-08 0:39 ` Humberto Jucá
2013-11-08 1:23 ` Eliezer Croitoru
2013-11-08 2:29 ` Humberto Jucá
2013-11-08 2:35 ` Humberto Jucá
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=527BC564.1000008@ngtech.co.il \
--to=eliezer@ngtech.co.il \
--cc=betolj@gmail.com \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.