Re: [FFmpeg-devel] Issue - Error Due to higher number of threads

[Srihari Sridhar <gshari9918@gmail.com>]

Hi,

I tried on AMD ThreadRipper 3990x machine. It has 64 cores and 128 logical
processors. The windows make starts failing with 64 threads.It worked
successfully until 32 and even 48 threads.

Regards,
S Srihari

On Thu, 19 May 2022 at 15:42, Wolfgang Haupt <haupt.wolfgang@gmail.com>
wrote:

> > Hi,
> >
> > Thanks for the reply. I checked the memory usage while building ffmpeg
> with
> > 64 threads. The machine I tested has 128 GB ram. While I tested it I
> found
> > that maximum memory utilized by the build of ffmpeg was 17GB.  Still the
> > build throws up error semaphore or child process wait (Error 87 : The
> > parameter is incorrect). Hence could you check on the same please. I have
> > attached screenshots of memory utilized from the task manager.
>
> What CPU are you on?
> There is some complexity regarding the amount of threads and
> process groups on windows, see:
>
> https://www.windowscentral.com/windows-10-pro-cant-handle-amd-threadripper-3990xs-128-threads
>
> Do you even have a processor that will utilize 64 cores?
> I recommend trying with smaller values and see where "windows make"
> starts to fail.
>
> >
> > Regards,
> > S Srihari
> >
> > On Thu, 12 May 2022 at 16:45, Timo Rothenpieler <timo@rothenpieler.org>
> > wrote:
> >
> >> On 12.05.2022 04:22, Srihari Sridhar wrote:
> >>> Hi,
> >>>
> >>> I was building ffmpeg through windows. While I was able to successfully
> >>> able to build for smaller number of threads, for larger number of
> >> threads I
> >>> faced an issue
> >>>
> >>> The commands I used were
> >>> bash ./configure --arch=x86 --target-os=mingw32 --disable-x86asm
> >>> make -j <no_of_Threads>
> >>>
> >>> While building with 4 Threads the build was successful
> >>> Screenshot:
> >>> [image: image.png]
> >>>
> >>> While building with 64 threads, I faced the following error,
> >>> Screenshot :
> >>> [image: image.png]
> >>>    semaphore or child process wait (Error 87 : The parameter is
> incorrect)
> >> Please don't use images for plain text. It's hard to access and barely
> >> legible.
> >>
> >>> Please could you check this issue. Thanks
> >> You probably just ran out of RAM or something. Highly unlikely that this
> >> is an issue with ffmpeg.
> >> _______________________________________________
> >> ffmpeg-devel mailing list
> >> ffmpeg-devel@ffmpeg.org
> >> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> >>
> >> To unsubscribe, visit link above, or email
> >> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
> >>
> >>
> >> _______________________________________________
> >> ffmpeg-devel mailing list
> >> ffmpeg-devel@ffmpeg.org
> >> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> >>
> >> To unsubscribe, visit link above, or email
> >> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".