# 30min\_ram\_swapped\_out **URL:** \ **Category:** Alerts\ **Created:** [November 3, 2021, 4:55pm UTC](https://community.netdata.cloud/t/30min-ram-swapped-out/1946 "2021-11-03T16:55:24Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Tasos\_Katsoulas](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/tasos_katsoulas/32/1344_2.png) [@Tasos\_Katsoulas](https://community.netdata.cloud/u/Tasos_Katsoulas)\ **Post date:** [November 3, 2021, 4:55pm UTC](https://community.netdata.cloud/t/30min-ram-swapped-out/1946/1 "2021-11-03T16:55:24Z")
# 30min\_ram\_swapped\_out If the system needs more memory resources than your available RAM, inactive pages in memory can be moved into the swap space (or swap file). The swap space (or swap file) is located on hard drives, which have a slower access time than physical memory. The Netdata Agent calculates the percentage of the system RAM swapped in the last 30 minutes. This alert is triggered in warning state if the percentage of the system RAM swapped in is more than 30%. ## OS: Linux ### Troubleshooting section: You can find the most resource greedy processes in your system, but if you receive this alert many times you must consider upgrade your system’s RAM. > **Find the processes that consume the most RAM** > > 1. Use `top` to see the top RAM consumers > > ```auto > root@netdata~ # top -b -o +%MEM | head -n 22 > > ``` > > Here, you can see which processes are the main RAM consumers on the `%MEM` column (it is calculated > in percentage). It would be wise to close/kill any of the main consumer processes that you do not > need to avoid thrashing, though Netdata strongly suggests knowing exactly what processes you are closing > and being certain that they are not necessary. ## OS: FreeBSD ### Troubleshooting section: You can find the most resource greedy processes in your system, but if you receive this alert many times you must consider upgrade your system’s RAM. > **Find the processes that consume the most RAM** > > 1. Use `top` to see the top RAM consumers > > ```auto > root@netdata~ # top -b -o res | head -n 22 > > ``` > > Here, you can see which processes are the main RAM consumers on the `RES` column (calculated in > bytes). It would be wise to close/kill any of the main consumer processes that you do not need > to avoid thrashing, though Netdata strongly suggests knowing exactly what processes you are closing > and being certain that they are not necessary.