From: Marton Balint <cus@passwd.hu> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] aviobuf: Avoid clearing the whole buffer in fill_buffer Date: Fri, 24 Mar 2023 22:35:02 +0100 (CET) Message-ID: <3a3dd093-eb11-f21-9d79-e4882eb59b6@passwd.hu> (raw) In-Reply-To: <10da54aa-8e62-d650-b49e-86f5dc87e8f7@martin.st> On Fri, 24 Mar 2023, Martin Storsjö wrote: > On Fri, 24 Mar 2023, Marton Balint wrote: > >> I am uneasy about complicating an already complicated and hard-to-follow >> AVIO layer with heuristics which activate on magic behaviour. And we all >> know how long temporary solutions last :) >> >> I guess we could add some new parameter to AVIOContext end enable this >> data-shifting behaviour explicitly when you reconfigure the buffer size >> for index in the MOV demuxer. But is it worth it? How significant is the >> "improvement" this patch provides over the previous one in the series? > > With the 2.6 GB, 40 minute mov file I'm looking at, originally, due to the > issue fixed in patch 1/2, the buffer size was never increased from the > original 32 KB, so when reading the file linearly, we would do many tens of > thousands of seek requests, giving absolutely abysmal performance. (I saw a > server side log number saying 120 000 requests.) > > With patch 1/2 applied, while reading the bulk of the file, it does ~170 > seeks. So nothing terrible, but it still feels unnecessarily inefficient to > do >4 seeks per minute due to the fact that the aviobuf layer is throwing > away good data that it already had buffered. > > In this case, it used a buffer size of 16 MB, and calculating 2.6 GB / 16 MB > ends up very near 170. So every time the 16 MB aviobuf buffer gets full and > aviobuf clears it, we end up doing a seek backwards. Thanks for the details. Patch/1 already made the significant improvement, so yeah, I am not sure about Patch/2 knowing it is not the "right" way. Regards, Marton > > With patch 2/2 applied, we no longer do any seeks while reading the bulk of > the file (at the start/end of the file there are still a bunch of scattered > seeks though). > > // Martin > > _______________________________________________ > 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:[~2023-03-24 21:35 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-21 12:37 [FFmpeg-devel] [PATCH 1/2] libavformat: Improve ff_configure_buffers_for_index for excessive deltas Martin Storsjö 2023-03-21 12:37 ` [FFmpeg-devel] [PATCH 2/2] aviobuf: Avoid clearing the whole buffer in fill_buffer Martin Storsjö 2023-03-21 19:29 ` Marton Balint 2023-03-21 20:24 ` Martin Storsjö 2023-03-24 11:11 ` Anton Khirnov 2023-03-24 11:25 ` Martin Storsjö 2023-03-24 11:55 ` Anton Khirnov 2023-03-24 20:45 ` Marton Balint 2023-03-24 21:05 ` Martin Storsjö 2023-03-24 21:35 ` Marton Balint [this message] 2023-03-24 21:41 ` Martin Storsjö 2023-03-24 21:49 ` [FFmpeg-devel] [PATCH 1/2] libavformat: Improve ff_configure_buffers_for_index for excessive deltas Marton Balint 2023-03-25 0:37 ` Michael Niedermayer 2023-03-25 22:17 ` Martin Storsjö
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=3a3dd093-eb11-f21-9d79-e4882eb59b6@passwd.hu \ --to=cus@passwd.hu \ --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