From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/3] lavc/speedhqdec: Add AV_CODEC_CAP_FRAME_THREADS
Date: Wed, 8 May 2024 09:46:19 -0300
Message-ID: <44cd0cf1-f3ac-402e-9d17-87f1416df823@gmail.com> (raw)
In-Reply-To: <5c0eea5911c9db73182395f873af8e86653ac765.camel@haerdin.se>
On 5/8/2024 9:42 AM, Tomas Härdin wrote:
> Hi
>
> On a 36-core machine (Intel(R) Xeon(R) Platinum 8124M CPU @ 3.00GHz)
> with a 7 minute 125 Mbit/s 1080p sample and -thread_type frame -threads
> 36 this brings CPU utilization from 117% to 3174%, 58x realtime
>
> Without -threads 36 the utilization is only 1601% due to it being 16 by
> default..
Does this default make sense anymore? I think it was added for h264, but
maybe it should be decoder dependent.
>
> /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".
_______________________________________________
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-08 12:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 12:42 Tomas Härdin
2024-05-08 12:42 ` [FFmpeg-devel] [PATCH 2/3] lavc/speedhqdec: Obey AVDISCARD_ALL Tomas Härdin
2024-05-08 12:43 ` [FFmpeg-devel] [PATCH 3/3] lavc/speedhqdec: Set AV_PICTURE_TYPE_I Tomas Härdin
2024-05-08 20:01 ` Marton Balint
2024-05-08 20:06 ` James Almer
2024-05-10 12:31 ` Tomas Härdin
2024-05-10 12:48 ` Andreas Rheinhardt
2024-05-11 23:07 ` Tomas Härdin
2024-05-13 6:57 ` Tomas Härdin
2024-05-08 12:46 ` James Almer [this message]
2024-05-08 12:48 ` [FFmpeg-devel] [PATCH 1/3] lavc/speedhqdec: Add AV_CODEC_CAP_FRAME_THREADS Tomas Härdin
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=44cd0cf1-f3ac-402e-9d17-87f1416df823@gmail.com \
--to=jamrial@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