Multi-featured system monitor
SMC v1 (GTK3) | SMC v2 (GTK3/4) | SMC v3 (Tk)
Translations: Chinese (Simplified) | Chinese (Traditional) | Czech | German | English | French | Hungarian | Persian | Polish | Portuguese (Brazilian) | Portuguese (Portugal) | Russian | Spanish | Turkish | Notes for translators
- Detailed system performance and usage usage monitoring/managing features:
- Monitoring CPU, RAM, Disk, Network, GPU hardware/usage information
- Monitoring and managing processes and services (systemd)
- Monitoring users, sensors and general system information
- Supports PolicyKit. No need to run the application with "sudo"
- Hardware selection options (selecting CPU cores, disks, network cards, GPUs)
- Plotting performance data of multiple devices at the same time
- Interactive charts for querying performance data on any point
- Option for showing processes as tree or list
- Optimized for low CPU usage
- Customization menus for almost all tabs
- Supports ARM architecture
- Free and open source
- There are several options for using System Monitoring Center:
- Installing from Flatpak (Details)
- Installing from application stores (Pardus Application Center, Pi-Apps Store)
- Installing from repositories of distributions
- Running from source code: in
src/folder, run:python3 ./run_from_source.py
Show
There is no need to install these dependencies for installing the application from Flatpak. For other installation types:
-
For System Monitoring Center v3.x.x:
dmidecode, hwdata, iproute2, python3 (>=3.6), python3-cairo, python3-tk, python3-pil, python3-pil.imagetk, util-linux (>=2.31)
-
Following dependencies may be required on some systems:
libcairo2-dev(for systems with .deb packages)polkit(for Arch Linux)
-
Optional dependencies:
vcgencmd(for physical RAM size, GPU frequency and video memory information on Raspberry Pi devices)xorg-xrandr(for more accurate screen resolution and refresh rate detection)
Show
- GPU usage information availability depends on vendor/driver.
- GPU load is not tracked if GPU tab is switched off (for lower CPU usage).
- Virtual machines may not provide CPU min-max frequencies, sensors and RAM hardware information.
- Non-Flatpak versions of the application has higher performance (start speed, CPU, RAM usage).
- Not detected so far.
















