Systemd-journald use high CPU

when send a lot of packet , systemd-journald use high CPU

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
9148 root 20 0 29476 3108 2844 R 100.0 0.2 0:43.81 systemd-journal

root@DQV8M42:~# journalctl
– Logs begin at Thu 2018-09-27 01:23:08 UTC, end at Thu 2018-09-27 01:23:14 UTC. –
Sep 27 01:23:07 DQV8M42 audit[4499]: AVC apparmor=“ALLOWED” operation=“recvmsg” profile="snap.bpscloud.
Sep 27 01:23:07 DQV8M42 audit[4499]: AVC apparmor=“ALLOWED” operation=“recvmsg” profile="snap.bpscloud.
Sep 27 01:23:07 DQV8M42 audit[3069]: AVC apparmor=“ALLOWED” operation=“sendmsg” profile="snap.bpscloud.
Sep 27 01:23:07 DQV8M42 audit[4499]: AVC apparmor=“ALLOWED” operation=“recvmsg” profile="snap.bpscloud.
Sep 27 01:23:07 DQV8M42 audit[4499]: AVC apparmor=“ALLOWED” operation=“recvmsg” profile="snap.bpscloud.

These messages are truncated, but it appears your snap is in devmode which can cause profuse logging if you don’t have any interfaces connected (policy violations are simple logged instead of denied). I suggest connecting the network and/or network-bind interfaces and these messages should be reduced. You might be interested in snappy-debug as described in Security policy and sandboxing.

thanks, this works! add [network]