For those going to build a dedicated BI PC (Server)

M

MartyO

Banned
Jun 4, 2015
589
20
I contacted BI do see if a multi drive design for a BI surveillance PC was worth it.

I asked:
I'm presently testing, learning BI on my regular PC, but will build dedicated BI surveillance PC.
To maximize performance I would have two SSD drives and one very large USB3 HDD configured as follows.
The idea is separate drives, for smooth operation.

1) OS and BI run on a small SSD drive ( C:)
2) Have BI record to NEW on a second medium size SSD drive (D:)
3) Put Storage on a large USB3 drive (E:).

Once a day or every other day, videos on New will be moved by BI to large USB3 drive.

Does this make sense?


BI Response:
Yes this is the default model ... please see Options/Clips in the software for the New and Stored folder default locations.
 
MartyO said:
I contacted BI do see if a multi drive design for a BI surveillance PC was worth it.

I asked:
I'm presently testing, learning BI on my regular PC, but will build dedicated BI surveillance PC.
To maximize performance I would have two SSD drives and one very large USB3 HDD configured as follows.
The idea is separate drives, for smooth operation.

1) OS and BI run on a small SSD drive ( C:)
2) Have BI record to NEW on a second medium size SSD drive (D:)
3) Put Storage on a large USB3 drive (E:).

Once a day or every other day, videos on New will be moved by BI to large USB3 drive.

Does this make sense?


BI Response:
Yes this is the default model ... please see Options/Clips in the software for the New and Stored folder default locations.
Click to expand...
What Ken meant was that the moving the files to storage is the default model..not using two ssd's...Its a complete waste. There is zero advantage to storing one days footage on a second ssd...if you wish, just use a single ssd for blue iris and the video...you will never reach the write performance limits.
 
Fenderman, I thought my question was as simple and clean describing the use of 3 drives, and Kens response was simple.

I would assume (not conclude) that as BI threads wait for bytes of data to process, they would get them with less latency (for a lack of a better word) when using the 3 drive design Ken called the default model. Probably more so with more cameras and simultaneous recording/playback visual usage.
 
MartyO said:
Fenderman, I thought my question was as simple and clean describing the use of 3 drives, and Kens response was simple.

I would assume (not conclude) that as BI threads wait for bytes of data to process, they would get them with less latency (for a lack of a better word) when using the 3 drive design Ken called the default model. Probably more so with more cameras and simultaneous recording/playback visual usage.
Click to expand...
No, a more clear question would have been specifically asking about using the ssd as a recording medium for a single days record...the proof is in his response that its the default model then pointing you to the storage folder..there is no way the default model was using two ssds..
In fact many users who have many hd cameras recording 24/7 would burn though the ssd really quickly...there is no way that could be the "default"..
Look, I have over 20 BI pc's I can assure you there is no performance impact by not using SSD's to record video. Using an ssd for 1 days recording is a complete waste of money....
 
fenderman said:
No, a more clear question would have been specifically asking about using the ssd as a recording medium for a single days record...the proof is in his response that its the default model then pointing you to the storage folder..there is no way the default model was using two ssds..
In fact many users who have many hd cameras recording 24/7 would burn though the ssd really quickly...there is no way that could be the "default"..
Look, I have over 20 BI pc's I can assure you there is no performance impact by not using SSD's to record video. Using an ssd for 1 days recording is a complete waste of money....
Click to expand...

Ok, experience is something never to be overlooked. Thanks for all your posts. I actually used one of then cause my non H264 cameras were being processed (reencoded) by BI to H.264, saw a post of yours advising direct to disk. This preserved my mjpeg, cut CPU from 25% to 10%, obviously sucked up 2.5 times more disk. I'm playing. I'm very impressed with BI.
 
Run the OS and perhaps BI off the SSD drive, then use a regular HD for the recordings.
 
MartyO said:
Ok, experience is something never to be overlooked. Thanks for all your posts. I actually used one of then cause my non H264 cameras were being processed (reencoded) by BI to H.264, saw a post of yours advising direct to disk. This preserved my mjpeg, cut CPU from 25% to 10%, obviously sucked up 2.5 times more disk. I'm playing. I'm very impressed with BI.
Click to expand...
If you use direct to disc make sure to set pretriggeer recording frames to at least twice the frame rate... Also set the iframes in the camera to match the frame rate. This is important because direct to disc begins recording only when a new complete frame is sent..

Sent via Taptalk
 
It is ideal to put the clip database on a solid state drive, since it is referenced often and lower latency will help operations especially when you get to having lots and lots of clips. However for actual clip recording and playback, unless you have some monster of a system you will run out of CPU time long before you reach the I/O limits of a mechanical hard drive. I wouldn't worry about disk speed unless you are continuously recording over 200 Mbps to a cheap drive or are using a USB 2.0 enclosure or something.
 
You must log in or register to reply here.
Top Bottom