[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-6261":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":39,"readmeContent":40,"aiSummary":41,"trendingCount":16,"starSnapshotCount":16,"syncStatus":17,"lastSyncTime":42,"discoverSource":43},6261,"nvtop","Syllo\u002Fnvtop","Syllo","GPU & Accelerator process monitoring for AMD, Apple, Huawei, Intel, NVIDIA and Qualcomm","",null,"C",10730,396,83,116,0,2,18,97,13,42.8,"Other",false,"master",true,[27,28,29,30,31,32,33,34,35,36,37,38],"adreno","amd","apple","ascend","command-line-tool","gpu","huawei","intel","linux","monitoring","ncurses","nvidia","2026-06-12 02:01:17","NVTOP\n=====\n\nWhat is NVTOP?\n--------------\n\nNVTOP stands for Neat Videocard TOP, a (h)top like task monitor for GPUs and\naccelerators. It can handle multiple GPUs and print information about them in a\nhtop-familiar way.\n\nCurrently supported vendors are AMD (Linux amdgpu driver), Apple (limited M1 &\nM2 support), Huawei (Ascend), Intel (Linux i915\u002FXe drivers), NVIDIA (Linux\nproprietary divers), Qualcomm Adreno (Linux MSM driver), Broadcom VideoCore (Linux v3d driver),\nRockchip, MetaX (MXSML driver), Enflame (Linux EFML driver), Tenstorrent (Linux tt-kmd driver).\nRockchip, MetaX (MXSML driver), Enflame (Linux EFML driver), Iluvatar CoreX (ixML \u002F libixml).\n\nBecause a picture is worth a thousand words:\n\n![NVTOP interface](\u002Fscreenshot\u002FNVTOP_ex1.png)\n\nTable of Contents\n-----------------\n\n- [NVTOP Options and Interactive Commands](#nvtop-options-and-interactive-commands)\n  - [Interactive Setup Window](#interactive-setup-window)\n  - [Saving Preferences](#saving-preferences)\n  - [NVTOP Manual and Command line Options](#nvtop-manual-and-command-line-options)\n- [GPU Support](#gpu-support)\n  - [AMD](#amd)\n  - [Intel](#intel)\n  - [NVIDIA](#nvidia)\n  - [Adreno](#adreno)\n  - [Apple](#apple)\n  - [Ascend](#ascend) (only tested on 910B)\n  - [Iluvatar CoreX](#iluvatar-corex)\n  - [VideoCore](#videocore)\n  - [Rockchip](#rockchip)\n  - [MetaX](#metax)\n  - [Enflame](#enflame)\n  - [Tenstorrent](#tenstorrent)\n- [Build](#build)\n- [Distribution Specific Installation Process](#distribution-specific-installation-process)\n  - [Ubuntu \u002F Debian](#ubuntu--debian)\n    - [Ubuntu Impish (21.10) \u002F Debian buster (stable) and more recent (stable)](#ubuntu-impish-2110-debian-buster-stable-and-more-recent)\n  - [Fedora \u002F Red Hat \u002F CentOS](#fedora--red-hat--centos)\n  - [OpenSUSE](#opensuse)\n  - [Arch Linux](#arch-linux)\n  - [Gentoo](#gentoo)\n  - [AppImage](#appimage)\n  - [Snap](#snap)\n  - [Conda-forge](#conda-forge)\n  - [Docker](#docker)\n  - [WSL2](#wsl2)\n- [NVTOP Build](#nvtop-build)\n- [Troubleshoot](#troubleshoot)\n- [License](#license)\n\nNVTOP Options and Interactive Commands\n--------------------------------------\n### Interactive Setup Window\n\nNVTOP has a builtin setup utility that provides a way to specialize the interface to your needs.\nSimply press ``F2`` and select the options that are the best for you.\n\n![NVTOP Setup Window](\u002Fscreenshot\u002FNvtop-config.png)\n\n### Saving Preferences\n\nYou can save the preferences set in the setup window by pressing ``F12``.\nThe preferences will be loaded the next time you run ``nvtop``.\n\n### NVTOP Manual and Command line Options\n\nNVTOP comes with a manpage!\n```bash\nman nvtop\n```\nFor quick command line arguments help\n```bash\nnvtop -h\nnvtop --help\n```\n\nGPU Support\n-----------\n\n### AMD\n\nNVTOP supports AMD GPUs using the `amdgpu` driver and the legacy `radeon` driver (legacy GPUs, limited support) through the exposed DRM and\nsysfs interface.\n\nThe radeon provides limited metrics compared to amdgpu.\n\nAMD introduced the fdinfo interface in kernel 5.14 ([browse kernel\nsource](https:\u002F\u002Fgit.kernel.org\u002Fpub\u002Fscm\u002Flinux\u002Fkernel\u002Fgit\u002Fstable\u002Flinux.git\u002Ftree\u002Fdrivers\u002Fgpu\u002Fdrm\u002Famd\u002Famdgpu\u002Famdgpu_fdinfo.c?h=linux-5.14.y)).\nHence, you will need a kernel with a version greater or equal to 5.14 to see the\nprocesses using AMD GPUs.\n\nSupport for recent GPUs are regularly mainlined into the linux kernel, so please\nuse a recent-enough kernel for your GPU.\n\n### Intel\n\nNVTOP supports Intel GPUs using the `i915` or `xe` linux driver.\n\nIntel introduced the fdinfo interface in kernel 5.19 ([browse kernel\nsource](https:\u002F\u002Fgit.kernel.org\u002Fpub\u002Fscm\u002Flinux\u002Fkernel\u002Fgit\u002Fstable\u002Flinux.git\u002Ftree\u002Fdrivers\u002Fgpu\u002Fdrm\u002Fi915\u002Fi915_drm_client.c?h=linux-5.19.y)).\nHence, you will need a kernel with a version greater or equal to 5.19 to see the\nprocesses using Intel GPUs.\n\nIntel requires CAP_PERFMON or CAP_SYS_ADMIN capabilities to access the total memory usage,\nyou can run `sudo setcap cap_perfmon=ep nvtop` to grant the necessary permissions or run nvtop as root.\n\n### NVIDIA\n\nThe *NVML library* does not support some of the queries for GPUs coming before the\nKepler microarchitecture. Anything starting at GeForce 600, GeForce 800M and\nsuccessor should work fine. For more information about supported GPUs please\ntake a look at the [NVML documentation](http:\u002F\u002Fdocs.nvidia.com\u002Fdeploy\u002Fnvml-api\u002Fnvml-api-reference.html#nvml-api-reference).\n\n### Adreno\n\nNVTOP supports Adreno GPUs using the `msm` linux driver.\n\nmsm introduced the fdinfo interface in kernel 6.0 ([browse kernel\nsource](https:\u002F\u002Fgit.kernel.org\u002Fpub\u002Fscm\u002Flinux\u002Fkernel\u002Fgit\u002Fstable\u002Flinux.git\u002Ftree\u002Fdrivers\u002Fgpu\u002Fdrm\u002Fmsm\u002Fmsm_drv.c?h=linux-6.0.y)).\nHence, you will need a kernel with a version greater or equal to 6.0 to see the\nprocesses using Adreno GPUs.\n\n### Apple\n\nNVTOP includes some initial support for Apple using Metal. This is only supported when building for Apple, and when building for Apple only this vendor is supported.\n\n**APPLE SUPPORT STATUS**\n- Apple support is still being worked on. Some bugs and limitations may apply.\n\n### Ascend\n\nNVTOP supports Ascend (testing on Altas 800 (910B)) by DCMI API (version 6.0.0).\n\nCurrently, the DCMI only supports limited APIs, missing PCIe generation, tx\u002Frx throughput info, max power draw etc.\n\n### Iluvatar CoreX\n\nNVTOP supports Iluvatar CoreX GPUs through the ixML library.\n\nThe backend dynamically loads `libixml.so` from `\u002Fusr\u002Flocal\u002Fcorex\u002Flib`,\n`\u002Fusr\u002Flocal\u002Fcorex\u002Flib64`, or the default dynamic loader search path. The ixML\nruntime exposes an NVML-compatible API surface used by NVTOP to query device,\npower, PCIe, clock, temperature, memory, and process information.\n\n### VideoCore\n\nNVTOP supports VideoCore (testing on raspberrypi 4B).\n\nSupports GPU frequency, temperature, utilization, per-process utilization, GPU memory usage, and H264 decoding utilization.\n\nOn non-raspberry pi os, you need to use the `linux-rpi 6.12.y` kernel and above, and ensure the presence of the `\u002Fdev\u002Fvcio` device.\n\n### Rockchip\n\nNVTOP supports Rockchip (testing on orangepi 5 plus).\n\nSupports NPU frequency, temperature, utilization.\n\n### MetaX\n\nNVTOP supports MetaX (testing on MXC500) by MXSML LIBRARY.\n\nFor more information about GPUs please take a look at the [METAX documentation](https:\u002F\u002Fdeveloper.metax-tech.com\u002Fdoc\u002Findex)\n\n### Enflame\n\nNVTOP supports Enflame GCUs (testing on Enflame S60, Enflame L300 and Enflame L600) by EFML LIBRARY\n\nGCU, which refers to General Compute Unit, is a type of accelerator card that is used to perform general-purpose computing tasks just like GPGPU.\n\n### Tenstorrent\n\nNVTOP supports Tenstorrent AI accelerators (Blackhole, Wormhole, Grayskull) through the [tt-kmd](https:\u002F\u002Fgithub.com\u002Ftenstorrent\u002Ftt-kmd) kernel driver.\n\nSupports temperature, power draw, AI clock, fan RPM, PCIe link info, and process listing. No external libraries required -- all data is read from sysfs, hwmon, and procfs.\n\nBuild\n-----\n\nSeveral libraries are required in order for NVTOP to display GPU info:\n\n* The *ncurses* library driving the user interface.\n  * This makes the screen look beautiful.\n* For NVIDIA: the *NVIDIA Management Library* (*NVML*) which comes with the GPU driver.\n  * This queries the GPU for info.\n* For AMD: the libdrm library used to query AMD GPUs through the kernel driver.\n* For METAX: the *MetaX System Management Library* (*MXSML*) which comes with the GPU driver.\n  * This queries the GPU for info.\n* For Enflame: the *Enflame Management Library* (*EFML*) which comes with the GCU driver.\n* For Iluvatar CoreX: the *ixML* runtime library (`libixml.so`) which comes with the driver.\n  * This backend loads the library dynamically at runtime.\n\n## Distribution Specific Installation Process\n\n### Ubuntu \u002F Debian\n\nIf your distribution provides the snap utility, follow the [snap installation process](#snap) to obtain an up-to-date version of `nvtop`.\n\nA standalone application is available as [AppImage](#appimage).\n\n#### Ubuntu Focal (20.04), Debian buster (stable) and more recent\n\n```bash\nsudo apt install nvtop\n```\n\n#### Ubuntu PPA\n\nA [PPA supporting Ubuntu 20.04 and newer](https:\u002F\u002Flaunchpad.net\u002F~quentiumyt\u002F+archive\u002Fubuntu\u002Fnvtop) is provided by\n[Quentin Lienhardt](https:\u002F\u002Fgithub.com\u002FQuentiumYT) that offers an up-to-date version of `nvtop`, enabled for NVIDIA, AMD and Intel.\n\n```bash\nsudo add-apt-repository ppa:quentiumyt\u002Fnvtop\nsudo apt install nvtop\n```\n\n#### Older\n\n- AMD and Intel Dependencies\n  ```bash\n  sudo apt install libdrm-dev libsystemd-dev\n  # Ubuntu 18.04\n  sudo apt install libudev-dev\n  ```\n\n- NVIDIA Dependency\n  - NVIDIA drivers (see [Ubuntu Wiki](https:\u002F\u002Fhelp.ubuntu.com\u002Fcommunity\u002FBinaryDriverHowto\u002FNvidia) or [Ubuntu PPA](https:\u002F\u002Flaunchpad.net\u002F~graphics-drivers\u002F+archive\u002Fubuntu\u002Fppa) or [Debian Wiki](https:\u002F\u002Fwiki.debian.org\u002FNvidiaGraphicsDrivers#NVIDIA_Proprietary_Driver))\n\n- NVTOP Dependencies\n  - CMake, ncurses and Git\n  ```bash\n  sudo apt install cmake libncurses5-dev libncursesw5-dev git\n  ```\n\n- NVTOP\n  - Follow the [NVTOP Build](#nvtop-build)\n\n\n### Fedora \u002F Red Hat \u002F CentOS\n\nA standalone application is available as [AppImage](#appimage).\n\n#### Fedora 36 and newer\n\n- ```bash\n  sudo dnf install nvtop\n  ```\n\n#### Red Hat Enterprise Linux 8 and 9\n\n- ```bash\n  sudo dnf install -y https:\u002F\u002Fdl.fedoraproject.org\u002Fpub\u002Fepel\u002Fepel-release-latest-$(rpm -E %{rhel}).noarch.rpm\n  sudo dnf install nvtop\n  ```\n\n#### CentOS Stream, Rocky Linux, AlmaLinux\n\n- ```bash\n  sudo dnf install -y epel-release\n  sudo dnf install nvtop\n  ```\n\n#### Build process for Fedora \u002F Red Hat \u002F CentOS:\n\n- AMD and Intel Dependencies\n  ```bash\n  sudo dnf install libdrm-devel systemd-devel\n  ```\n\n- NVIDIA Dependency\n  - NVIDIA drivers, **CUDA required for nvml libraries** (see [RPM Fusion](https:\u002F\u002Frpmfusion.org\u002FHowto\u002FNVIDIA))\n\n- NVTOP Dependencies\n  - CMake, ncurses, C++ and Git\n  ```bash\n  sudo dnf install cmake ncurses-devel git gcc-c++\n  ```\n\n- NVTOP\n  - Follow the [NVTOP Build](#nvtop-build)\n\n### OpenSUSE\n\nA standalone application is available as an [AppImage](#appimage).\n\nBuild process for OpenSUSE:\n\n- AMD Dependency\n  ```bash\n  sudo zypper install libdrm-devel\n  ```\n\n- NVIDIA Dependency\n  - NVIDIA drivers (see [SUSE Support Database](https:\u002F\u002Fen.opensuse.org\u002FSDB:NVIDIA_drivers))\n\n- NVTOP Dependencies\n  - CMake, ncurses and Git\n    ```bash\n    sudo zypper install cmake ncurses-devel git\n    ```\n\n- NVTOP\n  - Follow the [NVTOP Build](#nvtop-build)\n\n### Arch Linux\n\n- ```bash\n  sudo pacman -S nvtop\n  ```\n\n### Gentoo\n\n- ```bash\n  sudo emerge -av nvtop\n  ```\n\n### AppImage\n\nAn AppImage is a standalone application. Just download the AppImage, make it executable and run it!\n\n- Go to the [release page](https:\u002F\u002Fgithub.com\u002FSyllo\u002Fnvtop\u002Freleases\u002Flatest) and download `nvtop-x86_64.AppImage`\n\n- ```bash\n  # Go to the download location ** The path may differ on your system **\n  cd $HOME\u002FDownloads\n  # Make the AppImage executable\n  chmod u+x nvtop-x86_64.AppImage\n  # Enjoy nvtop\n  .\u002Fnvtop-x86_64.AppImage\n  ```\n\nIf you are curious how that works, please visit the [AppImage website](https:\u002F\u002Fappimage.org\u002F).\n\n### Snap\n\n- ```bash\n  snap install nvtop\n  # Add the capability to kill processes inside nvtop\n  snap connect nvtop:process-control\n  # Add the capability to inspect GPU information (fan, PCIe, power, etc)\n  snap connect nvtop:hardware-observe\n  # AMDGPU process list support (read \u002Fproc\u002F\u003Cpid>)\n  snap connect nvtop:system-observe\n  # Temporary workaround to get per-process GPU usage (read \u002Fproc\u002F\u003Cpid>\u002Ffdinfo)\n  snap connect nvtop:kubernetes-support\n  ```\n\nNotice: The connect commands allow\n\n### Conda-forge\n\nA [conda-forge feedstock for `nvtop`](https:\u002F\u002Fgithub.com\u002Fconda-forge\u002Fnvtop-feedstock) is available.\n\n#### conda \u002F mamba \u002F miniforge\n\n```bash\nconda install --channel conda-forge nvtop\n```\n\n#### pixi\n\n```bash\npixi global install nvtop\n```\n\n### Docker\n\n- NVIDIA drivers (same as above)\n\n- [nvidia-docker](https:\u002F\u002Fgithub.com\u002FNVIDIA\u002Fnvidia-docker) (See [Container Toolkit Installation Guide](https:\u002F\u002Fdocs.nvidia.com\u002Fdatacenter\u002Fcloud-native\u002Fcontainer-toolkit\u002Finstall-guide.html#docker))\n\n- ```bash\n  git clone https:\u002F\u002Fgithub.com\u002FSyllo\u002Fnvtop.git && cd nvtop\n  sudo docker build --tag nvtop .\n  sudo docker run -it --rm --runtime=nvidia --gpus=all --pid=host nvtop\n  ```\n\n### WSL2\n\nNvtop support in WSL2 mostly boils down to GPU\u002FAccelerator vendor support of\nWSL2. Nvtop should work out of the box for the following configurations:\n\n- NVIDIA: Please refer to [NVIDIA's user guide to get started with CUDA on\nWSL2](https:\u002F\u002Fdocs.nvidia.com\u002Fcuda\u002Fwsl-user-guide\u002Findex.html#getting-started-with-cuda-on-wsl)\nto avoid overiding the driver exposed by WSL2 (from Windows) with the NVIDIA\nLinux drivers.\n\n## NVTOP Build\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002FSyllo\u002Fnvtop.git\nmkdir -p nvtop\u002Fbuild && cd nvtop\u002Fbuild\ncmake .. -DNVIDIA_SUPPORT=ON -DAMDGPU_SUPPORT=ON -DINTEL_SUPPORT=ON\nmake\n\n# Install globally on the system\nsudo make install\n\n# Alternatively, install without privileges at a location of your choosing\n# cmake .. -DNVIDIA_SUPPORT=ON -DAMDGPU_SUPPORT=ON -DINTEL_SUPPORT=ON -DCMAKE_INSTALL_PREFIX=\u002Fpath\u002Fto\u002Fyour\u002Fdir\n# make\n# make install\n```\n\nIf you use **conda** as environment manager and encounter an error while building NVTOP, try `conda deactivate` before invoking `cmake`.\n\nThe build system supports multiple build types (e.g. -DCMAKE_BUILD_TYPE=RelWithDebInfo):\n\n* Release: Binary without debug info\n* RelWithDebInfo: Binary with debug info\n* Debug: Compile with warning flags and address\u002Fundefined sanitizers enabled (for development purposes)\n\nTroubleshoot\n------------\n\n- The plot looks bad:\n  - Verify that you installed the wide character version of the ncurses library (libncurses**w**5-dev for Debian \u002F Ubuntu), clean the build directory and restart the build process.\n- **Putty**: Tell putty not to lie about its capabilities (`$TERM`) by setting the field ``Terminal-type string`` to ``putty`` in the menu\n  ``Connection > Data > Terminal Details``.\n- `NO GPU to monitor.` for NVIDIA GPUs:\n  - `nvtop` loads a shared library named `libnvml.so` (shipped with the NVIDIA\n  drivers) to querry device information. If the library is not present, nvtop\n  will not be able to monitor your NVIDIA device.\n  - On `WSL2`, the installation instructions are slightly different since the\n  driver is being exposed by Windows to the virtual machine (see instruction\n  link in [the WSL2 section](#wsl2)). If you install the NVIDIA linux drivers\n  inside WSL2, you may encounter a version mismatch error or nvtop may silently\n  not work at all.\n\nLicense\n-------\n\nNVTOP is licensed under the GPLv3 license or any later version.\nYou will find a copy of the license inside the COPYING file of the repository or\nat the GNU website \u003C[www.gnu.org\u002Flicenses\u002F](http:\u002F\u002Fwww.gnu.org\u002Flicenses\u002F)>.\n","NVTOP 是一个用于监控 GPU 和加速器的工具，支持 AMD、Apple、华为、Intel、NVIDIA 和 Qualcomm 等多种厂商的设备。它通过类似 htop 的界面提供实时的 GPU 使用情况和性能数据，支持多 GPU 监控，并且可以自定义显示设置以适应不同用户的需求。该工具利用 C 语言编写，具有良好的跨平台兼容性，尤其适用于 Linux 系统。NVTOP 适合需要对 GPU 资源进行高效管理和监控的场景，如数据中心、高性能计算集群以及深度学习应用等。","2026-06-11 03:06:08","top_language"]