Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Rudi Starcevic <tech@wildcash.com>
To: netfilter@lists.netfilter.org
Subject: Iptables Media Server Performance
Date: Wed, 29 Dec 2004 15:23:14 -0800	[thread overview]
Message-ID: <41D33C62.1010505@wildcash.com> (raw)

Hi,

I need to implement a firewall for a linux machine whose primary task is 
a media server.
That is a web site with loads of video: mpeg, avi and wmv formats.

I have everything working well and am very happy.
However I am wondering if there is anything I should consider with 
regard to higher performance.

I have an idea of how much I should try and squeeze out per machine and 
would appreciate any feedback.

I want to ensure the machine is not overloaded resulting in slow video 
streaming/downloading performance.

Currently for:

1) 4000 members this machine has about
2) 200 users at any one time
3) which make about 1500 simultaneous connections
4) using about 75 MBps
5) on a machine with MemTotal: 905336 kB

Right now there are 230 connected users and rising.

When it gets to an average of 250 I'm thinking that is about as much as 
I can get
from this machine and will add more with DNS round robin.

Tasks:
a) www server
- tcp port 80
b) port-forwarding/NAT for a Microsoft Media Server
- tcp port 1755
- udp port 1755
- tcp port 554
- udp port 554
- udp port 5004
- udp port 5005
c) port-forwarding/NAT for ftp
tcp port 21 DNAT --to 192.168.0.10:21

Your input would be much appreciated.
Does it everything look OK to you? Or am I tripping out?

Thanks
Regards Rudi.


             reply	other threads:[~2004-12-29 23:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-29 23:23 Rudi Starcevic [this message]
2004-12-29  9:08 ` Iptables Media Server Performance Christian Theil

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=41D33C62.1010505@wildcash.com \
    --to=tech@wildcash.com \
    --cc=netfilter@lists.netfilter.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