Am 19.11.19 um 16:25 schrieb Martin Wilck:
Yuck. Looks like a thing someone should fix, some time. Have you considered filing a bug or feature request?
We had high level support tickets open for this for SLES12/SOC6/SOC7. It's just that the journal is designed essentially as a write only database. This is why it performs bad, even if no disk IO is involved at all. (This all was on machines with more RAM than my average machine at home has disk storage and more CPU cores than all the CPUs in my home combined, including the embedded CPUs..., so it is probably also not possible to solve the issue by "just" throwing more RAM or a bigger CPU at it. I'm quite sure there were no significantly bigger CPUs available at the time). Journal is designed to work somehow on the average developers notebook (fast SSD, reasonable amount of RAM, reboots often). It is near unusable for serious machines with big workloads. rsyslog performs fine, though. Feel free to rewrite the journal from scratch, considering serious use cases and not just toy usage. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org