[systemd-devel] Excessive (virtual) memory usage of journald

[Greg KH]

On Fri, Jun 21, 2013 at 03:16:50PM +0200, Holger Hans Peter Freyther wrote:
> On Fri, Jun 21, 2013 at 01:53:23PM +0200, Kay Sievers wrote:
> 
> > Fragmentation, allocation? I don't think we talk about the same thing here.
> 
> ... you will figure that out.
> 
> > Mapping an on-disk file "a symptom of inefficiency", you might need to
> > update your idea of how things work.
> 
> I didn't say that mmap of a file is bad. But thanks for putting words
> in my mouth. I just wonder how a process that manipulates a file that
> is stored in /run/log/journal/*/system.journal that can grow up to a
> single digit MB needs an address space of 200MB.
> 
> Sure the answer is that journald maps the same fd with the same flags
> (rwxs) and size multiple times (possible even with the same offset in
> the file). Isn't doing more work than needed excessive behavior?

How does this compare with other logging programs that implement the
same type of functionality?

Looking at raw memory footprints really doesn't show much at all,
especially with no context, or percentages compared to the overall
system memory.

greg k-h