this post was submitted on 19 Sep 2024
727 points (97.8% liked)

196

16484 readers
1668 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 14 points 1 month ago (1 children)

Fully agree, but the way it's worded makes it seem like log being a text file is the issue. Maybe I'm just misinterpreting intent though.

[–] [email protected] 24 points 1 month ago (2 children)

200GB of a text log file IS weird. It's one thing if you had a core dump or other huge info dump, which, granted, shouldn't be generated on their own, but at least they have a reason for being big. 200GB of plain text logs is just silly

[–] xantoxis 8 points 1 month ago (1 children)

no, 200gb of plain text logs is clearly a bug. I run a homelab with 20+ apps in it and all the logs together wouldn't add up to that for years, even without log rotation. I don't understand the poster's decision to blame this on "western game devs" when it's just a bug by whoever created the engine.

[–] [email protected] 5 points 1 month ago

Agreed, and there's a good chance that log is full of one thing spamming over and over, and the devs would love to know what it is.

[–] [email protected] 1 points 1 month ago

It could be a matter of storing non-text information in an uncompressed text format. Kind of like how all files are base 0s and 1s in assembly, other files could be "logged" as massive text versions instead of their original compressed file type.