FranceBB
25th November 2020, 10:33
Hi there,
it's me again.
I have several SMB Share with several TB in which masterfiles are stored temporarily before they're encoded.
I generally write .avs files in there and I run .bat from there.
Those storages are part of an AVID Nexis system.
The problem I'm facing has to do with the bandwidth and with the write failures. You see, from time to time, the system can delay a write or can even fail to write and enter for a very brief time (ms, really) in "protection" which means that it's in "read only mode" if it detects that there are too many operations on the disks. Of course all the AVID-Infrastructure software are well aware of this and can deal with it just fine, but this isn't the same for Avisynth, x264, x265, avs2yuv and FFMpeg...
In the very recent days, I had to run some pretty long jobs which involve QTGMC, MVTools and other filters which sadly run at about 0.6fps-4fps on a 28c/56th Xeon...
Those jobs take a very long time to complete, especially for files which last 3 hours or so and I leave them encoding for hours and hours. This morning, just like the other morning, I came back to the workstation only to find out that the jobs were stuck due to one of those connection errors occurred when I wasn't there...
Of course I can't do those things locally...
So, the question is: are you experiencing the same behavior? And if you do, is there a way to prevent my encodes to hang there stuck and not progressing when there's a connection error?
it's me again.
I have several SMB Share with several TB in which masterfiles are stored temporarily before they're encoded.
I generally write .avs files in there and I run .bat from there.
Those storages are part of an AVID Nexis system.
The problem I'm facing has to do with the bandwidth and with the write failures. You see, from time to time, the system can delay a write or can even fail to write and enter for a very brief time (ms, really) in "protection" which means that it's in "read only mode" if it detects that there are too many operations on the disks. Of course all the AVID-Infrastructure software are well aware of this and can deal with it just fine, but this isn't the same for Avisynth, x264, x265, avs2yuv and FFMpeg...
In the very recent days, I had to run some pretty long jobs which involve QTGMC, MVTools and other filters which sadly run at about 0.6fps-4fps on a 28c/56th Xeon...
Those jobs take a very long time to complete, especially for files which last 3 hours or so and I leave them encoding for hours and hours. This morning, just like the other morning, I came back to the workstation only to find out that the jobs were stuck due to one of those connection errors occurred when I wasn't there...
Of course I can't do those things locally...
So, the question is: are you experiencing the same behavior? And if you do, is there a way to prevent my encodes to hang there stuck and not progressing when there's a connection error?