From: Alexandru Dragoi <alex@zoomnet.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Dual CPU performance in routing
Date: Mon, 06 Nov 2006 10:21:12 +0000 [thread overview]
Message-ID: <454F0C98.10003@zoomnet.ro> (raw)
In-Reply-To: <183728573.20061106105325@mtm-info.pl>
GolemMTM wrote:
> Hello
>
> I have question, currently using linux box as router. It only route packets.
> Currently there is 80k packets/sec and this cause 90% CPU usage on
> Intel Celeron 3ghz CPU.
> Did multiprocessor system like 2x XEON DP 3.4ghz will divide CPU
> usage between 2 CPU and will allow double routing performance ?
>
>
>
It will improve performance if irqs are balanced, but not double. Also,
90% seems like a lot. If you use firewalling (many linear rules) and qos
(many linear u32 filter rules), they will cost a lot of performance, you
will se that with top, on soft interrupts (si). I suggest you to use
intel gigabit cards on pci64.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-11-06 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 9:53 [LARTC] Dual CPU performance in routing GolemMTM
2006-11-06 10:11 ` Dmytro O. Redchuk
2006-11-06 10:21 ` Alexandru Dragoi [this message]
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=454F0C98.10003@zoomnet.ro \
--to=alex@zoomnet.ro \
--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.