From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFV1 slicecrc: "hashxx" instead of "CRC" for speed?
Date: Wed, 26 Oct 2022 09:58:17 +0200
Message-ID: <CAPYw7P507mBnmdLL-hE-_WBjC-xH6OOTi7dRng88mP_f1ZS2rw@mail.gmail.com> (raw)
In-Reply-To: <CAK+ULv5wP7uX4M2HUoo0z=C3C8gk83pE3WVwv-HZ+gGOm0yMFw@mail.gmail.com>
On 10/26/22, Kieran Kunhya <kierank@obe.tv> wrote:
> On Tue, 25 Oct 2022, 21:32 Peter B., <pb@das-werkstatt.com> wrote:
>
>> Hi everyone :)
>>
>> Would it possibly have a significant impact on coding speed of FFV1's
>> slicecrc option (Where a CRC is calculated for each frame slice), to use
>> a faster algorithm instead (if one exists)?
>> I'm wondering if, for example something like "xxHash" may warrant a try?
>> (Haven't found CRC vs xxHash benchmarks yet, but I'm still looking)
>>
>> Anyhow,
>> Thanks for any of your time :D
>
>
> I haven't benchmarked the overhead of the CRC in FFv1 vs the encode or
> decode process.
> But FFmpeg's CRC could be optimised using multiple unrolled tables or SIMD
> or other approaches.
It is already using multiple tables.
>
> Regards,
> Kieran Kunhya
> _______________________________________________
> 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".
next prev parent reply other threads:[~2022-10-26 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 20:31 Peter B.
2022-10-25 20:37 ` Andreas Rheinhardt
2022-10-26 7:25 ` Kieran Kunhya
2022-10-26 7:58 ` Paul B Mahol [this message]
2022-10-26 19:13 ` Michael Niedermayer
2022-11-03 13:01 ` Leo Izen
2022-11-03 13:19 ` Nicolas George
2022-11-03 15:07 ` Leo Izen
2022-11-08 8:17 ` Peter B.
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=CAPYw7P507mBnmdLL-hE-_WBjC-xH6OOTi7dRng88mP_f1ZS2rw@mail.gmail.com \
--to=onemda@gmail.com \
--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