From: "Rémi Denis-Courmont" <remi@remlab.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v4 2/2][GSoC 2024] tests/checkasm: Add check_vvc_sad to vvc_mc.c Date: Tue, 21 May 2024 11:47:31 +0300 Message-ID: <A946210B-3052-4A88-B957-6F98C134EAB6@remlab.net> (raw) In-Reply-To: <fa5596e4-51e4-a77c-1971-87f193f3f84@martin.st> Le 21 mai 2024 09:37:18 GMT+03:00, "Martin Storsjö" <martin@martin.st> a écrit : >On Tue, 21 May 2024, Rémi Denis-Courmont wrote: > >> Hi, >> >> Le 20 mai 2024 03:42:03 GMT+03:00, Stone Chen <chen.stonechen@gmail.com> a écrit : >>> Adds checkasm for DMVR SAD AVX2 implementation. >>> >>> Benchmarks ( AMD 7940HS ) >>> vvc_sad_8x8_c: 70.0 >>> vvc_sad_8x8_avx2: 10.0 >>> vvc_sad_16x16_c: 280.0 >>> vvc_sad_16x16_avx2: 20.0 >>> vvc_sad_32x32_c: 1020.0 >>> vvc_sad_32x32_avx2: 70.0 >>> vvc_sad_64x64_c: 3560.0 >>> vvc_sad_64x64_avx2: 270.0 >>> vvc_sad_128x128_c: 13760.0 >>> vvc_sad_128x128_avx2: 1070.0 >>> --- >>> tests/checkasm/vvc_mc.c | 38 ++++++++++++++++++++++++++++++++++++++ >>> 1 file changed, 38 insertions(+) >> >> VVC benchmarks have increased checksam runtime by at least an order of magnitude. It's become so prohibitively slow that I could not even get to the end. >> >> This is not an acceptable situation and impedes non-VVC assembler work > >I don't quite understand; whenever benchmarking anything in checkasm, I would always run e.g. "checkasm --test=ac3dsp --bench=ac3_sum_square_bufferfly_float", limiting the total running of tests to a specific module, and only benchmarking a subset of the run functions. (The --bench parameter specifies a prefix; only functions matching that prefix gets benchmarked.) Sure that's how you do it when you're working on a specific new optimisation. Now we're trying to compare 128-bit and 256-bit vectors for *all* existing functions to see which ones need to be reworked. That used to work (in 30 minutes on K230, 5 minutes on Zen 2, IIRC). Now it's effectively broken and that's not acceptable' > >Without limiting the scope with a --test parameter, checkasm benchmarking has always been prohibitively slow for me - so I don't think there's anything new here? As said, it seems to be literally an order of magnitude slower than before if not worse. >That said I'm not familiar with the VVC tests in checkasm, perhaps they benchmark things excessively. But I don't see how that would impede work on other DSP functions in any way? James also complained about the same thing before I. _______________________________________________ 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".
next prev parent reply other threads:[~2024-05-21 8:47 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-20 0:42 [FFmpeg-devel] [PATCH v4 1/2][GSoC 2024] libavcodec/x86/vvc: Add AVX2 DMVR SAD functions for VVC Stone Chen 2024-05-20 0:42 ` [FFmpeg-devel] [PATCH v4 2/2][GSoC 2024] tests/checkasm: Add check_vvc_sad to vvc_mc.c Stone Chen 2024-05-21 5:12 ` Rémi Denis-Courmont 2024-05-21 6:37 ` Martin Storsjö 2024-05-21 8:47 ` Rémi Denis-Courmont [this message] 2024-05-21 10:12 ` Martin Storsjö 2024-05-21 14:35 ` Ronald S. Bultje 2024-05-20 11:23 ` [FFmpeg-devel] [PATCH v4 1/2][GSoC 2024] libavcodec/x86/vvc: Add AVX2 DMVR SAD functions for VVC Ronald S. Bultje 2024-05-20 15:52 ` Ronald S. Bultje 2024-05-22 0:05 ` Stone Chen -- strict thread matches above, loose matches on Subject: below -- 2024-05-20 0:37 Stone Chen 2024-05-20 0:37 ` [FFmpeg-devel] [PATCH v4 2/2][GSoC 2024] tests/checkasm: Add check_vvc_sad to vvc_mc.c Stone Chen
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=A946210B-3052-4A88-B957-6F98C134EAB6@remlab.net \ --to=remi@remlab.net \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git