Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] P4 dual core vs AMD64 dual core with HTB
Date: Mon, 30 Jan 2006 15:29:53 +0000	[thread overview]
Message-ID: <43DE30F1.5030902@gmx.net> (raw)
In-Reply-To: <a763a15b0601300643t739ae2bcmc31a63adb8afa3ad@mail.gmail.com>

Hi,

foxy 202 schrieb:
> 
> 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 ?
> Currently my problem is that i have too big system load over CPU / 60-80%/
> and packet dropping. at every 15-20sec i have traffic freeze for 1-2sec.
> when more users are online.

An Athlon64 3200+ should be sufficient for 200-400 MBit/s in each direction
with HTB and traffic accounting. At least it works for me. However, if you
start using tcpdump, your CPU usage will go through the roof.

Suggestion: Use oprofile and find out what demands the most performance in
your setup, then fix that and retest.


Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2006-01-30 15:29 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 [this message]
2006-01-30 15:42 ` Paweł Staszewski

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=43DE30F1.5030902@gmx.net \
    --to=c-d.hailfinger.devel.2006@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox