How long should FAF keep old replays?

MazorNoob

Yes, it will break for the new format. Someone will have to update it, somewhere around line 430 in page source. This diff should help with that.

Defiant

Oh please keep all replays. Can we throw money at buying more storage?

TheVVheelboy

Imo, no need to keep replays older than 3 years no matter what they are. If they were good they are already casted w/e.
Even then I wouldn't really keep replays older than 2 years unless they are from ranked games. It just seems pointless to keep so much when it's useless.

Eternal-

I would suggest to keep only the special old games. But I think there are no stamps like "Tournament". I also think that no one will sort their favorite replays. I guess you can just save replays of certain players, purely for memory?
But in general, I do not see any point in these replays, the game is growing up, the old tactics and methods of the game can not be applied to the current realities.
I am in favor of removing all replays since the last old patch.

And further sorting them with some parameters

Removing replays with one player
Removing replays with a sandbox
Removing of replays of the company
Removing "blacklisted" maps (gap, astro, etc)
Removing replays with desync
Removing replays after (optional) 4/8/12 months

Cascade

@ZLO I've been searching for this parser for ages! The old link on google 404s
edit: still seems to be broken for me

Eternal-

@Cascade You should try to open it with vpn. Works fine for me without vpn

PattogoTehen

Hi,
Bitbucket deleted my old mercurial repos (https://bitbucket.org/blog/sunsetting-mercurial-support-in-bitbucket).
Moved what i could save to Github.

Please update your links to: https://fafafaf.github.io/

Btw. sometime the CORS header got removed from https://content.faforever.com/faf/vault/replay_vault/replay.php hence it cant load the files directly by replay id.

Brutus5000

@PattogoTehen We changed a lot of urls, but I couldn't make a pull request against bitbucket as it was gone. I'll do one against your Github repository.

The CORS header issue is something we raised as a bug ticket in our reverse proxy, it might vanish in the near future (or already does if you use replay.faforever.com, not sure).

Zokora

I can offer to archive all replays and make them accessible to others as well. Size and traffic do not matter for my google drive.

edit: Others can make backups as well

nemir

Is it possible to create criteria by which you could keep some replays for longer... IE if it was a game with stronger players it gets kept longer... Or if it was a game with a certain number of downloads... Or 5 star reviews...

That might be a cool thing. It would be a decent way to raise the overall value of the replay library.

Brutus5000

So due to the server disk running full causing an outage we have prioritized recompressing all replays to Zstandard without base64 encoding. This reduced total replay size from 677 GB to 406 GB (-40%).
With the next server update we'll also activate the new compression for the replay server. So also the growth of new replays will be decreased by 40%.

This was actually much more than we expected.
Also we found a lot of broken replays in terms of corrupt files that need to clean up.

So as of now the server has 280 GB usable disk space free which should suffice for another 3-5 years.

Auriko

Good news

tatsu

@brutus5000 you rock!