Are you sure that there still is a problem? There were some bugs that
have been fixed months ago. Aside from that the memory usage could be
off as journal uses mmap.
But systemd always uses the journal (not runtime configurable IIRC), so
best to make it efficient. It should also somehow be low maintenance.
Meaning: maybe it will use less memory when there is less available
(guessing)?
I don't know about mmap, but that's what a top gives on the current cooker:
326 root 1 0 1064m 37m 36m S 0 1.9 0:14.73 systemd-journal
even though it is only virtual, that's sound crazy to go up 1GB.
rsyslog never goes above 1M.
Cheers,
Chris.
