Hello,
I'm running into some confusion with the output of arcstat.py. As I understand it, at the tail end of the output arcsz is the current size of the ARC, and c is the ARC maximum size.
arcsz is never larger than c, which leads me to believe that c is the max. But I don't understand what would make the ARC max change size. The reason this becomes a problem is because that number gets as low as 50M. I need to figure out why.
This is Proxmox 4.4-18.
I'm running into some confusion with the output of arcstat.py. As I understand it, at the tail end of the output arcsz is the current size of the ARC, and c is the ARC maximum size.
Code:
root@myprox:~# arcstat.py 1
time read miss miss% dmis dm% pmis pm% mmis mm% arcsz c
17:31:19 3 3 100 3 100 0 0 1 100 3.7G 3.7G
17:31:20 2.3K 467 20 434 18 33 76 10 58 3.7G 3.7G
17:31:21 1.1K 791 71 502 62 289 98 8 38 3.7G 3.7G
17:31:22 1.3K 832 63 468 50 364 92 38 20 3.7G 3.7G
17:31:23 1.9K 1.2K 66 643 51 598 97 28 11 3.5G 3.5G
17:31:24 2.2K 749 34 515 27 234 72 33 26 3.5G 3.5G
17:31:25 2.1K 1.0K 50 446 31 595 93 32 8 3.5G 3.5G
17:31:26 1.6K 880 54 862 53 18 66 34 82 3.5G 3.5G
17:31:27 2.8K 1.5K 53 663 37 824 83 31 7 3.5G 3.5G
17:31:28 2.8K 1.4K 50 460 26 971 86 41 6 3.5G 3.5G
17:31:29 1.1K 775 68 697 66 78 93 31 58 3.5G 3.5G
17:31:30 1.8K 733 41 519 34 214 84 23 17 3.5G 3.5G
17:31:31 2.7K 825 30 467 22 358 59 24 8 3.5G 3.5G
17:31:32 1.5K 722 47 615 49 107 38 16 11 3.5G 3.5G
17:31:33 2.1K 1.2K 57 450 34 761 95 20 4 3.6G 3.6G
arcsz is never larger than c, which leads me to believe that c is the max. But I don't understand what would make the ARC max change size. The reason this becomes a problem is because that number gets as low as 50M. I need to figure out why.
This is Proxmox 4.4-18.