Monitoring Resource Utilization With rcapstat - System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones

Skip Navigation Links
Exit Print View
	System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones

Oracle Technology Network

Document Information

Part I Resource Management

1. Introduction to Solaris 10 Resource Management

2. Projects and Tasks (Overview)

3. Administering Projects and Tasks

4. Extended Accounting (Overview)

5. Administering Extended Accounting (Tasks)

6. Resource Controls (Overview)

7. Administering Resource Controls (Tasks)

8. Fair Share Scheduler (Overview)

9. Administering the Fair Share Scheduler (Tasks)

10. Physical Memory Control Using the Resource Capping Daemon (Overview)

What's New in Physical Memory Control Using the Resource Capping Daemon?

Introduction to the Resource Capping Daemon

How Resource Capping Works

Attribute to Limit Physical Memory Usage for Projects

rcapd Configuration

Using the Resource Capping Daemon on a System With Zones Installed

Memory Cap Enforcement Threshold

Determining Cap Values

rcapd Operation Intervals

Determining rcapd Scan Intervals

Determining Sample Intervals

Monitoring Resource Utilization With rcapstat

Commands Used With rcapd

11. Administering the Resource Capping Daemon (Tasks)

12. Resource Pools (Overview)

13. Creating and Administering Resource Pools (Tasks)

14. Resource Management Configuration Example

15. Resource Control Functionality in the Solaris Management Console

16. Introduction to Solaris Zones

17. Non-Global Zone Configuration (Overview)

18. Planning and Configuring Non-Global Zones (Tasks)

19. About Installing, Halting, Cloning, and Uninstalling Non-Global Zones (Overview)

20. Installing, Booting, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks)

21. Non-Global Zone Login (Overview)

22. Logging In to Non-Global Zones (Tasks)

23. Moving and Migrating Non-Global Zones (Tasks)

24. Solaris 10 9/10: Migrating a Physical Solaris System Into a Zone (Tasks)

25. About Packages and Patches on a Solaris System With Zones Installed (Overview)

26. Adding and Removing Packages and Patches on a Solaris System With Zones Installed (Tasks)

27. Solaris Zones Administration (Overview)

28. Solaris Zones Administration (Tasks)

29. Upgrading a Solaris 10 System That Has Installed Non-Global Zones

30. Troubleshooting Miscellaneous Solaris Zones Problems

Part III lx Branded Zones

31. About Branded Zones and the Linux Branded Zone

32. Planning the lx Branded Zone Configuration (Overview)

33. Configuring the lx Branded Zone (Tasks)

34. About Installing, Booting, Halting, Cloning, and Uninstalling lx Branded Zones (Overview)

35. Installing, Booting, Halting, Uninstalling and Cloning lx Branded Zones (Tasks)

36. Logging In to lx Branded Zones (Tasks)

37. Moving and Migrating lx Branded Zones (Tasks)

38. Administering and Running Applications in lx Branded Zones (Tasks)

Monitoring Resource Utilization With `rcapstat`

Use rcapstat to monitor the resource utilization of capped projects. To view an example rcapstat report, see Producing Reports With rcapstat.

You can set the sampling interval for the report and specify the number of times that statistics are repeated.

interval: Specifies the sampling interval in seconds. The default interval is 5 seconds.
count: Specifies the number of times that the statistics are repeated. By default, rcapstat reports statistics until a termination signal is received or until the rcapd process exits.

The paging statistics in the first report issued by rcapstat show the activity since the daemon was started. Subsequent reports reflect the activity since the last report was issued.

The following table defines the column headings in an rcapstat report.

`rcapstat` Column Headings	Description
`id`	The project ID of the capped project.
`project`	The project name.
`nproc`	The number of processes in the project.
`vm`	The total amount of virtual memory size used by processes in the project, including all mapped files and devices, in kilobytes (K), megabytes (M), or gigabytes (G).
`rss`	The estimated amount of the total resident set size (RSS) of the processes in the project, in kilobytes (K), megabytes (M), or gigabytes (G), not accounting for pages that are shared.
`cap`	The RSS cap defined for the project. See Attribute to Limit Physical Memory Usage for Projects or the `rcapd`(1M) man page for information about how to specify memory caps.
`at`	The total amount of memory that `rcapd` attempted to page out since the last `rcapstat` sample.
`avgat`	The average amount of memory that `rcapd` attempted to page out during each sample cycle that occurred since the last `rcapstat` sample. The rate at which `rcapd` samples collection RSS can be set with `rcapadm`. See `rcapd` Operation Intervals.
`pg`	The total amount of memory that `rcapd` successfully paged out since the last `rcapstat` sample.
`avgpg`	An estimate of the average amount of memory that `rcapd` successfully paged out during each sample cycle that occurred since the last `rcapstat` sample. The rate at which `rcapd` samples process RSS sizes can be set with `rcapadm`. See `rcapd` Operation Intervals.

Copyright © 2004, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices

Previous

Next