[FFmpeg-devel] [RFC] statictrac, trac and caching
Michael Niedermayer
michael at niedermayer.cc
Sun Jun 15 19:53:30 EEST 2025
Hi Marth64
On Sun, Jun 15, 2025 at 11:06:47AM -0500, Marth64 wrote:
> On Sun, Jun 15, 2025 at 10:57 AM Kacper Michajlow
> <kasper93-at-gmail.com at ffmpeg.org> wrote:
> > Maybe it's time to retire the trac? It is quite slow by design and not
> > really actively maintained anymore. Holding onto legacy software
> > always increases the burden of maintainability.
>
> I do feel that a good portion of wiki technical documentation can
> probably be moved to the main docs.
The wiki has the huge advantage that people can edit it easily
Editing the docs people have to do a git checkout, edit a file
with an editor, make a git commit read patch submission rules
submit a patch to ML or forge.
Thats alot stumbling blocks thrown in ones way
> There are some good examples and information there that seem to me can
> be crystallized into plain old texi.
> While I'm neutral about Trac I think in a sense this could also help
> in the sense of reducing server load for this somewhat static content.
yesterdays incident had like ~40k accesses on teh same file.
So moving 99% of content out of trac would not have helped if
that file was in teh 1%
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Let us carefully observe those good qualities wherein our enemies excel us
and endeavor to excel them, by avoiding what is faulty, and imitating what
is excellent in them. -- Plutarch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20250615/d30bb1a2/attachment.sig>
More information about the ffmpeg-devel
mailing list