Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What would be, software wise, a good Stack to use for a media server, considering the Ubuntu OS (8.10 up)?

This is supposed to serve large QuickTime video files (.mov) with > 100Mb in average.

We expect the traffic to be high. And, even though total traffic (as in Gb served per month) is not a problem, bandwidth may be (as in Mbits/s).

What are good tips to assemble such a stack? I considered using CDN but since I am doing this for a hosting company, it may be overkill.

share|improve this question

closed as off-topic by Michael Hampton May 1 '15 at 11:10

This question appears to be off-topic. The users who voted to close gave this specific reason:

If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 1 down vote accepted

If you are talking about a webserver with static content only I'd definitely go for lighttpd.

To distribute the load (if indeed necessary) in the first place I'd choose a simple DNS round robin solution, keepalived and/or LVS can come into play later if that is really necessary.

You might also want to look into the several options that tune your IP stack with sysctl before throwing more hardware at it.

If you need to have more than one box I'd use rsync in combination with inotify, so that when you update your "master box" rsync will immediately push out the changes. I'd definitely try to avoid NFS since it would introduce a single point of failure (if not made highly available with some HA technique) and adds yet another layer of network interaction and latency.

The rsync and inotify approach would of probably require a fair amount of scripting but it would keep race conditions where customers want to download a file that is not yet synced to the web server in question to a minimum.

The part saying

I am doing this for a hosting company, it may be overkill

got me thinking. Why not run a BitTorrent tracker and let the CDN build up itself? Or is using HTTP a hard requirement?

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.