kbcommit in interpreting memory from sar output

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

kbcommit in interpreting memory from sar output

satish
Dear Erman,

We have 1GB of physical memory installed plus 1 GB of swap on the server and this makes the total amount of physical memory to 2GB.

$ sar -r 1 3
Linux 3.2.0-4-686-pae (flames) 22/02/14 _i686_ (2 CPU)

21:44:31 kbmemfr kbmemused %memused kbbuffers kbcached kbcommit %commit kbactive kbinact
21:44:32   16660   1006084    98.37      9504   548592  1388856   68.96   395700  561884
21:44:33   16536   1006208    98.38      9504   548612  1388856   68.96   395700  561872
21:44:34   16536   1006208    98.38      9504   548612  1388856   68.96   395700  561872
Average:   16577   1006167    98.38      9504   548605  1388856   68.96   395700  561876

How exactly can we interpret kbcommmit?
Could you please help us in understanding whether kbcommit will include swap as well?
Will kbcommit include page cache?


Thank you
Reply | Threaded
Open this post in threaded view
|

Re: kbcommit in interpreting memory from sar output

ErmanArslansOracleBlog
Administrator
This is already documented.

kbcommit

Amount of memory in kilobytes needed for current workload. This is an estimate of how much RAM/swap is needed to guarantee that there never is out of memory.