Je n’ai n’ai pas ce souci quand je modifie le % de cpu…
@stephane où vois-tu que Duniter est à 100% (dans les logs, avec la commande top, …) ?
[Edit]
Avec la commande top, je suis aussi à 100% 
top - 05:05:50 up 12:47, 2 users, load average: 4.54, 4.47, 4.28
Tasks: 167 total, 5 running, 161 sleeping, 0 stopped, 1 zombie
%Cpu(s): 99.6 us, 0.3 sy, 0.0 ni, 0.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem: 945512 total, 911628 used, 33884 free, 71800 buffers
KiB Swap: 102396 total, 560 used, 101836 free. 334624 cached Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2749 root 20 0 130772 70872 17616 R 99.6 7.5 695:08.81 node
2767 root 20 0 132920 71996 17616 R 99.3 7.6 695:21.97 node
2755 root 20 0 130216 72652 17684 R 97.3 7.7 696:05.28 node
2761 root 20 0 132856 70728 17572 R 97.0 7.5 695:13.09 node
1478 root 20 0 144632 10668 5556 S 0.7 1.1 1:23.76 fail2ban-server
1 root 20 0 23212 4044 2668 S 0.3 0.4 0:05.67 systemd
857 root 20 0 7972 4308 3880 S 0.3 0.5 0:00.29 sshd
963 redis 20 0 29352 2724 2092 S 0.3 0.3 1:25.19 redis-server
1530 mysql 20 0 554552 50756 12568 S 0.3 5.4 0:40.25 mysqld
2736 root 20 0 210008 125252 19772 S 0.3 13.2 100:43.98 duniter_default
7444 admin 20 0 11960 3492 2904 S 0.3 0.4 0:00.16 sshd
7462 admin 20 0 4992 2256 1848 R 0.3 0.2 0:00.40 top
2 root 20 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:05.52 ksoftirqd/0