BoycottSystemd.org bashes systemd for its journal files in a "complicated binary format", it being "anti Unix",
Concluston? Binary formats are not evil. It's matter of tools to transparently access them. E.g. you can pipe compressed log to other tools and they will handle it. If systemd would permit same thing, it is not anyhow worse of gzipped logs, isn't it? And then binary format can allow efficient indexing. Let's assume we have 10 gigz of logs. Now I'm interested what IP 10.10.10.10 did on my system. Classic *nix solution assumes parsing whole 10 gigz and then discarding all entries not matching criteria. Needless to say it is not efficient at all and stinks when it comes to dealing with large log files. OTOH binary format can offer index, so I can quickly get idea what mentioned IP did without reading whole 10 gigz by only looking matching records as long as there is proper index built. Not to mention IPv4 takes 4 bytes to store as binary but up to 15 bytes as text. That is it - almost 4 times larger than it could be. So when it comes to dealing with large logs from busy servers, Lennart getting some point, huh?
Comment