Hi,
I have a wowza server engine running on AWS EC2
I will do a live broadcast and would like to know which machine to use / CPU on AWS EC2 to support 30 ~ 40 simultaneous connections entry,
RTMP is used to view, moodle system
t2.medium, vCPU 2 , mem 4.0 , IO Low to Moderate
t2.large, vCPU 2 , mem 8.0 , IO Low to Moderate
m4.large, vCPU 2 , mem 8.0 , IO Moderate Yes
I wonder if the above machines can support transmission of about 4 hours, for up to 40 incoming connections ?
There is a great resource around here on benchmarking:
This is performance with transcoding enabled. If you are not doing transcoding, your bottleneck may be network performance, but for what you are talking about 30-40 connections (assume around 2-3 mbps, you are barely talking 100 mbps on the out) and a single incoming stream that is not transcoding, I bet the medium will meet your needs.
If you are open to it, I would suggest you consider looking into Cloudfront as your CDN for delivery, which will further reduce the load on your server (removing it as a single point of connection to your viewers).
Hi,
I have a wowza server engine running on AWS EC2
I will do a live broadcast and would like to know which machine to use / CPU on AWS EC2 to support 30 ~ 40 simultaneous connections entry,
RTMP is used to view, moodle system
t2.medium, vCPU 2 , mem 4.0 , IO Low to Moderate
t2.large, vCPU 2 , mem 8.0 , IO Low to Moderate
m4.large, vCPU 2 , mem 8.0 , IO Moderate Yes
I wonder if the above machines can support transmission of about 4 hours, for up to 40 incoming connections ?
CloudFront supports HTTP live stream types but not RTMP. Depending on the size of your RTMP audience, you could either use a separate Live Edge Application along with the Stream Duplicator module to copy your stream from the Live HTTP Origin Application to the Live Edge Server:
Another option maybe to use a Stream Target to publish your RTMP stream to another CDN that does support live RTMP Stream Types. The following article describes how to setup these Stream Targets:
Best regards,
Andrew
You can pick up more here about Wowza and CloudFront. We use Akamai, so have never done more than read the documentation, so your mileage may vary:
As to transcoding, it sounds like you are not doing it. Transcoding (transrating in most instances, to be specific) generally takes that one source stream and kicks our multiple bitrates. So your source may be at 1.5 to 2 mbps, but you could deliver a 500 kbps and a 1.2 mbps (and play with the screen resolution). This is what drives up the load on the Wowza server, and why the benchmarks focus on that as a measure of performance.
I did not understand very well about CloudFront, and on this transcoding, which would make transcoding? I will transmit at 720x480, and access is via rtmp
I did not understand very well about CloudFront, and on this transcoding, which would make transcoding? I will transmit at 720x480, and access is via rtmp
use Moodle, with some modifications, as with username and password, ie only people registered (40) were able to watch the broadcast
I’ve already set like this:
https://www.wowza.com/docs/how-to-configure-a-wowza-server-as-an-http-caching-origin
and now?
AWS CloudFront :
Select a delivery method for your content.
Web ou RMTP
how will I use RTMP RTMP can choose to CloudFront?
.
You can pick up more here about Wowza and CloudFront. We use Akamai, so have never done more than read the documentation, so your mileage may vary:
Use Wowza Streaming Engine EC2 instances with CloudFro
As to transcoding, it sounds like you are not doing it. Transcoding (transrating in most instances, to be specific) generally takes that one source stream and kicks our multiple bitrates. So your source may be at 1.5 to 2 mbps, but you could deliver a 500 kbps and a 1.2 mbps (and play with the screen resolution). This is what drives up the load on the Wowza server, and why the benchmarks focus on that as a measure of performance.
The link you sent me to add CloudFront, I can not use RTMP, look note below:
Note: As shown in the previous figure, HTTP origin applications support all HTTP streaming playback types by default. They don’t support the RTMP and RTSP playback types.