From: Robert Penz <robert.penz@outertech.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] good hardware
Date: Wed, 05 Feb 2003 22:17:55 +0000 [thread overview]
Message-ID: <marc-lartc-104448364928239@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104448243926562@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 05 February 2003 22:59, Joshua Daniel Franklin wrote:
> NICs: I've seen several mentions of the Intel eepro NICs. Are they best?
I still believe that the DEC ones are the best, you still can get new 100mbit
nic with tulip chips on port, in our tests they are the best, we've about
1000 of them running here.
ps: intel does now produce that chips, but I don't know which intel nic models
do contain that chip, as we buy cheap cards with that chip on it.
our dealer in munich, justs calls it
CompuShack FASTLine PCI 10/100Mbit/s DEC Chip 32 euro
under linux just load the tuplic.o module.
> Processor: speeds probably don't matter too much (my Cisco 3640 router
> with 4 T1s has a 100Mhz processor, though it's RISC and has optimized
> IOS) but faster processors have faster FSB as well
> Memory: 128 MB probably enough to deal with 100Mb?
not the amount of ram that is important, it's the memory throughoutput , as I
can remember rambus is there better than ddr-ram.
ps: we only buy pcs with 512mb ram and 80gb hd, as it doesn't make much
difference and someday you'll may need it ;-)
> HD: Obviously you want everything in memory, but if you're doing much
> logging you might get a solid-state disk.
and only write in chunks, not each entry alone and not in sync mode ;-)
> I've done a little comparison testing of prebuilt firewall routers with a
> few little DLink/Sonicwall/Netgear boxes vs. an Athlon running IPCop, but
> I'm sure someone has done better hardware tests than mine.
> I'm open to any info. If I get enough for a good summary perhaps it could
> be added to the HOWTO.
> Thanks.
look at the pci performace of the chipset, there are big differences
- --
Regards,
Robert
- ----------------
Robert Penz
robert.penz AT outertech.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE+QY2T8tTsQqJDUBMRAgF4AJ9dUUU3oXTRIqs/XhnClT1dZ8lshQCgn9i4
jZnLT2lPOnrCfRDF7mWqutkŠTL
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-02-05 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 21:59 [LARTC] good hardware Joshua Daniel Franklin
2003-02-05 22:17 ` Robert Penz [this message]
2003-02-06 0:56 ` William L. Thomson Jr.
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=marc-lartc-104448364928239@msgid-missing \
--to=robert.penz@outertech.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 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.