The problem:
I've had this problem since BI3, and I've moved into BI4x64 bit with still same results.
When BI turns on, all everything is functional for the first 5-10minutes. If there is any kind of motion, or long video stream, the BI just hangs for a long time. The remote viewers (IE/ff/chrome web browser, android) all have video that hang. I'm sure the application is hanging and not sending video to the remote viewers. If we wait ~15-20min, the video will jump forward, work a bit, and hang again.
Back in BI3, the hanging seems to happen when BI3 eats up ~1.5GB of ram. It would never go past 25% CPU usage. Understandable for ram, as it was 32bit.
On BI4x64, BI4 constant hogs around 2.5-4GB of ram, and CPU seems to hover around 50%. Once in a while it spikes to 100%, but it drops real quick.
For the system, there's still plenty of extra ram, cpu, and disk IO available. Why is the remote viewers and BI application hanging? How can I troubleshoot this? Do I have too many cameras connected? This issue is less noticeable when I disable a lot of cameras .
The Setup details:
-The set-up is done on a windows 2008r2 server OS.
-All cameras are continuous recording, and files are broken base on motion. I do this, as i don't trust the record on motion to work perfectly.
I- have the "Pre-Tirgger fram buffer size" unchecked.
I-Recording to AVI format, using H264, Quality 50%, 1024 bit rate, 30 GOP, 0 Max B between P frames, preset: superfast. I have all the files re-encoded to AVI so that we can play back the files remotely on another PC using VLC/Mediaplayer/etc. I also do this is to save on disk space
-All cameras(a mix of foscam, dahua, axis) running ~13FPS with these resolutions:
10 x 640x480
1 x 1280x800
1 x 1280x960
4 x 1280x720
9 x 1920x1080
3 x 1440 x 1376
This is on a gigabit network, running on a supermicro X9DRi-LN4F+ with DUAL socket Xeon E5-2650v2 2.6Ghz(8 core), 16GB Ram, SSD for OS/BI (Images/cache/ db), 2x raid arrays(each composed of 8x4TB drives) for video storage.
Why can't my monster server handle this??
I've had this problem since BI3, and I've moved into BI4x64 bit with still same results.
When BI turns on, all everything is functional for the first 5-10minutes. If there is any kind of motion, or long video stream, the BI just hangs for a long time. The remote viewers (IE/ff/chrome web browser, android) all have video that hang. I'm sure the application is hanging and not sending video to the remote viewers. If we wait ~15-20min, the video will jump forward, work a bit, and hang again.
Back in BI3, the hanging seems to happen when BI3 eats up ~1.5GB of ram. It would never go past 25% CPU usage. Understandable for ram, as it was 32bit.
On BI4x64, BI4 constant hogs around 2.5-4GB of ram, and CPU seems to hover around 50%. Once in a while it spikes to 100%, but it drops real quick.
For the system, there's still plenty of extra ram, cpu, and disk IO available. Why is the remote viewers and BI application hanging? How can I troubleshoot this? Do I have too many cameras connected? This issue is less noticeable when I disable a lot of cameras .
The Setup details:
-The set-up is done on a windows 2008r2 server OS.
-All cameras are continuous recording, and files are broken base on motion. I do this, as i don't trust the record on motion to work perfectly.
I- have the "Pre-Tirgger fram buffer size" unchecked.
I-Recording to AVI format, using H264, Quality 50%, 1024 bit rate, 30 GOP, 0 Max B between P frames, preset: superfast. I have all the files re-encoded to AVI so that we can play back the files remotely on another PC using VLC/Mediaplayer/etc. I also do this is to save on disk space
-All cameras(a mix of foscam, dahua, axis) running ~13FPS with these resolutions:
10 x 640x480
1 x 1280x800
1 x 1280x960
4 x 1280x720
9 x 1920x1080
3 x 1440 x 1376
This is on a gigabit network, running on a supermicro X9DRi-LN4F+ with DUAL socket Xeon E5-2650v2 2.6Ghz(8 core), 16GB Ram, SSD for OS/BI (Images/cache/ db), 2x raid arrays(each composed of 8x4TB drives) for video storage.
Why can't my monster server handle this??