tube site hardware configuration
 

Any suggestions?

i suggest a visit to the toilet, after yesterdays thanks giving dinner..

Job well done.

To help with "user uploads"

http://s1.reutersmedia.net/resources...India-555526-1

You're gonna generally want as much of everything that will fit into the box while still being in your budget.

In all seriousness though, it depends on what you are planning to do...if you're running a tube with all embedded videos you have different requirements then if you are hosting all your own videos and transcoding them into 5 different formats...

I was thinking centos with apache and nginx pulling content off ssds and having a large upload capacity.

SSD's are too small to store enough for tube content, and it'd be too expensive to throw together 2 or 3tb of SSD drives. You'd be better off putting an OS on an SSD, toss apache with nginx in front of it as a proxy and store your content on regular 2-3tb drives, using that as the origin server for a CDN.

The thing is that I have your script making very small flvs. So it becomes feasible to host it on an ssd, the os included. Even 10 sites with thousands of movies will fit on a single 512gb ssd. The content delivery network is avoided by using adobe media server. I get what you are saying though which is gold for the standard crowd. I want speed at a low price.

For the server, this is perfect:
http://www.ovh.ie/dedicated_servers/eg_64g_hybrid.xml
Hosted in Canada for N.America traffic or NE France for euro-traffic.

It's a beast of a machine for the money, with apache and databases running on the SSDs and content on the SATAs. Absolutely no need for content on ssd's since the read capicity of HDDs is far more than required for,delivery.
Personally, I would recommend wowza rather than adobe since it's much more customizable.

What is the benefit of nginx in front of apache? Ok if it's as a load balancer but i see no benefit at all to pass requests from one web server to another on the same machine.
Serve thumbs from nginx, yes maybe.

You setup nginx to respond to js, css, flv, jpg, gif, mp4, etc and pass through everything else to apache. Same sort of idea as using nginx to host just the thumbs but this also serves the pieces of your layout like the css and images from that via nginx. Give's you the best of both worlds...

do they allow adult., ??

If it's legal adult, yes it's allowed. I wouldn't do any grey area stuff like extreme adult etc... but mainstream adult no problem.

Right that's what I was thinking, though I'd do it the other way round - set up nginx as "static.dom.com" and implicitly call all static content from the HTML. That way the nginx proxy process isn't waiting until apache has completed the response in the passthru situation you described.

nginx load balances. ^

yes it does, and it does it very well, but that wasn't what was being discussed - load balancing means >1 server, but what was being discussed was proxying, passing certain requests through to another machine (the same in this case) for certain requests, like css, jpg etc.
you asked for advice, we're all giving advice ;)

Whatever the script calls for and whatever you need to support your traffic.

storing tube videos on SSDs LOL...
dude you'll need 3TB drives and lots of those...

ssd hosted videos are going to load faster.

is this meant to be a joke?

:1orglaugh:1orglaugh:1orglaugh