A NVIDIA GeForce RTX 5090 GPU is shown next to a 'GPU Taskman' application interface displaying real-time GPU and memory usage statistics for various processes.

Microsoft VP Unveils Open-Source GPU Task Manager That Reveals What’s Eating Your VRAM

GPU Taskman Gives PC Users a Clearer Look at VRAM Usage, GPU Performance, and Local AI Memory Demands

Tracking GPU memory usage can be frustrating, especially when VRAM seems to disappear without an obvious explanation. Windows Task Manager offers basic per-process GPU memory stats, but it does not always provide the depth needed by gamers, developers, or users running local AI models.

GPU Taskman, also known as gputaskman, is a new open-source utility created by Scott Hanselman, Vice President and Member of Technical Staff at Microsoft/GitHub. The tool is designed to show exactly how GPU resources are being used, with a much more detailed breakdown than many built-in monitoring options.

Hanselman shared the project in early November, explaining that he wanted better visibility into what was consuming his GPU memory. He also invited developers to contribute, making GPU Taskman a community-focused project with room to grow.

Unlike standard monitoring tools, GPU Taskman combines multiple types of GPU data in one terminal-based interface. It can display VRAM usage, GPU-accessible system memory, process-level GPU activity, and hardware telemetry. This gives users a clearer picture of how their graphics card is behaving under different workloads.

The utility can show key GPU statistics such as utilization, temperature, power draw, clock speeds, memory activity, PCIe information, and per-process GPU resource usage. That makes it useful for anyone trying to understand whether a game, browser, desktop compositor, creative app, or AI tool is responsible for high memory consumption.

One of the most interesting features of GPU Taskman is its focus on local AI workloads. As more users run AI models directly on their own PCs, understanding GPU memory allocation has become increasingly important. Large language models and other AI applications can quickly consume several gigabytes of VRAM, and basic monitoring tools often do not explain why.

GPU Taskman can identify supported AI models and provide additional details about them, including architecture, quantization, parameter count, model weights, and estimated KV-cache requirements. This helps users understand not just how much memory an AI application is using, but what that memory is being used for.

The tool currently recognizes several popular local AI runtimes and applications, including llama.cpp, Ollama, and LM Studio. The amount of information shown may vary depending on the runtime and how much data is available, but the feature is already useful for people experimenting with AI on consumer GPUs.

For example, instead of simply showing that an AI app is using a large amount of VRAM, GPU Taskman can help separate memory used for model weights from memory linked to KV cache and compute buffers. This level of detail can be valuable when choosing model sizes, adjusting context length, or deciding whether a specific GPU has enough memory for a workload.

GPU Taskman gathers information by combining operating system GPU counters with process metadata, model files, runtime logs, and local APIs. However, some AI-related values are estimates rather than exact hardware-level measurements, so users should treat them as helpful guidance rather than perfect readings.

The tool is not only useful for AI developers. PC gamers may also benefit from GPU Taskman when investigating stuttering, poor frame pacing, or performance drops related to memory pressure. When a game runs out of available VRAM, it may rely more heavily on slower system memory, which can contribute to hitching and inconsistent performance.

That said, GPU Taskman does not magically reveal every detail inside a game engine. It cannot identify individual textures, determine exactly which assets have been moved out of VRAM, or prove that GPU-accessible system RAM usage always means VRAM overflow. Still, it can provide more visibility than many users currently have.

GPU Taskman supports NVIDIA and AMD graphics cards on Windows 10 and Windows 11. It also works on Linux, WSL, and Apple Silicon macOS systems, although available features depend on the operating system, GPU vendor, drivers, and hardware capabilities.

Development is moving quickly. Version 0.3.5, released on November 10, added Intel GPU support on Linux, CPU and system RAM monitoring, and more options for recording GPU statistics. These updates suggest the project is expanding beyond basic VRAM tracking into a broader system monitoring tool for GPU-heavy workloads.

GPU Taskman is distributed under the MIT license and is available as experimental open-source software. Portable Windows builds are offered for users who do not want to install Python separately, while Python users can also install it through the standard package ecosystem.

Because the project is still experimental, some features may need more validation across different GPU models, drivers, and platforms. Even so, GPU Taskman already looks promising for PC enthusiasts, AI users, software developers, and gamers who want a better understanding of how their GPU memory and performance resources are being used.