From: "Tomas Härdin" <tjoppen@acc.umu.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 01/13] lavc/jpeg2000dec: Finer granularity threading
Date: Fri, 24 Jun 2022 10:19:46 +0200
Message-ID: <b821b8f98d1b1a5e4b91b30e89f0f6a9325de976.camel@acc.umu.se> (raw)
In-Reply-To: <165556380125.13099.10440228465158079139@lain>
lör 2022-06-18 klockan 16:50 +0200 skrev Anton Khirnov:
> Quoting Tomas Härdin (2022-06-14 16:39:00)
> > Patch 12 in this series is optional since it's just me getting the
> > speed up on a specific machine
> >
> > /Tomas
> >
> > From 115aa26c343419e81c1b5ba0bfdb1615cbec27e9 Mon Sep 17 00:00:00
> > 2001
> > From: =?UTF-8?q?Tomas=20H=C3=A4rdin?= <git@haerdin.se>
> > Date: Fri, 10 Jun 2022 14:10:02 +0200
> > Subject: [PATCH 01/13] lavc/jpeg2000dec: Finer granularity
> > threading
> >
> > Decoding and dequant is now threaded on codeblock level.
> > IDWT is threaded on component level.
> > MCT and write_frame() remain threaded on tile level.
> >
> > This brings lossless 4K J2K with -lowres 2 -thread_type slice -
> > threads 96 on an AMD EPYC 7R32 from 4.8 fps (177% CPU) to 31 fps
> > (1284% CPU).
>
> Any measurable impact on single-threaded or frame-threaded decoding?
>
median of 11 runs with -threads 1 -vframes 100 on a 4K file
before: real 0m38,664s
after: real 0m39,139s
I have in mind to try and roll together the last step in the IDWT code
with the av_clip() in write_frame() which should improve run time in
all cases.
/Tomas
_______________________________________________
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".
prev parent reply other threads:[~2022-06-24 8:19 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 14:39 Tomas Härdin
2022-06-14 14:39 ` [FFmpeg-devel] [PATCH 02/13] lavc/jpeg2000dec: Reindent Tomas Härdin
2022-06-14 14:40 ` [FFmpeg-devel] [PATCH 03/13] lavc/jpeg2000dwt: Implement sliced transforms Tomas Härdin
2022-06-14 14:40 ` [FFmpeg-devel] [PATCH 04/13] lavc/jpeg2000dec: Implement IDWT slicing Tomas Härdin
2022-06-14 14:41 ` [FFmpeg-devel] [PATCH 05/13] lavc/jpeg2000dec: Thread init_tile() Tomas Härdin
2022-06-14 21:11 ` Michael Niedermayer
2022-06-15 13:11 ` Tomas Härdin
2022-06-15 21:05 ` Michael Niedermayer
2022-06-16 9:28 ` Tomas Härdin
2022-06-14 14:42 ` [FFmpeg-devel] [PATCH 06/13] lavu/mem: Add ff_fast_recalloc() Tomas Härdin
2022-06-14 20:26 ` Michael Niedermayer
2022-06-15 9:59 ` Tomas Härdin
2022-06-15 12:15 ` James Almer
2022-06-16 12:44 ` Tomas Härdin
2022-06-18 14:57 ` Anton Khirnov
2022-06-21 8:04 ` Tomas Härdin
2022-06-14 14:42 ` [FFmpeg-devel] [PATCH 07/13] lavc/jpeg2000*: Use ff_fast_recalloc() to eliminate lots of allocations Tomas Härdin
2022-06-14 15:23 ` Andreas Rheinhardt
2022-06-15 10:03 ` Tomas Härdin
2022-06-14 14:43 ` [FFmpeg-devel] [PATCH 08/13] lavc/jpeg2000: Switch Jpeg2000TgtNode to int32_t parent Tomas Härdin
2022-06-14 14:43 ` [FFmpeg-devel] [PATCH 09/13] lavc/jpeg2000: Speed up ff_jpeg2000_tag_tree_init() using stereotypes for sizes <= 4x4 Tomas Härdin
2022-06-18 15:00 ` Anton Khirnov
2022-06-21 7:57 ` Tomas Härdin
2022-06-14 14:43 ` [FFmpeg-devel] [PATCH 10/13] lavc/jpeg2000: Reindent Tomas Härdin
2022-06-14 14:44 ` [FFmpeg-devel] [PATCH 11/13] lavc/jpeg2000: Minimize calls to av_codec_is_encoder() Tomas Härdin
2022-06-14 15:04 ` Andreas Rheinhardt
2022-06-15 10:20 ` Tomas Härdin
2022-06-14 14:44 ` [FFmpeg-devel] [PATCH 12/13] lavc/jpeg2000dec: Use coarser slicing for initial reslevels Tomas Härdin
2022-06-14 14:47 ` [FFmpeg-devel] [PATCH 13/13] lavc/jpeg2000dec: Component-level threading of write_frame() Tomas Härdin
2022-06-18 14:50 ` [FFmpeg-devel] [PATCH 01/13] lavc/jpeg2000dec: Finer granularity threading Anton Khirnov
2022-06-24 8:19 ` Tomas Härdin [this message]
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=b821b8f98d1b1a5e4b91b30e89f0f6a9325de976.camel@acc.umu.se \
--to=tjoppen@acc.umu.se \
--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