Summary
The profiler tool shows CPU usage for each process running in RouterOS. It helps to identify which process is using most of the CPU resources.
[admin@MikroTik] > /tool/profile
On multi-core systems, the tool allows specifying per core CPU usage.
"CPU" parameter allows specifying integer number which represents a core or two of predefined values all and total:
- total - this value sets to show the sum of all core usages;
- all - value sets to show CPU usages separately for every available core
In the following example we will take a look at both predefined values:
[admin@MikroTik] > /tool/profile cpu=all NAME CPU USAGE ethernet 1 0% kvm 0 0% kvm 1 4.5% management 0 0% management 1 0.5% idle 0 100% idle 1 93% profiling 0 0% profiling 1 2% [admin@MikroTik] > /tool profile cpu=total NAME CPU USAGE ethernet all 0% console all 0% kvm all 2.7% management all 0% idle all 97.2% profiling all 0% bridging all 0%
Classifiers
Profile classifies processes in several classifiers. Most of them are self-explanatory and do not require detailed explanation.
- backup
- bfd{table
- bgp
- bridging
- btest
- certificate
- console
- dhcp
- disk
- dns
- dude
- eoip
- ethernet
- fetcher
- firewall
- firewall-mgmt
- flash
- ftp
- gps
- graphing
- gre
- health
- hotspot
- idle
- igmp-proxy
- internet-detect
- ip-pool
- ipsec
- isdn
- kvm
- l2tp
- l7-matcher
- ldp
- logging
- m3p
- management
- mme
- mpls
- networking
- ntp
- ospf
- ovpn
- p2p-matcher
- pim
- ppp
- pppoe
- pptp
- profiling
- queue-mgmt
- queuing
- radius
- radv
- rip
- routing
- serial
- sniffing
- snmp
- socks
- ssh
- ssl
- sstp
- synchronous
- syscalls
- telnet
- tftp
- traffic-accounting
- traffic-flow
- upnp
- usb
- user-manager
- web-proxy
- winbox
- wireless
- www