3 ms·
You shouldn't need to choose. MySQL's InnoDB engine supports compression, and not only does it use less space on disk, it's actually faster to read and write.
by kbenson 11y ago
You shouldn't need to choose. MySQL's InnoDB engine supports compression, and not only does it use less space on disk, it's actually faster to read and write. I don't see why journald can't implement something similar.
- msandford 11y agoWhy not log them directly to a hadoop cluster while you're at it? I mean, while we're cramming everything into the low-level OS services.
- kbenson 11y agoThe deflate algorithm is well understood, well defined, available in every language, and not hard to implement. At this point, we might benefit from having it included and provided by the kernel. In fact, the kernel does have limited support for compression[1] (well, decompression only currently, it seems). Expanding upon this to allow compression as well would likely yield quite a few benefits for multiple applications. 1: https://www.kernel.org/doc/Documentation/xz.txt https://www.kernel.org/doc/Documentation/xz.txt