Measures the stutter. Removes it.
Marshal watches how fast the app you are using responds. The moment it starts to hitch, background CPU hogs get throttled.
Small tool. Sharp control.
One window, one job. Everything below is in the build you download today.
Adaptive taming
Marshal pings the window you are working in and times the reply. A healthy app answers in well under a millisecond, a starved one takes tens. Only when that number climbs past your threshold does anything get throttled, so a long compile or export runs at full speed until the moment it actually costs you.
Priority and affinity
Set any process to a priority class by hand, or pin it to specific cores. IdleBelow normalNormalHighRealtime
Rules that stick
Pin a priority or a core mask to a process by name. Marshal reapplies it every time that process appears, including after a reboot, and steps aside for anything AutoTame is currently holding.
Gaming Mode
One toggle: performance power plan, tighter thresholds, and the focused game boosted to High. Your games list is exempt from throttling even when you alt-tab away, which is exactly when naive tools get it wrong.
Puts everything back
Every priority Marshal changes and the power plan it found are journaled to disk. If it is killed mid-flight, the next launch reconciles that journal and restores what was there. Nothing is left changed behind your back.
A process table you can read
CPU, memory, PID and priority class on your own refresh interval, with per-process trend sparklines and a column picker that remembers what you chose. Sampling is raw Win32 rather than a crate, which is why the whole binary is 11 MB with no runtime to install.
Throttling everything is easy.
Knowing when to is the hard part.
Most tools throttle on a CPU percentage alone, which punishes your own background work for existing. Marshal asks a different question first.
Ask the app, do not guess
Every tick, Marshal sends the active window a message and times how long the reply takes. That round trip is the only honest measure of whether you are being made to wait.
While it is smooth, do nothing
A responsive app answers in about a millisecond. Below your threshold Marshal leaves every background process completely alone, so your render, compile or backup keeps all the CPU it can get.
Watch the number climb
When something starts taking cores away from the foreground, the reply time rises. Marshal waits for that to hold, so one unlucky frame is never enough to trigger it.
Throttle the culprits, not the list
Now the CPU floor decides who. Background processes above it drop to a lower priority class. The app you are using gets the cores back, usually within a second.
Give it all back
Once the reply time settles, every throttled process returns to the priority it had. Nothing is left changed behind your back, and the log records each step.
Three tools, one idea
Small native Windows utilities that measure something precisely and then act on it. Same build, same look, no installers.
Marshal
Watches how responsive the active app is and throttles whatever is starving it.
You are hereDisk usage as a treemap, plus a Changes view that answers why the drive filled up since last scan.
quarry.aimbetween.games SiftInstant file search straight off the NTFS index, and a content: query that searches inside your files.
sift.aimbetween.gamesGet Marshal for Windows
One executable. Run it and it works. Uninstalling is deleting the file.
Marshal is unsigned, so SmartScreen may warn on first launch: choose More info, then Run anyway. Verify the download against the checksum if you like. Changing priorities on processes owned by other users needs Administrator.