From: Jeff Largent <jlargent@imagelinks.com>
To: Glynn Clements <glynn.clements@virgin.net>
Cc: Kev <savage-garden@hanikamail.com>,
Linux Admin <linux-admin@vger.kernel.org>
Subject: Re: Re[4]: Linux Help
Date: Wed, 21 Jul 2004 14:01:52 -0400 [thread overview]
Message-ID: <1090432912.4897.8.camel@milhouse.imagelinks.com> (raw)
In-Reply-To: <16636.21568.952345.578826@cerise.nosuchdomain.co.uk>
Glynn,
I'll let you correct me if I'm wrong, but isn't ip filtering also a
memory requirement? I'm thinks specifically of connection tracking.
Jeff
On Mon, 2004-07-19 at 19:07, Glynn Clements wrote:
> Kev wrote:
>
> > i was just saying what i will be running on the server, i was asking if
> > i can run all that on a P1/166Mhz
>
> It depends upon the amount of network traffic.
>
> Networking daemons (and the IP filtering code) only consume CPU time
> when they're actually doing something, and the amount of CPU time used
> is roughly proportional to the amount of work they have to do.
>
> Try it. If the load average is consistently high, you need a faster
> CPU. If the hard disk is always busy, you need more RAM. If the box is
> mostly idle but it still seems too slow, you need a faster Internet
> connection.
next prev parent reply other threads:[~2004-07-21 18:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 17:34 Linux Help Kev
2004-07-19 17:46 ` Jens Knoell
2004-07-19 17:53 ` Re[2]: " Kev
2004-07-19 18:02 ` Adam Lang
2004-07-19 18:09 ` Re[4]: " Kev
2004-07-19 23:07 ` Glynn Clements
2004-07-20 15:20 ` Re[6]: " Kev
2004-07-20 15:31 ` Sascha Retzki
2004-07-21 3:09 ` joy
2004-07-21 3:26 ` Re[2]: " Kev
2004-07-21 18:01 ` Jeff Largent [this message]
2004-07-21 19:02 ` Re[4]: " Glynn Clements
2004-07-22 15:44 ` Jeff Largent
2004-07-22 16:18 ` Glynn Clements
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=1090432912.4897.8.camel@milhouse.imagelinks.com \
--to=jlargent@imagelinks.com \
--cc=glynn.clements@virgin.net \
--cc=linux-admin@vger.kernel.org \
--cc=savage-garden@hanikamail.com \
/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;
as well as URLs for NNTP newsgroup(s).