SWAP_FREE_BYTES 17,145,614,336 17,145,872,384 BUSY_TIME 1,305,569,937 IDLE_TIME 4,312,718,839 IOWAIT_TIME 53,417,174 NICE_TIME 29,815 SYS_TIME 148,567,570 USER_TIME 1,146,918,783 LOAD 25 29 VM_IN_BYTES 593,920 VM_OUT_BYTES ...
(cpu use, virtual memory, hardware config), name statistic value end value free_memory_bytes 921,088,000 907,710,464 inactive_memory_bytes 1,740,865,536 1,696,837,632 swap_free_bytes 2,097,147,904 busy_time 2,240 idle_time 177,120 iowait_time 1,925 sys_time ...
(1)swpd :如果 swap 的值不为 0,或者比较大,比如超过 100 MB ,但是 si 和 so 的值长期为 0,这种情况不会影响系统性能。 (2)free :空闲内存 (free) 很少或接近于 0 时,并不能认定为内存不够用,Linux 是抢占内存的 OS,还要结合 si 和 so;如果 free 很少,si 和 so 也很少(大多时候是 0),系统性...
GET_TOTAL_MEMORY_SQL="SELECT sys.format_bytes(sum(CURRENT_NUMBER_OF_BYTES_USED)) AS MEMORY_USED FROM performance_schema.memory_summary_global_by_event_name LIMIT 250;" GET_EVENT_MEMORY_SQL="SELECT event_name,sys.format_bytes(CURRENT_NUMBER_OF_BYTES_USED) AS MEMORY FROM performance_schema.mem...
CPU states: 35.2% idle, 40.1% user, 9.4% kernel, 15.4% iowait, 0.0% swap Memory: 3072M real, 286M free, 3120M swap in use, 1146M swap free PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND 11855 smspf 1 59 0 1355M 1321M cpu/0 19:32 16.52% oracle ...
End Value is displayed if different • rdered by statistic type (CPU Use, Virtual Mem ry, Hardware C nfig), Name Statistic Value End Value FREE_MEMORY_BYTES 921,088,000 907,710, 6 INACTIVE_MEMORY_BYTES 1,7 0,865,536 1,696,837,632 SWAP FREE BYTES 2,097,1 7,90 BUSY_TIME 2,2...
1146M swap free PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND 11855 smspf 1 59 0 1355M 1321M cpu/0 19:32 16.52% oracle 2264 oracle 1 0 0 1358M 1316M run 283.3H 16.36% oracle 11280 oracle 1 13 0 1356M 1321M sleep 79.8H 0.77% oracle21043 oracle 1 43 0 3264K 2056...
my ( $filesystem, $totalmb, $usedmb, $freemb, $usedpct, $mountpoint ); my $snap_id; my $snap_time; # Get options info &get_options(); &get_loadinfo(); &get_diskinfo(); &get_cpuinfo(); &get_swapinfo();
Swap: 33551744k total, 115632k used, 33436112k free, 13809040k cached 可以看到CPU的使用率虽高,但是IO却几乎没有什么消耗。 然后查看部分的进程信息,发现有部分的进程CPU使用率较高。这个时候看起来是一个全表扫描的概率偏大了。 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND ...
(cpu use, virtual memory, hardware config), name statistic value end value free_memory_bytes 921,088,000 907,710,464 inactive_memory_bytes 1,740,865,536 1,696,837,632 swap_free_bytes 2,097,147,904 busy_time 2,240 idle_time 177,120 iowait_time 1,925 sys_time...