What are the bandwidth requirements for Oritor?

You’ll need good upstream and downstream bandwidth from the server. We recommend (at least) 100 MBits/second bandwidth in both directions.


When sharing a webcam as a moderator Oritor lets you select 160×120, 320×240 or 640×480. These use the same amount of bandwidth, roughly 30-50 kbytes/second per stream.


For example, if you have a room with 5 users, each sharing their webcam, then you can calculate the bandwidth usage as follows:


Y = 30-50 Kbytes/sec; let’s assume 40 Kbytes/sec on average

W = amount of webcams that are streaming

U = amount of users that are watching

For calculations:


server incoming bandwidth: W*Y

server outgoing bandwidth: W*(U-1)*Y (minus one since a broadcaster does not have to subscribe to his own stream)

For example, with 5 users in a room with 5 webcams streaming, the bandwidth calculation is as follows:

in: 5*40 = 200 Kbytes/sec incoming bandwidth needed to the server (e.g. 1.6 Mbit)

out: 5*(5-1)*40 = 800 Kbytes/sec outgoing bandwidth needed from the server (e.g. 6.4 Mbit)

Total traffic used after one hour: 60 mins*60 secs*(200 + 800) = 3.6 Gbyte traffic per hour

If you’d have a typical conference situation with the presenter broadcasting their webcam to 30 remote participants, the calculation is as follows:

in: 1*40 = 40 Kbytes/sec incoming (e.g. 0.32 Mbit/sec)

out: 1*(30-1)*40 = 1160 Kbytes/sec outgoing (e.g. 9.3 Mbit/sec)

Total traffic used after one hour: 60 mins*60 secs*( 40 + 1160) = 4.3 Gbyte traffic per hour

If you have 10 of those conferences, then your server needs to be able to output 93 Mbit/sec; that’s not much in a LAN, but it’s a lot if you’re in a hosted environment.

Large “cafe-style chatroom”: 20 viewers, 8 people broadcasting with a webcam:

in: 8*40 = 320 Kbytes/sec ( 2.5 Mbit )

out: 8*(20-1)*40 = 6080 Kbytes/sec ( 48.6 Mbit )

Total traffic used after one hour: 60 mins*60 secs*( 320 + 6080 ) = 23 Gbyte traffic per hour

Sharing slides takes almost no bandwidth beyond the initial uploading/downloading of slides. When the presenter clicks to show the next slide, the viewers receive a “move next slide” command in their Oritor client, and they load the next slide from the local cache. Chat has almost no bandwidth as well.

Desktop sharing takes the most bandwidth, and it’s dependent on the area chosen by the presenter (full screen and region) and how often their screen updates.

A VoIP connection to the Oritor server takes roughly 20 kB/sec per user. The bandwidth for VoIP grows linearly with number of users. For example, if there are 20 participants in a conference, then the bandwidth requirements for the server to support VoIP is 20 * 20 KBytes/sec = 400 kBytes/sec.

If the presenter has only 100 KByte/second upstream, then performing VoIP, video, and desktop sharing will not fit within that upstream constraint. In reality, red5/Flash does a good job of using limited bandwidth and actually works quite well. In the case of desktop sharing, the remote desktops will still receive updates, but the refresh will be much slower than if the presenter was on a LAN (such as within the university or college network).


Posted in: Technical