Network slowing down using Blue Iris, then full speed after shutting down and turning back on

ENTPNR

n3wb
Jan 2, 2025
3
0
Roswell, Ga
Dedicated PC just for Blue Iris. Plenty of resources only eight cameras, not doing any recording and only motion detection on a few cameras. Three cameras are hardwired Amcrest POE 4K, four cameras are Amcrest 4k WiFi. All cameras are set at frame rate 15 and other settings are relatively low. I have throttled back all the camera settings to a very conservative level. Just after starting up Blue Iris, all cameras active, network is at full speed. Can be like this for hours or days then the network will drop in speed significantly (80%). Turned off individual cameras or all the cameras has no effect on speed. Turned off or unplugged every other device on the network one at a time with no effect.. Closing the Blue Iris app however, returns the network to full speed. Then without rebooting, starting the blue Iris app again speeds are back to normal, for a while. I have been monitoring the bandwidth usage on my router, which is showing no abnormally high amount of data being pushed through any camera. As far as data to the server PC, I am getting some fluctuations that I have yet to completely explain, but they’re only swinging in the band with by 100 Mb on one gigabyte network with most equipment capable of 2.5. This amount of data draw shouldn’t be noticeable and certainly my speed tests are showing much less available bandwidth. That Speedtest is being run on both wireless and direct wired connections. Speed from ISP is consistently one point gb. Same results whether I’m on the hardwired adapter on the server PC or using its internal wireless. Running windows 11. Would love to see if anyone can give me some insight, next step is to strip PC server down, reformat and reinstall everything and see where I’m at.
 
The three possible things I can think of are a wonky driver on your ethernet card or sending the cameras through the router or an unstable version of BI.

We have seen instances here were a bad ethernet driver is wreaking havoc on the system.

Are you on auto-update of BI and if so maybe it updated to an unstable beta version. Most here do not update and only update when a feature we want or need is added.

But I suspect it is having all your cameras going thru the router, coupled with wifi cams.

Most here do not have their cameras going through the router and instead of taking their cameras off their main network via a dual NIC (2nd ethernet port) on their BI computer or VLAN switch.

Cameras connected to Wifi routers (whether wifi or not) are problematic for surveillance cameras because they are always streaming and passing data. And the data demands go up with motion and then you lose signal. A lost packet and it has to resend. It can bring the whole network down if trying to send cameras through a wifi router. At the very least it can slow down your entire system.

Unlike Netflix and other streaming services that buffer a movie, these cameras do not buffer up part of the video, so drop outs are frequent, especially once you start adding distance. You would be amazed how much streaming services buffer - don't believe me, start watching something and unplug your router and watch how much longer you can watch NetFlix before it freezes - mine goes 45 seconds. Now do the same with a camera connected to a router and it is fairly instantaneous (within the latency of the stream itself)...

The same issue applies even with the hard-wired cameras trying to send all this non-buffer video stream through a router. Most consumer grade wifi routers are not designed to pass the constant video stream data of cameras, and since they do not buffer, you get these issues. The consumer routers are just not designed for this kind of traffic, even a GB speed router.

So the more cameras you add, the bigger the potential for issues.

So what could be happening is BI is still requesting those lost packets that add up quickly and when you kill BI, the requests for the dropped packets stops and speed returns to normal.


This was a great test that SouthernYankee tried and posted about it here:

I did a WIFI test a while back with multiple 2MP cameras each camera was set to VBR, 15 FPS, 15 Iframe, 3072kbs, h.264. Using a WIFI analyzer I selected the least busy channel (1,6,11) on the 2.4 GHZ band and set up a separate access point. With 3 cameras in direct line of sight of the AP about 25 feet away I was able to maintain a reasonable stable network with only intermittent signal drops from the cameras. Added a 4th camera and the network became totally unstable. Also add a lot of motion to the 3 cameras caused some more network instability. More data more instability.
The cameras are nearly continuously transmitting. So any lost packet causes a retry, which cause more traffic, which causes more lost packets.
WIFI does not have a flow control, or a token to transmit. So your devices transmit any time they want, more devices more collisions.
As a side note, it is very easy to jam a WIFI network. WIFI is fine for watching the bird feed but not for home surveillance and security.
The problem is like standing in a room, with multiple people talking to you at the same time about different subjects. You need to answer each person or they repeat the question.

Test do not guess.

For a 802.11G 2.4 GHZ WIFI network the Theoretical Speed is 54Mbps (6.7MBs) real word speed is nearer to 10-29Mbps (1.25-3.6 MBs) for a single channel


And TonyR recommends this (which is the preferred way IF you want to do wifi)

The only way I'd have wireless cams is the way I have them now: a dedicated 802.11n, 2.4GHz Access Point for 3 cams, nothing else uses that AP. Its assigned channel is at the max separation from another 2.4GHz channel in the house. There is no other house near me for about 300 yards and we're separated by dense foliage and trees.

Those 3 cams are indoor, non-critical pet cams (Amcrest IP2M-841's) streaming to Blue Iris and are adequately reliable for their jobs. They take their turns losing signal/reconnecting usually about every 12 hours or so for about 20 seconds which I would not tolerate for an outdoor surveillance cam pointed at my house and/or property.

But for me, this works in my situation: dedicated AP, non-critical application and periodic, short-term video loss.... if any one of those 3 conditions can't be achieved or tolerated, then I also do not recommend using wireless cams. :cool:
 
  • Love
Reactions: SpacemanSpiff
Just after starting up Blue Iris, all cameras active, network is at full speed. Can be like this for hours or days then the network will drop in speed significantly (80%).
How are you measuring network speed? How are you determining that it's the network (vs your client or host) that's slowing down? Do you only see the slow down in your measurement or is there a practical effect that you're noticing and that's what caused you to start measuring things? If the latter, how does that show itself?
 
  • Like
Reactions: ENTPNR
How are you measuring network speed? How are you determining that it's the network (vs your client or host) that's slowing down? Do you only see the slow down in your measurement or is there a practical effect that you're noticing and that's what caused you to start measuring things? If the latter, how does that show itself?
Hi, a couple different ways starting with seat of my pants. Then I will try speed guide or fast.com on a wired PC and an iphone, 5ft from router. Test with the built in test on router interface gives correct, full speeds everytime.
 
The three possible things I can think of are a wonky driver on your ethernet card or sending the cameras through the router or an unstable version of BI.

We have seen instances here were a bad ethernet driver is wreaking havoc on the system.

Are you on auto-update of BI and if so maybe it updated to an unstable beta version. Most here do not update and only update when a feature we want or need is added.

But I suspect it is having all your cameras going thru the router, coupled with wifi cams.

Most here do not have their cameras going through the router and instead of taking their cameras off their main network via a dual NIC (2nd ethernet port) on their BI computer or VLAN switch.

Cameras connected to Wifi routers (whether wifi or not) are problematic for surveillance cameras because they are always streaming and passing data. And the data demands go up with motion and then you lose signal. A lost packet and it has to resend. It can bring the whole network down if trying to send cameras through a wifi router. At the very least it can slow down your entire system.

Unlike Netflix and other streaming services that buffer a movie, these cameras do not buffer up part of the video, so drop outs are frequent, especially once you start adding distance. You would be amazed how much streaming services buffer - don't believe me, start watching something and unplug your router and watch how much longer you can watch NetFlix before it freezes - mine goes 45 seconds. Now do the same with a camera connected to a router and it is fairly instantaneous (within the latency of the stream itself)...

The same issue applies even with the hard-wired cameras trying to send all this non-buffer video stream through a router. Most consumer grade wifi routers are not designed to pass the constant video stream data of cameras, and since they do not buffer, you get these issues. The consumer routers are just not designed for this kind of traffic, even a GB speed router.

So the more cameras you add, the bigger the potential for issues.

So what could be happening is BI is still requesting those lost packets that add up quickly and when you kill BI, the requests for the dropped packets stops and speed returns to normal.


This was a great test that SouthernYankee tried and posted about it here:

I did a WIFI test a while back with multiple 2MP cameras each camera was set to VBR, 15 FPS, 15 Iframe, 3072kbs, h.264. Using a WIFI analyzer I selected the least busy channel (1,6,11) on the 2.4 GHZ band and set up a separate access point. With 3 cameras in direct line of sight of the AP about 25 feet away I was able to maintain a reasonable stable network with only intermittent signal drops from the cameras. Added a 4th camera and the network became totally unstable. Also add a lot of motion to the 3 cameras caused some more network instability. More data more instability.
The cameras are nearly continuously transmitting. So any lost packet causes a retry, which cause more traffic, which causes more lost packets.
WIFI does not have a flow control, or a token to transmit. So your devices transmit any time they want, more devices more collisions.
As a side note, it is very easy to jam a WIFI network. WIFI is fine for watching the bird feed but not for home surveillance and security.
The problem is like standing in a room, with multiple people talking to you at the same time about different subjects. You need to answer each person or they repeat the question.

Test do not guess.

For a 802.11G 2.4 GHZ WIFI network the Theoretical Speed is 54Mbps (6.7MBs) real word speed is nearer to 10-29Mbps (1.25-3.6 MBs) for a single channel


And TonyR recommends this (which is the preferred way IF you want to do wifi)

The only way I'd have wireless cams is the way I have them now: a dedicated 802.11n, 2.4GHz Access Point for 3 cams, nothing else uses that AP. Its assigned channel is at the max separation from another 2.4GHz channel in the house. There is no other house near me for about 300 yards and we're separated by dense foliage and trees.

Those 3 cams are indoor, non-critical pet cams (Amcrest IP2M-841's) streaming to Blue Iris and are adequately reliable for their jobs. They take their turns losing signal/reconnecting usually about every 12 hours or so for about 20 seconds which I would not tolerate for an outdoor surveillance cam pointed at my house and/or property.

But for me, this works in my situation: dedicated AP, non-critical application and periodic, short-term video loss.... if any one of those 3 conditions can't be achieved or tolerated, then I also do not recommend using wireless cams. :cool:
WOW, thanks! Great response. I was suspecting collisions, that's what is "feels" like. Switching NICS doesn't help so your theory that is at the router or software level makes sense. Note that if I throttle the NIC back to 100 mb everything is workable I supposed because its reducing the total possible "noise" from the BI Server. I am on a pretty old release 5.??? waiting for 6.x to update. What about a 2nd dedicated router since I have a drawer full of them, LOL? If yes, is this the correct setup? Setup separate Wi-Fi router. Connect BI server to new router. Connect POE switch with wired cameras to new router. Connect WI-FI camera to new router SSID. Connect new router WAN to existing router LAN.
 
Almost.

Set up a 2nd router just for the wifi cams - do not connect an internet cable to it or your other router.

Connect the remaining cameras to a POE switch and connect the 2nd router and BI to it.

Others have found, and I have as well, that using a 2nd router just as a dumb switch and turning wifi off and DHCP off and it would still struggle for this non-buffering video. It is fine to use it as a switch for computers and what not, but it struggles with cameras.