I have been using Ispy for about 1 month now. I am having great results so far. I have 7 HP cameras and it is only using 20 percent of my cpus. The problem I have is the spike I get when I have 2 - 3 cameras record at the same time.
2 things that I can think of that might help me and a lot of other people
1. a delayed encoding process. Let Ispy write the full AVI file to the disk and then process the encode when the system has more resources
2. Put a governor on the FFmpeg process. If we had the option to use 1 - 8 threads that could slow down the ffmpeg encoding and conserve resources. I understand that it would take longer to encode, but waiting an extra 5 - 10 minutes would not be that big of a deal and it would really help cut down on processing.
Do you think either of those 2 ideas would work? I prefer the 2nd one but I am not a coder and have no idea where to start. I did find the FFmpeg readme file, and you can request thread count. (ffmpeg - thread 1) I tested it and it worked great. Without the thread aug the processor was at 99 with the aug it was at 44. I still want Ispy to run unrestricted, just want to put a governor on ffmpeg.
let me know
Got any feature requests or suggestions?
2 posts • Page 1 of 1
Who is online
Users browsing this forum: No registered users and 1 guest