CPU Roof Ignored...
Posted: Fri Aug 18, 2017 9:28 pm
Hi,
I am running a workflow on Version 0.8.0 and I think have a pretty simple flow going and everything runs well and usually ends in success, but occasionally I will run into trouble as I try to move my files from the capture computers onto the networked drives within the transcoding computer where FFAStrans operates. I believe the culprit may be that the FFAStrans cpu roof configuration setting seems to be totally ignored by my workflow. All indications seem to indicate that my cpu is running at or nearly at 100% (99.5%, 99.7%, 97.9%, etc...) whenever it can. Which would be fine my be, the more efficient the better, but that amount of usage by FFAStrans, I believe, is blocking the rest of the system from being able to properly write to the hard drive. Ie, the captured files moving from the capture stations into the locally watched folder on the transcoder where FFAStrans resides are timing out and even the occasional permission denied... And I guess i thought I'd like to see if I could indeed cap to the cpu roof of FFAStrans then I could see if that was indeed the culprit for my files not being able to get written to the watched folders. Any thoughts much appreciated. Great product btw... Thank you, Derek
I am running a workflow on Version 0.8.0 and I think have a pretty simple flow going and everything runs well and usually ends in success, but occasionally I will run into trouble as I try to move my files from the capture computers onto the networked drives within the transcoding computer where FFAStrans operates. I believe the culprit may be that the FFAStrans cpu roof configuration setting seems to be totally ignored by my workflow. All indications seem to indicate that my cpu is running at or nearly at 100% (99.5%, 99.7%, 97.9%, etc...) whenever it can. Which would be fine my be, the more efficient the better, but that amount of usage by FFAStrans, I believe, is blocking the rest of the system from being able to properly write to the hard drive. Ie, the captured files moving from the capture stations into the locally watched folder on the transcoder where FFAStrans resides are timing out and even the occasional permission denied... And I guess i thought I'd like to see if I could indeed cap to the cpu roof of FFAStrans then I could see if that was indeed the culprit for my files not being able to get written to the watched folders. Any thoughts much appreciated. Great product btw... Thank you, Derek