From: Zhao Zhili <quinkblack@foxmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/amfenc: Fix for windows imprecise sleep Date: Tue, 17 Oct 2023 09:25:58 +0800 Message-ID: <tencent_A7D3321C428B82A62B10A8A6D1E7E5EA9706@qq.com> (raw) In-Reply-To: <2315cfb6-7fed-4429-aebd-d958471898f9@jkqxz.net> > 在 2023年10月17日,上午5:24,Mark Thompson <sw@jkqxz.net> 写道: > > On 16/10/2023 10:13, Evgeny Pavlov wrote: >> This commit reduces the sleep time on Windows to improve AMF encoding >> performance on low resolution input videos. >> This fix is for Windows only, because sleep() function isn't >> very accurate on Windows OS. >> Fix for issue #10622 >> Signed-off-by: Evgeny Pavlov <lucenticus@gmail.com> >> --- >> libavcodec/amfenc.c | 4 ++++ >> 1 file changed, 4 insertions(+) >> diff --git a/libavcodec/amfenc.c b/libavcodec/amfenc.c >> index 061859f85c..0c95465d6e 100644 >> --- a/libavcodec/amfenc.c >> +++ b/libavcodec/amfenc.c >> @@ -770,7 +770,11 @@ int ff_amf_receive_packet(AVCodecContext *avctx, AVPacket *avpkt) >> if (query_output_data_flag == 0) { >> if (res_resubmit == AMF_INPUT_FULL || ctx->delayed_drain || (ctx->eof && res_query != AMF_EOF) || (ctx->hwsurfaces_in_queue >= ctx->hwsurfaces_in_queue_max)) { >> block_and_wait = 1; >> +#ifdef _WIN32 >> + av_usleep(0); //Sleep() is not precise on Windows OS. >> +#else >> av_usleep(1000); >> +#endif >> } >> } >> } while (block_and_wait); > > Wasting lots of power by spinning on a CPU core does not seem like a good answer to this problem. (I mean, presumably that is why Windows isn't honouring your request for a short sleep, because it wants timers to have larger gaps to avoid wasting power.) If av_usleep is implemented via Sleep like current case, sleep 0 means yield current thread, so it’s not busy wait in normal case (but it can be busy wait). av_usleep(500) may looks better and do the same job by depending 500/1000 = 0. I agree use sleep without real async is like a bug. > > Why is there a sleep here at all, anyway? An API for hardware encoding should be providing a way for the caller to wait for an outstanding operation to complete. > > Thanks, > > - Mark > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email _______________________________________________ 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:[~2023-10-17 1:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-16 9:13 Evgeny Pavlov 2023-10-16 21:24 ` Mark Thompson 2023-10-17 1:25 ` Zhao Zhili [this message] 2023-10-17 17:11 ` Evgeny Pavlov 2023-10-17 19:45 ` Kacper Michajlow 2023-10-18 10:32 ` Evgeny Pavlov 2023-10-18 20:36 ` [FFmpeg-devel] [PATCH] amfenc: Use a blocking call instead of sleeping and polling Mark Thompson 2023-10-19 16:13 ` Evgeny Pavlov 2023-10-22 14:30 ` Mark Thompson 2023-11-13 14:37 ` [FFmpeg-devel] [PATCH v2] avcodec/amfenc: increase precision of Sleep() on Windows Evgeny Pavlov 2023-11-20 16:01 ` Evgeny Pavlov 2023-11-27 13:42 ` Mark Thompson 2023-11-27 14:04 ` Henrik Gramner via ffmpeg-devel 2024-02-19 15:26 ` Evgeny Pavlov
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=tencent_A7D3321C428B82A62B10A8A6D1E7E5EA9706@qq.com \ --to=quinkblack@foxmail.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