Question / Help Is my OBS and/or nginx broadcasting?

[antigua]

I'm using OBS and nginx to broadcast meetings in my company. OBS is installed in one pc, and nginx is installed in another PC. Both PCs are Windows.

When I press "start streaming", the nginx PC's load of network interface goes up by 2% as each client connects.
Last time of meeting, more than 20 people connected and the load went up to 50%. Later, I installed Wireshark and found that the nginx PC sends a lot of 1514-bytes TCP and RMTP packets to all the clients individually.

My boss says this is not a problem because OBS is just broadcasting packets, and other computers can use network as usual. He also points that broadcasting packets travel as electric signal, so the network load of nginx PC does not affect to bandwidth.
In my opinion, OBS and/or nginx are sending usual packets, not broadcasting packets, and this is going to use up bandwidth in the long run.

Please tell me what we are misunderstanding, and what we need to do to broadcast meetings without occupying network traffic.

abstract nginx.conf 
http {
    server {
        listen 8888;
        
        location / {
            root live;
            index index.html index.htm;
        }
    }
rtmp {
    server {
        listen 1935;
        application live {
            live on;
            }
    }
}

abstract nginx\live\index.html
<script src="./utils.js"></script>
<script src="./flowplayer/flowplayer-3.2.13.min.js"></script>
<script type="text/javascript">SetupPlayer();</script>

abstract nginx\live\utils.js
    flowplayer("player", "./flowplayer/flowplayer-3.2.18.swf", {
        plugins: { influxis: { url: "./flowplayer/flowplayer.rtmp-3.2.13.swf", netConnectionUrl: 'rtmp://' + location.hostname + '/live/' } },
        clip: { url: 'livestream', live: true, autoPlay: true, scaling: 'fit', provider: 'influxis',

abstract OBS config
broadcast
    URL: rmtp://10.20.30.40:1935/live
Output
    Output mode: normal

 

[Harold]

rtmp is unicast, but unless your switching backbone has a bottleneck that isn't on the rtmp server's network port(s), you will be fine performance-wise.

 

[antigua]

rtmp is unicast, but unless your switching backbone has a bottleneck that isn't on the rtmp server's network port(s), you will be fine performance-wise.

Thank you for your comment. I would like to have a comment on what we can do to broadcast meetings without occupying network traffic. Thank you.

 

[R1CH]

Sending video will always require some amount of bandwidth. If all the viewers are in the same LAN then UDP multicast is about as efficient as you can get assuming all your network gear supports it, but this is not possible with RTMP.

Note that this is all LAN (internal) bandwidth, it will not affect your internet bandwidth and most LANs will have more than enough bandwidth spare.

 

[antigua]

Hi R1CH,
Thank you for your reply. As you mentioned, I'm thinking about sending data in UDP. It should be possible because broadcast must be reached only within my company.
Thank you ;D