Find the project
using all that RAM.
A dev server can keep using memory long after you switch tasks. See CPU and RAM by project, follow the process tree, and stop what you’ve finished with.
macOS + Windows. Pay once. Future updates included.
Know what your projects are using.
A busy dev machine can hide a lot behind a process name. Pip puts resource usage in the context of your projects. Follow live CPU and memory charts, inspect the process tree, and decide which servers still need a place on your machine.
- between CPU and memory samples
- 1.5s
- live resource readings
- CPU + RAM
- see the work behind each server
- Process trees
Read memory in useful terms.
See a project’s memory usage as both an absolute amount and a share of your machine. An amber reading helps draw attention to a busy process.
Follow more than one moment.
Live charts show CPU and memory alongside peaks, averages and memory drift per minute, helping you spot usage that keeps climbing.
Release resources when you’re done.
Inspect the server’s process tree, then stop an unneeded server and its child processes. Elevated processes are marked when Pip can’t stop them.
Find the server you can close.
Read about live server statsLook at your running projects.
Start with the server list to see which projects are using memory and how much of your machine they account for.
Open the live stats.
Follow CPU and memory over time, inspect the process tree, and check peaks, averages and memory drift.
Close what you no longer need.
Stop an unneeded server to release its resources, then watch the updated readings as you return to your work.
Make sense of the changing numbers.
A resource reading is more useful when you know what it represents. Here’s how to interpret the timing, memory figures and trends while a server is running.
- Why are there two memory figures for one project?
- Pip shows memory as an absolute amount and as a percentage of your machine’s memory. The percentage helps you judge how much of the machine that project occupies; the absolute figure makes its size easier to compare with other projects. They’re two views of the same usage, so you don’t add them together.
- Why do resource readings update before the server list changes?
- Server detection runs every five seconds, while CPU and memory are sampled every 1.5 seconds. That lets the resource readings change more often than projects appear or disappear from the list. After starting or stopping a server, allow the next detection scan to catch up with the change you just made.
- Does increasing memory usage mean my server has a leak?
- The Stats tab shows live memory alongside peaks, averages and a drift figure per minute. Those readings help you notice memory that keeps climbing and decide which server deserves a closer look. A rising line describes the behaviour you’re seeing; it doesn’t identify the cause on its own. The process tree adds context for that investigation.
Make room for the work you’re doing next.
Every Pip tool. $29 USD, once. One machine at a time.