From: Davy Durham <ddurham@davyandbeth.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] ffmpeg appears to be wasting CPU time
Date: Fri, 7 Apr 2023 15:26:40 -0500
Message-ID: <64a08e5f-d3cb-825d-ff3c-165448e80020@davyandbeth.com> (raw)
In-Reply-To: <CAK+ULv7=YMZBS3LnKf6Rra5jEM-fQUP95vY_iUzNcdLmshoBUA@mail.gmail.com>
Ah, you appear to be correct. I learned about cpufreq and adjusted it
to not scale and the problem also disappears then too. I had not even
considered that. Thank you
On 4/7/23 11:15, Kieran Kunhya wrote:
> On Fri, 7 Apr 2023 at 05:03, Davy Durham <ddurham@davyandbeth.com> wrote:
>
>> After furiously digging through the ffmpeg code (particularly in older
>> versions that also exhibit the problem, but where the code is simpler) I
>> have found no reason for there to be wasted CPU time.
>>
>> In my travels, I frustratingly noticed that sometime the problem would
>> mysteriously vanish. And, long story short, I believe I've been chasing
>> a phantom. If, on my local machine w/ 8 cores, I start a process that
>> simply spins one CPU, the problem vanishes--that is, now whether running
>> ffmpeg at full speed or with a read rate limit, the cumulative CPU
>> reported by 'time' is nearly** the same, as one would expect it to be.
>>
> Are you sure this isn't just your CPU governor and/or the effects of
> frequency scaling/C-states?
>
> Kieran
> _______________________________________________
> 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".
prev parent reply other threads:[~2023-04-07 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 8:20 Davy Durham
2023-04-07 4:03 ` Davy Durham
2023-04-07 16:15 ` Kieran Kunhya
2023-04-07 20:26 ` Davy Durham [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=64a08e5f-d3cb-825d-ff3c-165448e80020@davyandbeth.com \
--to=ddurham@davyandbeth.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