This module provides basic mechanisms for measuring and controlling system resources utilized by a program.
Symbolic constants are used to specify particular system resources and to request usage information about either the current process or its children.
A single exception is defined for errors:
The functions described below may raise this error if the underlying system call failures unexpectedly.
Resources usage can be limited using the
setrlimit() function described below. Each resource is controlled by a pair of limits: a soft limit and a hard limit. The soft limit is the current limit, and may be lowered or raised by a process over time. The soft limit can never exceed the hard limit. The hard limit can be lowered to any value greater than the soft limit, but not raised. (Only processes with the effective UID of the super-user can raise a hard limit.)
The specific resources that can be limited are system dependent. They are described in the getrlimit(2) man page. The resources listed below are supported when the underlying operating system supports them; resources which cannot be checked or controlled by the operating system are not defined in this module for those platforms.
Constant used to represent the limit for an unlimited resource.
Sets new limits of consumption of resource. The limits argument must be a tuple
(soft, hard) of two integers describing the new limits. A value of
RLIM_INFINITY can be used to request a limit that is unlimited.
ValueError if an invalid resource is specified, if the new soft limit exceeds the hard limit, or if a process tries to raise its hard limit. Specifying a limit of
RLIM_INFINITY when the hard or system limit for that resource is not unlimited will result in a
ValueError. A process with the effective UID of super-user can request any valid limit value, including unlimited, but
ValueError will still be raised if the requested limit exceeds the system imposed limit.
setrlimit may also raise
error if the underlying system call fails.
These symbols define resources whose consumption can be controlled using the
getrlimit() functions described below. The values of these symbols are exactly the constants used by C programs.
The Unix man page for getrlimit(2) lists the available resources. Note that not all systems use the same symbol or same value to denote the same resource. This module does not attempt to mask platform differences — symbols not defined for a platform will not be available from this module on that platform.
The maximum size (in bytes) of a core file that the current process can create. This may result in the creation of a partial core file if a larger core would be required to contain the entire process image.
The maximum amount of processor time (in seconds) that a process can use. If this limit is exceeded, a
SIGXCPU signal is sent to the process. (See the
signal module documentation for information about how to catch this signal and do something useful, e.g. flush open files to disk.)
The maximum size of a file which the process may create.
The maximum size (in bytes) of the process’s heap.
The maximum size (in bytes) of the call stack for the current process. This only affects the stack of the main thread in a multi-threaded process.
The maximum resident set size that should be made available to the process.
The maximum number of processes the current process may create.
The maximum number of open file descriptors for the current process.
The BSD name for
The maximum address space which may be locked in memory.
The largest area of mapped memory which the process may occupy.
The maximum area (in bytes) of address space which may be taken by the process.
These functions are used to retrieve resource usage information:
This function returns an object that describes the resources consumed by either the current process or its children, as specified by the who parameter. The who parameter should be specified using one of the
RUSAGE_* constants described below.
The fields of the return value each describe how a particular system resource has been used, e.g. amount of time spent running is user mode or number of times the process was swapped out of main memory. Some values are dependent on the clock tick internal, e.g. the amount of memory the process is using.
For backward compatibility, the return value is also accessible as a tuple of 16 elements.
ru_stime of the return value are floating point values representing the amount of time spent executing in user mode and the amount of time spent executing in system mode, respectively. The remaining values are integers. Consult the getrusage(2) man page for detailed information about these values. A brief summary is presented here:
| || ||time in user mode (float)|
| || ||time in system mode (float)|
| || ||maximum resident set size|
| || ||shared memory size|
| || ||unshared memory size|
| || ||unshared stack size|
| || ||page faults not requiring I/O|
| || ||page faults requiring I/O|
| || ||number of swap outs|
| || ||block input operations|
| || ||block output operations|
| || ||messages sent|
| || ||messages received|
| || ||signals received|
| || ||voluntary context switches|
| || ||involuntary context switches|
Changed in version 2.3: Added access to values as attributes of the returned object.
Returns the number of bytes in a system page. (This need not be the same as the hardware page size.)
RUSAGE_* symbols are passed to the
getrusage() function to specify which processes information should be provided for.
RUSAGE_SELF should be used to request information pertaining only to the process itself.
getrusage() to request resource information for child processes of the calling process.
getrusage() to request resources consumed by both the current process and child processes. May not be available on all systems.
© 2001–2017 Python Software Foundation
Licensed under the PSF License.