From: Marek Kierdelewicz <marek@piasta.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Hardware Requirements for qdisc htb/sfq
Date: Wed, 14 Nov 2007 21:36:29 +0000 [thread overview]
Message-ID: <20071114223629.3f00537b@catlap> (raw)
In-Reply-To: <7C454E01C5FAE748BEFE65F4C6B7FD8BF42B1F@s-marcell.hemc.coop>
>My question is what are the general hardware requirements for routing
>to about 20 subnets (class c), traffic shaping for about 50 fiber
>customers (TC QDISC), 2 T1s (straight into the Linux router) and about
>35MB of traffic out to the next ISP? We are planning to implement BGP
>sometime in the near future.
From my experience router load is mostly dependant on pps (packet per
second).
I was doing statefull 550k pps on Athlon64 X2 5200
cpu usage was ~50% per core.
I'm doing stateless > 1m pps on Quad-core Xeon(R) CPU E5345 @ 2.33GHz,
peak cpu usage is less then 25% per core
both configs used e1000 nics, 1GB Ram
both boxes were running BGP
>I have been searching everywhere for some kind of guidelines, but I see
>none. If anyone could give me a round about answer that would point me
>in the right direction I would be obliged.
Use irqbalance of smp affinity to distribute irqs between cores. Make
your router stateless or optimeze netfilter settings related to
conntrack (more memory, bigger hashtables ect)
>2.0GHz Dual-Core Xeon, 4GB 667MGz RAM, 2x1Gbit Network Interfaces.
Quite a lot of ram for statefull firewall + BGP (1GB would probably
suffice). As for CPU diagnose your network and compare your pps with the
numbers and platforms I specified.
cheers,
Marek Kierdelewicz
KoBa ISP
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-11-14 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 20:44 [LARTC] Hardware Requirements for qdisc htb/sfq Shane McKinley
2007-11-14 21:36 ` Marek Kierdelewicz [this message]
2007-11-14 21:51 ` Shane McKinley
2007-11-14 22:04 ` Marek Kierdelewicz
2007-11-15 1:59 ` Mohan Sundaram
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=20071114223629.3f00537b@catlap \
--to=marek@piasta.pl \
--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.