Expert help to see what the following description of two VMSTATS
Users questions: 1 VirtualMemoryStatistics:(pagesize=8192)procsmemorypagesintrcpurwuactfreewirefaultcowzeroreactpinp outinsycsussyid4797119179K294K37K87M18M37M013M01745K2K0199 (2) VirtualMemoryStatistics (pageSize = 8192) procsmemorypagesintrcpurwuactfreewirefaultcowzeroreactpinpoutinsycsussyid31K38220K260332K42G257M667M Does anyone know how 1M251M185K64156K81941087 ah? Irrigation do not come, thank you.
Experts answer: This seems to be obtained by running vmstat it, here are some parameters reference. LZ can they understand what vmstat are used to check real-time Look at memory usage, reflecting the situation intuitive than top. If used directly, the current situation can only get the best collection with a time interval in which T vmstatT marked with a specific time, in seconds, for example: vmstat5 form for each collected once every 5 seconds. so that refresh When comparing the system will be able to see that the columns are not normal procs: r **; in the run queue waiting to process the number of b **; the number of processes waiting for io w **; can enter the run queue, but were replaced process memoyswap **; currently available swap memory (k Indicated) free **; free memory (k that) pagesre - "Recycling the pages mf -" non-serious error page pi - "to enter the page number (k that) po -" the page number (k said ) fr - "the number of free pages (k that) de -" provided Front page read misses in the number of sr - "pages scanned by clock algorithm disk shows the disk operations per second. s said scsi disk, disk number 0 fault shows the number of interrupts per second, in - "device interrupts sy -" system outage cy - "cpu cpu swap That cpu's use of state cs - "user process time sy -" the system time used by the process id - "cpu idle time in which: If you r always greater than 4, and id always less than 40, said the cpu's load is heavy. If pi, po term is not equal to 0, Memory. If the disk is often not equal to 0, and b in the queue in the more than 3, indicating poor io performance.