From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/hls: reduce default max reload to 100
Date: Fri, 12 May 2023 00:45:33 +0200
Message-ID: <20230511224533.GC1391451@pb2> (raw)
In-Reply-To: <CAPYw7P5XPu46DxGM8tjXLw9EAku4B5_ohUk23Kjr=7KEUW61cg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1221 bytes --]
On Thu, May 11, 2023 at 07:36:04PM +0200, Paul B Mahol wrote:
> On Wed, May 10, 2023 at 11:58 PM Michael Niedermayer <michael@niedermayer.cc>
> wrote:
>
> > The 1000 did result in a apparent never ending reload loop
> >
> >
> How so? Somewhere overflow happens causing infinity?
no, it was lack of patience
each reload before the patches takes 50seconds with the testcase
thats with one url which returns 55 bytes
i didnt benchmark it but i would expect 1000 reloads to take
about 14 hours
after the bugfix it should be a bit less than 2 hours
and with just 100 reloads its maybe 10minutes
Why is the reload taking so long ?
The RFC says this:
"If the client reloads a Playlist file and finds that it has not
changed, then it MUST wait for a period of one-half the target
duration before retrying."
Given that i think a default of 100 is actually still too much
and something like 3 is better, so i will locally change the default
to 3
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Complexity theory is the science of finding the exact solution to an
approximation. Benchmarking OTOH is finding an approximation of the exact
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-05-11 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 21:58 [FFmpeg-devel] [PATCH 1/2] avformat/format: Stop reading data at EOF during probing Michael Niedermayer
2023-05-10 21:58 ` [FFmpeg-devel] [PATCH 2/2] avformat/hls: reduce default max reload to 100 Michael Niedermayer
2023-05-11 17:36 ` Paul B Mahol
2023-05-11 22:45 ` Michael Niedermayer [this message]
2023-09-16 17:35 ` [FFmpeg-devel] [PATCH 1/2] avformat/format: Stop reading data at EOF during probing Michael Niedermayer
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=20230511224533.GC1391451@pb2 \
--to=michael@niedermayer.cc \
--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