On Wed, 21 Nov 2018 14:07:13 +0100, "Carlos E. R."
On 21/11/2018 13.51, H.Merijn Brand wrote:
On Wed, 21 Nov 2018 13:33:56 +0100, "Carlos E. R." <> wrote:
[...]
chrony:
top - 13:21:03 up 13 days, 12:59, 3 users, load average: 0.23, 0.46, 0.54 Tasks: 342 total, 1 running, 341 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.9 us, 4.7 sy, 0.1 ni, 76.7 id, 0.1 wa, 0.0 hi, 0.5 si, 0.0 st KiB Mem : 3942200 total, 1096244 free, 2397364 used, 448592 buff/cache KiB Swap: 12582908 total, 9669852 free, 2913056 used. 1185596 avail Mem
PID USER PR NI VIRT RES SHR SWAP S %CPU %MEM TIME+ COMMAND 1166 chrony 20 0 90388 76 0 132 S 0.000 0.002 0:00.72 chronyd
systemd-timesyncd
top - 13:25:34 up 13 days, 13:03, 3 users, load average: 0.39, 0.60, 0.59 Tasks: 323 total, 1 running, 322 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.9 us, 4.7 sy, 0.1 ni, 76.7 id, 0.1 wa, 0.0 hi, 0.5 si, 0.0 st KiB Mem : 3942200 total, 1002344 free, 2444456 used, 495400 buff/cache KiB Swap: 12582908 total, 9683932 free, 2898976 used. 1113416 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 14070 systemd+ 20 0 133332 3024 2560 S 0.000 0.077 0:00.03 systemd-timesyn
Well, no, it seems systemd-timesyncd uses much more memory.
I'm going back to chrony.
If size is the only argument, ntpd is the smallest
USER PID PPID PRI NI SIZE STIME TTY TIME COMMAND ntp 1533 1 20 0 9962 14:48:24 - 0:00:05 /usr/sbin/ntpd -p /var/run/ntp/ntpd.pid -g -u ntp:ntp -c /etc/ntp.conf ntp 1538 1533 20 0 9962 14:48:24 - 0:00:00 ntpd: asynchronous dns resolver
USER PID PPID PRI NI SIZE STIME TTY TIME COMMAND chrony 346 1 20 0 22305 13:43:27 - 0:00:00 /usr/sbin/chronyd
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1534 ntp 20 0 39848 4080 3300 S 0.000 0.025 0:00.00 ntpd 1535 ntp 20 0 39848 776 0 S 0.000 0.005 0:00.00 ntpd
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 346 chrony 20 0 89220 2484 2300 S 0.000 0.015 0:00.01 chronyd
Chrony uses half the resident size than ntpd (top output).
But more than twice virtual memory
The other output is from "ps", I guess; I don't know there what "SIZE" means, what exact concept. :-?
The SIZE and RSS fields don't count some parts of a process including the page tables, kernel stack, struct thread_info, and struct task_struct. This is usually at least 20 KiB of memory that is always resident. SIZE is the virtual size of the process (code+data+stack). -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.29 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/