Optimise Tournament Bracket file sizes / Remove unneeded values from json objects for tournaments. #18681
-
This has become a bit of an issue, espcially with Round of 128 tournaments where you would replicate the bracket to share across to multiple streamers for the lazer client. On smaller scales, a Round of 32 tournament (single elimination) can go upwards of 7-8mb towards grand finals, making sharing across discord (to share to other streamers) a bit more cumbersome to handle having to zip up a json file. The main issue with the storage of the bracket.json file is the bloat of the APIUser and APIBeatmap values where every single value is included and not just the Title, ID, Difficulty, Image, any anything else used for the tournament client. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Would add onto this by saying that these extra APIUser and APIBeatmap values could be stored separately to still keep these values and still reducing the file size of the bracket file. |
Beta Was this translation helpful? Give feedback.
-
I'm not against this being done. It shouldn't be a very hard one to improve if someone feels like stepping up to make the changes. |
Beta Was this translation helpful? Give feedback.
-
Should be improved magnificently starting with #18750. |
Beta Was this translation helpful? Give feedback.
Should be improved magnificently starting with #18750.