Bug#856265: systemd-journald: RuntimeMaxUse is not properly obeyed

2017-02-27 Thread Michael Biebl
Am 27.02.2017 um 13:57 schrieb Martin Pitt: > Felipe Sateler [2017-02-27 9:39 -0300]: >> For avoidance of doubt, RuntimeMaxUse does not refer to RSS, but >> rather to the "disk" space used in /run when the persistent journal is >> not active. So this flag does not control what you want. AFAIK, the

Bug#856265: systemd-journald: RuntimeMaxUse is not properly obeyed

2017-02-27 Thread Martin Pitt
Felipe Sateler [2017-02-27 9:39 -0300]: > For avoidance of doubt, RuntimeMaxUse does not refer to RSS, but > rather to the "disk" space used in /run when the persistent journal is > not active. So this flag does not control what you want. AFAIK, there > is no way to control max memory usage. Ther

Bug#856265: systemd-journald: RuntimeMaxUse is not properly obeyed

2017-02-27 Thread Stephan Sokolow (You actually CAN reply)
The observed behaviour is *with* the persistent journal. Forwarding to inetutils-syslogd and using Storage=none results in steady memory consumption at 20% of the peak memory I experienced while testing Storage=persistent (and that's for both journald and syslogd combined). On 17-02-27 07:23

Bug#856265: systemd-journald: RuntimeMaxUse is not properly obeyed

2017-02-27 Thread Stephan Sokolow (You actually CAN reply)
Ahh. Is there currently any functionality in journald for controlling flushing to limit RSS or is this just a case where journald's built-in logging capabilities are not currently suited to constrained systems? On 17-02-27 07:04 AM, Michael Biebl wrote: Am 27.02.2017 um 10:41 schrieb Stephan

Bug#856265: systemd-journald: RuntimeMaxUse is not properly obeyed

2017-02-27 Thread Felipe Sateler
On Mon, Feb 27, 2017 at 6:41 AM, Stephan Sokolow (You actually CAN reply) wrote: > > In my testing, 7.7% RSS appeared to be a hard lower limit well above the > 2/3/4 MiB I specified while experimenting. For avoidance of doubt, RuntimeMaxUse does not refer to RSS, but rather to the "disk" space

Bug#856265: systemd-journald: RuntimeMaxUse is not properly obeyed

2017-02-27 Thread Michael Biebl
Am 27.02.2017 um 13:11 schrieb Stephan Sokolow (You actually CAN reply): > Is there currently any functionality in journald for controlling > flushing to limit RSS Not that I'm aware of. That said, if you have constrained memory requirements, I wouldn't log to /run (which is a tmpfs, i.e. uses you

Bug#856265: systemd-journald: RuntimeMaxUse is not properly obeyed

2017-02-27 Thread Stephan Sokolow (You actually CAN reply)
Package: systemd Version: 215-17+deb8u6 Severity: normal File: /lib/systemd/systemd-journald Dear Maintainer, While configuring a Debian jessie VM for testing deployments to a 256MiB VPS, I discovered that no combination of settings I tried would keep journald's memory usage from climbing sign