This application allows you to set constraints on a process. It uses a job object for this purpose. The available options are:
Usage: procgov [OPTIONS] [args] Options: -m, --maxmem=VALUE Max committed memory usage in bytes (accepted suffixes: K, M or G). --env=VALUE A text file with environment variables (each line in form: VAR=VAL). Applies only to newly created processes. -c, --cpu=VALUE If in hex (starts with 0x) it is treated as an affinity mask, otherwise it is a number of CPU cores assigned to your app. --nogui Hide Process Governor console window (set always when installed as debugger). -p, --pid=VALUE Attach to an already running process --install Installs procgov as a debugger for a specific process using Image File Executions. --uninstall Uninstalls procgov for a specific process. -h, --help Show this message and exit -? Show this message and exit
REMEMBER to always use procgov with the same bitness as your application.
You may set limits on a newly created process or on an already running one. To attach to a process use the -p|--pid switch, eg.
procgov --maxmem 40M --pid 1234. To start a new process with the limits applied, just pass the process image path and its arguments as procgov arguments, eg.
procgov --maxmem 40M c:\temp\test.exe arg1 arg2".
Finally, it is possible to run procgov always when a given process starts. When you use the --install switch Process Governor will add a special key to the Image File Execution Options in the registry, so that it will always start before your chosen process. To install Process Governor for a test.exe process, use the following command:
procgov --install --maxmem 40M test.exe. You may later remove this installation by using the --uninstall switch, eg.
procgov --uninstall test.exe.
Limit memory of a process
With the --maxmem switch Process Governor allows you to set a limit on a memory committed by a process. On Windows committed memory is actually all private memory that the process uses. This way you may use Process Governor to test your .NET applications (including web applications) for memory leaks. If the process is leaking memory you faster get the OutOfMemoryException.
Limit CPU usage of a process (CPU affinity)
With the --cpu switch you may control on which cores your application will run. If you provide the CPU core number as a decimal value, your application will be allowed to use the specified number of cores. If you provide the CPU core number as a hex value (with 0x prefix), this number will be treated as an affinity mask - where each bit represents a CPU core (starting from the least significant bit). Let's have a look at two example usages on a CPU intensive application. In a first one we set the CPU core limit to two cores:
> procgov --cpu=2 TestLimit.exe
A CPU usage graph on my machine looks as follows:
In a second we set the CPU affinity mask (with the hex notation):
> procgov --cpu=0x2 TestLimit.exe
A CPU graph in this case looks as follows (notice only the second core is used):
Set additional environment variables for a process
With the --env switch you may provide a file with additional environment variables, which should be set for a process. An example usage (provided by @weidingerhp) is to set the COR PROFILING variables:
Below you may find a list of people who contributed to this project. Thank you!
- @weidingerhp - idea of environment variables for a process and CLR profiler setup