Quote:
Originally Posted by Senior_Spank
Actually you are horribly horribly wrong which makes me wonder about the way you brag in your first post. Forgive me if I go about the rest of my comment with a bit of arrogance, but just because you teach a dog to play dead does not mean you are Cesar Millan.
Like I said; everything on our system has been configured with huge amounts thought and foresight. The reads are that way because of the IOScheduler we use combined with the massive read-aheads we have set. The system has the capacity, why not use it. Also, the fact that there is 0 IO load, it shouldn't matter how much it's reading because it's not the bottleneck.
We do not use NFS mounts, It's { Storage => Wowza => Internet } to keep overhead and possible complications as limited as possible.
Now, the way I see it is I have one solution should I want to keep using this software while keeping up with growth. An NFS, and a bunch of servers with a shitload of RAM and a shitload of CPU power. Put it behind a load balancer (or round-robin the DNS to a series of IPs) and for every gigabit of capacity I want to add, I need an additional $3,000 to $4,000 in hardware overhead. (This of course doesn't include power overhead, additional network ports used on the switch, whatever)
If you like to wipe your ass with $20's, then Wowza is the software for you. For those of you who live in a world with budget's and do not enjoy responding to server alerts at 3 AM (Don't get me started on the fact it doesn't "crash" but just stops serving video files at random.) then I'd recommend skipping Wowza.
On a positive note about WowzaMedia - Their software does work, and their support team actually seems to be very responsive to customers. If you are running a smaller operation and want very good streaming and scrubbing. Then Wowza may be the solution for you. My comments are only speaking to people who plan to be serving multiple gigabits of content.
And lastly, a bit of why I've even had to deal with this headache...
We were able to saturate a 2 gigabit connection with a modest $2,000 server with 4 gigs of RAM and using nginx. The only problem of course, is the MP4 atom at the beginning of the video causing slow load times for long videos. Wowza (and other FMS servers) solves this problem with rtmp.
In our efforts to get this working we have spent over $6,000 in additional equipment. Dual Quad-Core processors, 32GB of RAM, SSD drives, etc.
|
I can give you a hint. We have had atoms engineered "correctly" with only 4G of ram push out 1.5G without any problems. Konrad can contest to our server setups.
We have spent countless hours engineering streaming solutions and have perfected a proven solution. You don't need 32g of ram or dual quads. But a simple Atom server.
Wowza is a great product we have several dozen machines running it. It fixes problems that are left open that lighttpd and nginx would fail at. The biggest one that I can think of? Indexed keyframes in flv files. wowza takes care of it. Lighttpd and nginx use the same backend modules to handle these file types and both have identical issues. Skipping through videos just wont happen. Also with MP4 files that are not correct they will just cause nginx/lighttpd to hang and stall out.
Best advice keep things simple, it works the best.