On Sun, Apr 14, 2013 at 6:09 AM, Stefan Seyfried <stefan.seyfried@googlemail.com> wrote:
(and no, journal is not an
alternative, because the performance is abysmal. "journalctl", then hitting "end" thrashes my disk for about three minutes before responding. I can grep through 3 Years worth of /var/log/messages-* in the same time).
Since systemd 195 there have been a lot of improvements into the journal, I suggest you test and report what happends with systemd > 201
I doubt they will fix the online file format after the fact. The problem is, that it creates massively fragmented files on-disk and this hurts everyone with non-SSD setup. Probably it works well on Lennart and Kay's notebooks with fast SSD but it sucks almost everywhere else.
Even each "systemctl status foo.service" thrashes the disk for ~10 seconds because it queries the journal.
This may have something to do with the fact that the journal is mmaped into memory, even for writing. It may be worthwhile to consider a different strategy there, or at least make heavy use of madvise, in conjunction with preallocating the space on disk, to make sure the FS allocates it sequentially. Otherwise, the result will be a sparse file, which are usually heavily fragmented when written in random order. I guess I should say this upstream, but the thought occurred to me here, I hope Christian will push it upstream if it is worthwhile? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org