You dont need to save video to the ssd. Get a 50 dollar 250gb drive for the OS, blue iris and the database. You wont have any problems. Buy a reliable brand and series, like the crucial mx500. You wont have any problems and the performance difference will be night and day. Every pc and every blue iris server should have one.Is the continuous writing & deleting of video data excessively HARD on SSD drives? I am considering replacing a 1tb hard drive in a 5 year old system with an SSD as the boot / C: drive.... Will a Blue Iris server be excessive and shorten the longevity (and reliability) of an SSD?
OK-- I thought BI recommends the "New" folder as well as DB be on the C drive..... ???You dont need to save video to the ssd. Get a 50 dollar 250gb drive for the OS, blue iris and the database. You wont have any problems. Buy a reliable brand and series, like the crucial mx500. You wont have any problems and the performance difference will be night and day. Every pc and every blue iris server should have one.
You dont need to place the new folder on the ssd. You can. The 1tb mx500 for example has a 360TB write endurance rating. It can probably go much higher before you see issues. So even if you write 10tb a month that is 3 years+, and likely much much longer.OK-- I thought BI recommends the "New" folder as well as DB be on the C drive..... ???
EDIT:
View attachment 61546
key word: should --- If I used the current 1tb drive as the "new" folder, and the WD Purple continues as Store-- then I'm just as fast as before.
OK--- Someone else did a new build and had a 1TB NVME drive-- assumed the reason was that putting New on anything but C is asking for BI trouble... Thanks for clarifying this! Instead of spending $160 or so on a 1TB drive-- they could get a 250 and another low-end camera.You dont need to place the new folder on the ssd. You can. The 1tb mx500 for example has a 360TB write endurance rating. It can probably go much higher before you see issues. So even if you write 10tb a month that is 3 years+, and likely much much longer.
A side note:
If you are using a complete disk for large video file storage (BVR) continuous recording, I recommend formatting the disk, with a windows cluster size of 1024K (1 Megabyte). This is a increase from the 4K default. This will reduce the physical number of disk writes, decrease the disk fragmentation, speed up access.
I like a lot of people on the forum use the SSD for the C drive, windows OS and all BI files except the recorded video. I use a Samsung Evo 250GB. I have had zeo problems with the EVO. I have had a Kingston 240GB die, it just got slower and slower as it was trying to recover errors.
Thanks to your frequent guidance on this I recently remembered to do this for my video storage drives. Hoping it helps, with video files being so big I'm banking on the performance of less fragmented files will be a big performance boost while watching clips etc.If you are using a complete disk for large video file storage (BVR) continuous recording, I recommend formatting the disk, with a windows cluster size of 1024K (1 Megabyte).
One definite impact is more slack/wasted space on the disk. Think of cluster size as the smallest increment of storage, so if you select something small you have less wasted space when a file is slightly too big for a cluster, but you can have a file broken into thousands of little fragments over time (at least for working files).Is there a downside to this? Does it impact some other aspect of disk operation?
Ahhh.... I have BI recording a jpeg every 10 minutes on all cameras. I would need to figure out a different way to do that-- or that cluster size would waste a LOT of space.... those pics are 530k on my newest 4mp cameras. That would be 2 gb per week-- roughly. I could dedicate 10 gb of space and keep a good 5 week collection of photos to use for time lapse.... just send them to a different physical drive to not waste space on my video drive....
One place I have to put some thought into is the JPEG Alerts, you may have to look at your own situation but most of my alert images are 250-400kB which means 50-60% of each cluster would be wasted so might not want such a large cluster size in that case, as the alerts folder would balloon in size if you have a lot of them.