3 ms·
Their measurement isn't wrong. It's demonstrating the exact point in question: that if the logs were just stored in plain text, then grepping them would be an o
by burntsushi 1y ago
Their measurement isn't wrong. It's demonstrating the exact point in question: that if the logs were just stored in plain text, then grepping them would be an order of magnitude faster (or multiple orders of magnitude in the case of ripgrep) than whatever `journalctl --grep` is doing.
- godelski 1y agoTheir measurements are wrong because the journalctl command is also performing a decompression operation. THEY ARE NOT DOING THE SAME THING > that if the logs were just stored in plain text So store them in plain text then cat /etc/systemd/journald.conf https://www.freedesktop.org/software/systemd/man/latest/journald.conf.html
- burntsushi 1y agoHow it's doing the search is irrelevant. What's being measured here is the user experience. This isn't some kind of attempt to do an apples-to-apples grep comparison. This is about how long you have to wait for a search of your logs to complete.