Repeated disk overallocation

Dewcal

Getting the hang of it
Oct 19, 2019
88
39
Darlington
I am using a headless Windows 11 PC (i7-8700 with 32Gb RAM, 25oGb C SSD and 12 Tb Seagate HDD) using some 25 wired cameras - a mixture of Hikvision for security and "Chinese" for nature watching, bird boxes etc. The PC runs 24/7 and is also used for Homeseer (Home automation) and CumulusMX (weather).

Since upgrading to 5.9.9.43 in April this year, I have had repeated "New" folder overallocations. I have the New folder set to 100Gb which leaves some 60Gb free on the C drive. The New folder frequently (every couple of days) shows a size of 165Gb, effectively taking over the rest of the C drive. I have to move/delete the "new" files and repair the database to get the system to produce alerts etc again - it also stops my home automation...

I have 5 of the security cameras set to continuously record with direct to disk in one-hour segments - this should give plenty of time for files to close and be transferred to storage.

I have been in email contact with support since April and nothing has solved the issue - I appear to be going around in circles.

In addition, I am also seeing high CPU usage of 50-70%, at times going to 90% - I am using sub-streams on all cameras and direct-to-disk recording.

Can anyone give me any clues as to how I can get BI to be reliable again? There is little point in a system that decides to effectively stop my PC from working every couple of days.

While I think I have all cameras set up correctly, can anyone kindly point me to a current "idiot's guide" on how to set up the cameras? I have requested this via support to no avail. With such a guide, I can at least double-check my settings.

Thanks for any help.
 
  • Like
Reactions: Flintstone61
Put the "New" folder on a separate partition or separate drive. The C drive free space can change with Windows updates, and Restore points building up, and saved pictures. These types of thing can impinge on the designated drive space. Most use a separate drive for the NEW folder because streaming generates Terabytes of data.
 
I think almost everybody here who been here awhile is not storing camera stream data to the C:\ drive. or if they were, not anymore. We all get thrown into the learning curve here. School of Hard Knocks if you will.
 
  • Like
Reactions: tigerwillow1
Reduce the cameras FPS to 15 if you haven't already. 30 FPS uses up drive space faster.
 
Reduce the cameras FPS to 15 if you haven't already. 30 FPS uses up drive space faster.
Many thanks for the suggestions - appreciated. All cameras at 15fps. Will look at partitioning C drive - not sure I have connections for a third drive in the PC. Any reason why "new" and "stored" should not be on the same drive?
 
There isn't much reason to have both New and Storage on the same machine otherwise you are spending all your time copying and deleting.

Most people set it up so their large HDD is New and then delete when that is about 90% full. Storage folder is then unnecessary.

As for your CPU usage, that sounds unreasonably high unless one of the other apps are using it up.

Read the following post on optimizing BI.
 
There isn't much reason to have both New and Storage on the same machine otherwise you are spending all your time copying and deleting.

Most people set it up so their large HDD is New and then delete when that is about 90% full. Storage folder is then unnecessary.

As for your CPU usage, that sounds unreasonably high unless one of the other apps are using it up.

Read the following post on optimizing BI.
Many thanks for comments - I was wondering about the need for New and Storage folders. I will review the information on optimisation later today - time to take motorbike out.....
 
Don’t waste CPU time moving files around between disks in the same machine.

I have 2 HDDs in my system, I’ve setup half my cams to directly write the clips to 1 and the rest directly to the other. BI then only has to maintain the disk allocation by deleting older clips.

When splitting the cams over multiple disks do it so that if you have multiple cams covering the same area that if a disk should die you still will have footage from the other view.
 
Don’t waste CPU time moving files around between disks in the same machine.

I have 2 HDDs in my system, I’ve setup half my cams to directly write the clips to 1 and the rest directly to the other. BI then only has to maintain the disk allocation by deleting older clips.

When splitting the cams over multiple disks do it so that if you have multiple cams covering the same area that if a disk should die you still will have footage from the other view.
Many thanks for the suggestion - it makes sense and something to try when I find another HDD.