this post was submitted on 25 Oct 2024
9 points (100.0% liked)
AskBeehaw
2002 readers
2 users here now
An open-ended community for asking and answering various questions! Permissive of asks, AMAs, and OOTLs (out-of-the-loop) alike.
In the absence of flairs, questions requesting more thought-out answers can be marked by putting [SERIOUS] in the title.
Subcommunity of Chat
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In general, this is definitely an area where the best approach is to just find an existing tool for what you need and use that. Especially for text data, compression is a pretty well-studied field and there are plenty of public (and open-source, if that's a requirement) tools that will do a fantastic job at reducing size. Rolling your own is likely to result in significantly worse compression rates, and if you make an error your data could be irreparably destroyed which you won't know until you try to access it later.
If your data is incredibly specific you might be able to do better, but it's usually best to ignore that sort of optimization until you actually need it.