libvpx via ffmpeg on high-cpu machines
I think this one can be safe to test, if you have >16 cpu/thread machine ... https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/c13d95934327ddad4db30f6aee93...
I tried compiling by decommenting "MAX_AUTO_THREADS 16" in the "pthread_internal.h" file. My processor has 16 threads (8c/16t). The compilation stops with error. I tried decommenting the line: #define MAX_AUTO_THREADS 16 I also tried changing the default (16) to 32. I get errors in both cases. I put the link to cin5.log: https://ufile.io/hn1vfdtx [PS: compiling with only the latest patch for memory leaks works well.]
ср, 25 янв. 2023 г., 16:59 Andrea paz <[email protected]>:
I tried compiling by decommenting "MAX_AUTO_THREADS 16" in the "pthread_internal.h" file. My processor has 16 threads (8c/16t). The compilation stops with error. I tried decommenting the line:
#define MAX_AUTO_THREADS 16
I also tried changing the default (16) to 32. I get errors in both cases.
did you tried to download patch directly and apply it to ffmpeg? https://git.ffmpeg.org/gitweb/ffmpeg.git/patch/c13d95934327ddad4db30f6aee93c... (clicked on little diff link, then on another link 'patch' on next page) because it works a bit differently, by touching libvpx wrapper files in libavcodec and leaving pthread_internal unchanged .. thanks for a try, anyway .... I put the link to cin5.log:
[PS: compiling with only the latest patch for memory leaks works well.]
Sorry but I can't download the patch. Il mer 25 gen 2023, 18:06 Andrew Randrianasulu <[email protected]> ha scritto:
ср, 25 янв. 2023 г., 16:59 Andrea paz <[email protected]>:
I tried compiling by decommenting "MAX_AUTO_THREADS 16" in the "pthread_internal.h" file. My processor has 16 threads (8c/16t). The compilation stops with error. I tried decommenting the line:
#define MAX_AUTO_THREADS 16
I also tried changing the default (16) to 32. I get errors in both cases.
did you tried to download patch directly and apply it to ffmpeg?
https://git.ffmpeg.org/gitweb/ffmpeg.git/patch/c13d95934327ddad4db30f6aee93c...
(clicked on little diff link, then on another link 'patch' on next page)
because it works a bit differently, by touching libvpx wrapper files in libavcodec and leaving pthread_internal unchanged ..
thanks for a try, anyway ....
I put the link to cin5.log:
[PS: compiling with only the latest patch for memory leaks works well.]
I wget'ed it without problem. Attached renamed version ... ср, 25 янв. 2023 г., 22:18 Andrea paz <[email protected]>:
Sorry but I can't download the patch.
Il mer 25 gen 2023, 18:06 Andrew Randrianasulu <[email protected]> ha scritto:
ср, 25 янв. 2023 г., 16:59 Andrea paz <[email protected]>:
I tried compiling by decommenting "MAX_AUTO_THREADS 16" in the "pthread_internal.h" file. My processor has 16 threads (8c/16t). The compilation stops with error. I tried decommenting the line:
#define MAX_AUTO_THREADS 16
I also tried changing the default (16) to 32. I get errors in both cases.
did you tried to download patch directly and apply it to ffmpeg?
https://git.ffmpeg.org/gitweb/ffmpeg.git/patch/c13d95934327ddad4db30f6aee93c...
(clicked on little diff link, then on another link 'patch' on next page)
because it works a bit differently, by touching libvpx wrapper files in libavcodec and leaving pthread_internal unchanged ..
thanks for a try, anyway ....
I put the link to cin5.log:
[PS: compiling with only the latest patch for memory leaks works well.]
$ git am /home/patch/*.diff fatal: impossible open '/home/patch/*.diff': File or directory not exist.
On Thu, Jan 26, 2023 at 12:22 AM Andrea paz <[email protected]> wrote:
$ git am /home/patch/*.diff fatal: impossible open '/home/patch/*.diff': File or directory not exist.
Interesting to have the "impossible". I got one of these when I was using Valgrind: vex: the `impossible' happened: VEX temporary storage exhausted.
Interesting to have the "impossible". I got one of these when I was using Valgrind: vex: the `impossible' happened: VEX temporary storage exhausted.
It is my bad italian translation. The real sentence should be "no such file or directory". Instead of "git am ..." I also tried "patch -p(n) < ..." with n=0,1,2,3 and 4 but I still have errors. PS: Can you remove the word "table:" from the table caption in advanced.tex --> proxy?
participants (3)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith