Am 21.11.18 um 14:00 schrieb Carlos E. R.:
On 21/11/2018 13.55, Stefan Seyfried wrote:
Am 21.11.18 um 13:33 schrieb Carlos E. R.:
Well, no, it seems systemd-timesyncd uses much more memory.
You are looking at the wrong field.
Nobody realy cares how much virtual memory a process has mapped / reserved, but instead how big its resident set size is.
I looked at the resident size :-)
Ok, I was confused by the "top" line.
76 chronyd 3024 systemd-timesyn
But something is fishy there. If even my pretty minimal example program uses 772kB (with 708kB shared) according to top,then I cannot imagine how chrony will work with just 76kb. You are also using different tools on both machines (see the different output columns), so the results might not be comparable. It would of course be highly embarassing if a stupid sntp client like systemd-timesyncd really uses more memory than a full fledged ntp server implementation like chronyd. Judging from other systemd experiences, I would not be surprised, though. -- 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