From: Mohan Sundaram <mohan.tux@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Hardware Requirements for qdisc htb/sfq
Date: Thu, 15 Nov 2007 01:59:29 +0000 [thread overview]
Message-ID: <473BA7CF.3010201@vsnl.com> (raw)
In-Reply-To: <7C454E01C5FAE748BEFE65F4C6B7FD8BF42B1F@s-marcell.hemc.coop>
Shane McKinley wrote:
> 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.
>
> This is what I have been looking at:
>
> 2.0GHz Dual-Core Xeon, 4GB 667MGz RAM, 2x1Gbit Network Interfaces.
>
> Is this overkill?
>
Speed normally seen in PPS. The 7200 routes approx 1M PPS. I ran our own
routing and classification s/w on a AMD Opteron 2Ghz, 1GB RAM and got
1.1M PPS. Linux Kernel gave approx 700K PPS.
IMHO your h/w is way oversized but why not? H/w is cheap nowadays.
Mohan
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-11-15 1:59 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
2007-11-14 21:51 ` Shane McKinley
2007-11-14 22:04 ` Marek Kierdelewicz
2007-11-15 1:59 ` Mohan Sundaram [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=473BA7CF.3010201@vsnl.com \
--to=mohan.tux@gmail.com \
--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