From: Nickola Kolev <nikky@mnet.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] hardware requirements
Date: Fri, 11 Jul 2003 12:51:07 +0000 [thread overview]
Message-ID: <marc-lartc-105792796317052@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105791819408788@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
On Fri, 11 Jul 2003 14:56:42 +0300 (EEST)
Catalin BOIE <util@deuroconsult.ro> wrote:
: > The only problem I'm experiencing is with heavy udp traffic, f.e. Counter Strike
: > and Bnetd (Diablo, DiabloII, {Star|War}Craft) game play. Then the machine is reaching
: > some really high load averages, like 8 to 10. Have no idea how this
: > could be avoided.
:
: How many filters?
:
Almost the same as the count of classes, i.e. aroung 2000. But not all of them are playing
Couter Strike, probably not more than 20-30.
--
________________________________________________________________________
So long, and thanks for all the fish!
Nickola
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-11 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 10:08 [LARTC] hardware requirements alexandru matei
2003-07-11 11:44 ` Nickola Kolev
2003-07-11 11:56 ` Catalin BOIE
2003-07-11 12:51 ` Nickola Kolev [this message]
2003-07-11 13:01 ` Catalin BOIE
2003-07-12 19:17 ` Leonardo Balliache
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-105792796317052@msgid-missing \
--to=nikky@mnet.bg \
--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