Question on cores*3/2 formula

[LoRd_MuldeR]

Can you provide an insane setting slow enough to makes b-adapt 2 using 100% CPU on my Dual Core? If there is not, you cannot prove your logic.

I don't need to prove anything! That's because I never claimed that you can get 100% load on your CPU with "--b-adapt 2" during the first pass.

In fact I explained to you why the opposite is the case! And still you are not willing to understand the obvious...


This thread has become useless, because the same questions that have been answered already are asked over and over again :rolleyes:

[Dark Shikari]

Can you provide an insane setting slow enough to make b-adapt 2 using 100% CPU on my Dual Core? If there is not, you cannot prove your logic.--me tesa --merange 64 --ref 16 :rolleyes:

[Fishman0919]

Can you provide an insane setting slow enough to make b-adapt 2 using 100% CPU on my Dual Core? If there is not, you cannot prove your logic.




--pass 1 --bitrate 3750 --stats "d:\temp\job1.stats" --level 4.0 --sar 1:1 --aud --vbv-bufsize 20000 --vbv-maxrate 20000 --filter 0,0 --ref 3 --mixed-refs --bframes 3 --b-pyramid --aq-mode 2 --aq-strength 1.0 --direct auto --b-adapt 2 --keyint 24 --min-keyint 2 --subme 9 --trellis 2 --partitions all --8x8dct --me tesa --merange 64 --no-fast-pskip --threads auto --thread-input --progress --no-psnr --no-ssim --output "d:\temp\video.264"

--pass 2 --bitrate 3750 --stats "d:\temp\job1.stats" --level 4.0 --sar 1:1 --aud --vbv-bufsize 20000 --vbv-maxrate 20000 --filter 0,0 --ref 3 --mixed-refs --bframes 3 --b-pyramid --aq-mode 2 --aq-strength 1.0 --keyint 24 --min-keyint 2 --weightb --direct auto --subme 9 --trellis 2 --partitions all --8x8dct --me tesa --merange 64 --no-fast-pskip --threads auto --thread-input --progress --no-psnr --no-ssim --output "d:\temp\video.264"

Seems to peg my Dual and Quad core at 100% cpu all the time with r1046

[roozhou]

--pass 1 --bitrate 3750 --stats "C:\temp\job1.stats" --level 4.0 --sar 1:1 --aud --vbv-bufsize 20000 --vbv-maxrate 20000 --filter 0,0 --ref 3 --mixed-refs --bframes 3 --b-pyramid --aq-mode 2 --aq-strength 1.0 --direct auto --b-adapt 2 --keyint 24 --min-keyint 2 --subme 9 --trellis 2 --partitions all --8x8dct --me tesa --merange 64 --no-fast-pskip --threads auto --thread-input --progress --no-psnr --no-ssim --output "D:\temp\video.264"

--pass 2 --bitrate 3750 --stats "C:\temp\job1.stats" --level 4.0 --sar 1:1 --aud --vbv-bufsize 20000 --vbv-maxrate 20000 --filter 0,0 --ref 3 --mixed-refs --bframes 3 --b-pyramid --aq-mode 2 --aq-strength 1.0 --keyint 24 --min-keyint 2 --weightb --direct auto --subme 9 --trellis 2 --partitions all --8x8dct --me tesa --merange 64 --no-fast-pskip --threads auto --thread-input --progress --no-psnr --no-ssim --output "D:\temp\video.264"

Seems to peg my Dual and Quad core at 100% cpu all the time with r1046

Thanks. It works but giving me ~0.2fps on 1080P.

[LoRd_MuldeR]

--me tesa --merange 64

Thanks. It works but giving me ~0.2fps on 1080P.

What a surprise :D

[Fishman0919]

Thanks. It works but giving me ~0.2fps on 1080P.

No one said it was going to be fast. :rolleyes:


"C:\x264\x264.exe" "C:\temp\Movie.avs" --pass 1 --bitrate 3750 --stats "C:\temp\Movie.stats" --level 4.0 --sar 1:1 --aud --vbv-bufsize 16500 --vbv-maxrate 17500 --filter 0,0 --ref 3 --mixed-refs --bframes 3 --b-pyramid --aq-mode 2 --aq-strength 1.0 --direct auto --b-adapt 1 --keyint 24 --min-keyint 2 --subme 3 --trellis 2 --partitions all --me hex --no-fast-pskip --threads auto --thread-input --progress --no-psnr --no-ssim --output "C:\temp\video.264"

"C:\x264\x264.exe" "C:\temp\Movie.avs" --pass 2 --bitrate 3750 --stats "C:\temp\Movie.stats" --level 4.0 --sar 1:1 --aud --vbv-bufsize 16500 --vbv-maxrate 17500 --filter 0,0 --ref 3 --mixed-refs --bframes 3 --b-pyramid --aq-mode 2 --aq-strength 1.0 --keyint 24 --min-keyint 2 --weightb --direct auto --subme 7 --trellis 2 --partitions all --8x8dct --me umh --merange 24 --no-fast-pskip --threads auto --thread-input --progress --no-psnr --no-ssim --output "C:\temp\video.264"

Still pegs both my Dual and Quad core

[Sagekilla]

@roozhou: 100% CPU usage does not imply fast encoding. You can completely max out x264 using --me tesa --merange 512 --subme 9 --ref 16 --b-adapt 2 --bframes 16 and it'll spit out 0.1 fps @ 100% CPU.

Likewise, you can use settings so fast that you'll get 100 fps but only 50% CPU usage because of a decoding bottleneck.

100% CPU != Fast encode!

[kemuri-_9]

It's come to be obvious that he's look for the 'efficient' encode:
that is that everything is in a perfectly ideal situation,
where there's no particular bottleneck in any one part of the encode to slow the overall rate down.

obviously complaining that --b-adapt 2 is a bottleneck on non super extreme settings.

On those super extreme settings things are more balanced and can actually use 100% cpu with 1:1 cpu:thread ratio.

This is not the case when you back down from those settings to more sane ones though, and that's where the problem lies.

and from what Dark Shikari & akupenguin have said,
to fix --b-adapt 2 to fit more into the ideal situation, the code rewrite would be fairly non trivial.

so obviously, solutions to the situation are
A. don't use --b-adapt 2
B. help fix it
C. shut up and wait for it to get fixed

</annoyed rant>

[roozhou]

@roozhou: 100% CPU usage does not imply fast encoding. You can completely max out x264 using --me tesa --merange 512 --subme 9 --ref 16 --b-adapt 2 --bframes 16 and it'll spit out 0.1 fps @ 100% CPU.

Likewise, you can use settings so fast that you'll get 100 fps but only 50% CPU usage because of a decoding bottleneck.

100% CPU != Fast encode!

You don't have to tell me such things that everyone here has already known.

Actually i was pointing out how slow b-adapt 2 is.

On my Duo Core.

--crf 24 --ref 3 --mixed-refs --bframes 3 --b-pyramid --keyint 240 --min-keyint 6 --weightb --direct auto --subme 8 --trellis 2 --partitions all --8x8dct --me umh --merange 24 --no-fast-pskip --threads 4 --thread-input --progress --no-psnr --no-ssim -o NUL --b-adapt 2

gives me 1.55fps and 100% CPU load.


--crf 24 --ref 3 --mixed-refs --bframes 3 --b-pyramid --keyint 240 --min-keyint 6 --weightb --direct auto --subme 8 --trellis 2 --partitions all --8x8dct --me umh --merange 24 --no-fast-pskip --threads 3 --thread-input --progress --no-psnr --no-ssim -o NUL --b-adapt 2

gives me 1.38fps and 85%~90% CPU load.

It proves 3*cores/2 threads wrong and "threads auto" should be more intellegient.

[nurbs]

You don't have to tell me such things that everyone here has already known.

Actually i was pointing out how slow b-adapt 2 is.

Which also falls under "such things that everyone here has already known" :)

[Shinigami-Sama]

You don't have to tell me such things that everyone here has already known.

Actually i was pointing out how slow b-adapt 2 is.


pot meet kettle?

but I do agree threads auto could use a little more brains but a quick trip to #x264 will set people straight...

[Sagekilla]

1.5 * cores is just a roundabout "One size fits most." ANY time you want optimal speed or quality you should tweak your settings to your source and to your hardware. This can be time consuming so it's easier to use an automatic detection that will work for 99% of all cases. Not all CPUs are the same, so some may do better with 3 threads and others may do better with 2 or 4 threads. The devil is in the details..