Hi,
I would like to know the estimated maximum number of concurrent connection that Wowza server can support for the below config :
4 CPU, 2 Core, 7.5GB RAM.
Windows 2003 x64
Network bandwidth : say no limit/or rather dynamic
Thanks.
Regards,
Boon Seong
Hi,
What bitrate will you compress your streams to? 128 Kbit/s? 256 Kbit/s? 512 Kbit/s?
What is the network connection speed for this server? Is it 10 Mbit/sec, 100 Mbit/sec, or 1000 Mbit/s?
These are critical pieces of data for streaming.
-John
1gbs minus some overhead should provide about 800mbs of throughput.
800mbs /128kbs = 6250
Richard
Lee,
100 incoming live streams is very high. It is possible to handle that many incoming streams with a big server with lots of ram, late-model dual quad cpu and plenty of bandwidth, but 100 is on the high end of any hardware configuration. So you should back it down until you see better playback and add a server to handle the difference.
Richard
With those serverspecs, bandwidth is gonna be your bottleneck. At least until 1Gb/s your server will handle it I think
Hi John,
We will be using 128 Kbits/s stream. As for the network connection speed, we did a benchmark and the speed is around 40Mbps.
Can you also provide the max concurrent connections say I have a 1Gbps network connetction speed at 128 Kbits/s stream ?
Thanks.
Regards,
Boon Seong
Hi John,
What will be the estimated max concurrent connection the server can handle if my network is 1Gbps ?
Regards,
Boon Seong
Hi Myung-Ho,
Please see the performance tests in the FAQ for performance info.
Hi,
Make sure that your Wowza installation is tuned to properly use the system resources you
have available, by closely following this guide:
https://www.wowza.com/docs/general-tuning
A 2Gbit network with 20% overhead should provide you with roughly 1.6Gbit throughput (taking into account 20% overhead)
which will put you right on the edge with 800 * 2Mbit streams.
After tuning, try to test the actual network throughput outside of Wowza to make sure you truly have that 1.6Gbit available, and that the NIC bonding and channel bonding are working properly.
Also try to scale up your testing gradually, say with 400 * 2Mbit, then 600 * 2Mbit etc
to see where it breaks.
Daren
Hi, Richard.
Does 800Mbps of thoughput are maximum bandwidth that wowza can support?
I set up my server as follows;
2.2G Quard Core 2 CPUs
8G RAM
2G network ( two gigabit cards are bonded and physical ports of gigabit network switch are channel bonded also.)
there are two input sources
2Mbps multicast MPEG2 TS streaming channel
1Mbps multicast MPEG2 TS streaming channel
when I try to make 800 sessions to 1Mbps channel, wowza can serve well.
But if I try to make 800 session to 2Mbps channel, wowza droped down all session after about 5 minutes.
What should I do to serve 800 sessions for 2Mbps channels?
Myung-Ho.
Hi, one of my problem was solved by changing test client notebook. 
some notebook(that has gigabit lancard) of specific vendor can not overcome 200Mbps traffic.
After change these notebooks to another model, the concurrent session problem is gone.
And now, I have faced the other problem.
I have plan to service more 100 live channels. Total bandwidth of multicast traffic from encoders are about 150Mbps.
In that case, Quality of HLS stream from WOWZA is seriously bad.
I did almost tune the server based on WOWZA web guide(change processor number, ulimit value, JAVA VM memory, ‘-server’ option etc.)
can you give me any advice to overcome this problem?
Thanks for your reply, Rechard.
My server specs are as follows.
CPU
model name : Intel® Xeon® CPU X5675 @ 3.07GHz
cpu MHz : 1596.000
cache size : 12288 KB
cpu cores : 6
#cat /proc/cpuinfo | grep processor | wc -l
24
RAM 16GB
LAN 2G
Based on your experience, Can you estimate how many live channels can be served with it?
Or do you have any comparison table between server spec and hls service capability?