From: "Jamie Harris" <jamie@jharris.homeip.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Packet mangling latency
Date: Thu, 02 Oct 2003 07:36:55 +0000 [thread overview]
Message-ID: <marc-lartc-106508035617513@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106504245621689@msgid-missing>
> The server should be fine. What network bandwidths are you looking into?
Nothing wild, ~10Mb tops
> The more the bandwidth, the higher the requirements. Also, ram is useful
> if you have a lot of smaller connections passing through the server at
> once.
Memory should be a problem from what I've been reading, but at todays
prices I can just fill the box to capacity.
> In my experience I have never felt latency on the line.
What kind of applications and at what bandwidth yourself? Some of the
traffic will be going to/from game servers so latency can become
noticable.
cheers
Jamie...
--
** This message was transmitted on 100% recycled electrons **
_______________________________________________
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-10-02 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 21:06 [LARTC] Packet mangling latency Jamie Harris
2003-10-02 7:36 ` Jamie Harris [this message]
2003-10-02 9:38 ` Mike Miller
2003-10-02 11:58 ` Jamie Harris
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-106508035617513@msgid-missing \
--to=jamie@jharris.homeip.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