From: "Paweł Staszewski" <pstaszewski@artcom.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] P4 dual core vs AMD64 dual core with HTB
Date: Mon, 30 Jan 2006 15:42:13 +0000 [thread overview]
Message-ID: <43DE33D5.1000004@artcom.pl> (raw)
In-Reply-To: <a763a15b0601300643t739ae2bcmc31a63adb8afa3ad@mail.gmail.com>
>Hi All,
>
>Please for some advice.
>
>I have Linux router that do traffic control with HTB , routing and traffic
>counting.
>currently machine is with P4 2.2GHZ 1GB RAM. I plan to migrate to dual core
>CPU. I know well
>P4 dual core but is it anybody has experience with AMD64 dual core / or
>single core / for traffic control . I use Deban Linux for my router. Can I
>expect problems with HTB and iproute 2 over ATHLON DUAL CORE/BOX or single
>box ?
I have dual core p4 (64bit compiled) with hfsc configuration for 4500users
CPU load on this machine is about 20% Average with 60Mbit/s traffic
I also want to know did the AMD (Opteron) will be better for such solution like traffic management :)
>Currently my problem is that i have too big system load over CPU / 60-80%/
How many users You have ?
How many pps on interfaces ?
How large is traffic load (data) , what kind of traffic ?
Did You use hashing filters for traffic management (filtering) ?
Is this machine is doing NAT or any of iptables things ?
>and packet dropping. at every 15-20sec i have traffic freeze for 1-2sec.
>when more users are online.
What type of interfaces You have ?
Did You use NAPI if available ?
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-01-30 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 14:43 [LARTC] P4 dual core vs AMD64 dual core with HTB foxy 202
2006-01-30 14:47 ` Paul M.
2006-01-30 15:29 ` Carl-Daniel Hailfinger
2006-01-30 15:42 ` Paweł Staszewski [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=43DE33D5.1000004@artcom.pl \
--to=pstaszewski@artcom.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.