All of lore.kernel.org
 help / color / mirror / Atom feed
From: Derek Sims <derek@interdart.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Which CPU for heavy traffic with much filtering/shaping?
Date: Mon, 19 Nov 2007 17:55:20 +0000	[thread overview]
Message-ID: <4741CE08.8020506@interdart.co.uk> (raw)
In-Reply-To: <47415A73.9020107@interdart.co.uk>

Marek Kierdelewicz wrote:
>> Hi
>>     
>
> Hi
>
>   
>> I have a router with a large number of iptables rules and some
>> extensive traffic shaping (HTB + RED + ... ) + conntrack.
>>     
>
> Performance boost tips:
>
> - Use "set" module instead of sequential iptables rules. It can lower
> cpu usage.
>   

Hmm - I don't know what the "set" module is - can you point me to some 
documentation please?
> - Use hashing filters for shaping if you're using many u32 filters.
>   
Only 3
> - configure conntrack to use bigger hashsize for better performance;
> i'm passing following parameter to kernel in grub to achieve this:
> ip_conntrack.hashsize\x1048575 
>
>   
I have 64k in conntrack_max and hashsize of 16000
Currently running with about 20000 conntrack connections

I will try increasing this
> - configure routecache to use bigger to use more memory for better
> performance; i'm passing following parameter to kernel in grub to
> achieve this: rhash_entries$00000
>
>   
>> 1. What processors should I be looking for in order to achieve the
>> best routing throughput on a linux router?
>>     
>
> I've had good experiences with P4 (with and without HT), Athlon64, Xeon
> [dempsey], Xeon [woodcrest]. The last one is the best choice because of
> the large cache and architecture. I think you can use Core 2 Duo too
> if you want to save some money.
>
>   
Thanks - I will see what I can get
>> 2. Is it true that multicore processors will not help much in this 
>> situation?
>>     
>
> Not true. In your setup with two nics with same load you can easily use
> two cores. You can assign each nic to different core by the means of
> smp_affinity setting in /proc/irq/... or by using irqbalance daemon.
>
>   
That is good news :) - however I guess 4 core with dual ethernet would 
not help very much!
>> Best regards,
>> Derek
>>     
>
> pozdrawiam
> Marek Kierdelewicz
> KoBa ISP
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>   
Best regards,
Derek
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-11-19 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19  9:42 [LARTC] Which CPU for heavy traffic with much filtering/shaping? Derek Sims
2007-11-19 16:40 ` Marek Kierdelewicz
2007-11-19 17:55 ` Derek Sims [this message]
2007-11-19 23:08 ` sawar
2007-11-20  1:03 ` Marek Kierdelewicz
2007-11-20  3:15 ` Mohan Sundaram
2007-11-20  3:30 ` Mohan Sundaram
2007-11-20 16:03 ` Marco C. Coelho

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=4741CE08.8020506@interdart.co.uk \
    --to=derek@interdart.co.uk \
    --cc=lartc@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.