Nah, sekarang gimana caranya buat mengetahui proses apa aja yang membuat CPU Load Mikrotik nya jadi tinggi? Jawabannya mudah, kita tinggal buka aja menu Tool --> Profile. Untuk Mikrotk dengan CPU Core lebih dari 1, maka kita bisa memilih CPU Core mana yang hendak dilihat proses nya, bisa juga dilihat proses total untuk semua CPU core nya. Berikut tampilan menu profiler nya :
- idle - shows unused CPU. Typically idle=100%-(sum of all process cpu usages).
- ppp
- pppoe
- ppp-compression
- ppp-mppe
- ethernet - cpu used by ethernets when sending/receiving packets
- bridging
- encrypting - cpu used by packet encryption
- ipsec - IP security
- queuing - packet queuing
- firewall - packet processing in Ip firewall
- l7-matcher - cpu used by Layer7 matcher.
- p2p-matcher - Peer-to-peer traffic matcher in ip firewall
- gre - Gre tunnels
- eoip - EoIP tunnels
- m3p - MikroTik Packet Packer Protocol
- radius
- ip-pool
- routing
- sniffing
- traffic-accounting
- traffic-flow
- console
- telnet
- ssh
- ftp
- tfpt
- www
- dns
- snmp
- socks
- web-proxy
- winbox
- metarouter-fs
- metarouter-net
- kvm
- profiling - cpu used by Profiler tool itself
- btest - bandwidth test tool
- logging
- flash - cpu usage when writing to NAND
- disk - cpu usage when wiring to Disk
- networking - core packet processing
- serial
- usb
- firewall-mgmt
- queue-mgmt
- fetcher
- backup
- graphing
- health
- isdn
- dhcp
- hotspot
- radv - IPv6 route advertisement
- ntp - NTP server/client
- ldp
- mpls
- pim - Multicast routing protocol
- igmp-proxy
- bgp
- ospf
- rip
- mme
- synchronous - cpu usage by synchronous cards
- gps
- user-manager
- wireless
- dude
- supout.rif - cpu used by supout.rif file creator.
- management - RouterOS management processes that do not fall into any other classifier. For example, when routes added to kernel, internal messaging exchange between RouterOS applications, etc.
- unclassified - any other processes that were not classified.
RouterOS management processes that do not fall into any other classifier. For example, when routes added to kernel, internal messaging exchange between RouterOS applications, etc.