-
-
Notifications
You must be signed in to change notification settings - Fork 461
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]hope to add an option: Clean up when the Standby Memory percentage threshold reaches a certain value #265
Comments
in English or Russian plz
|
Hello herypp! |
Sorry, my browser translation plugin has restored automatic translation of my English and uploaded it 😭 |
Could you provide some technical details about the device? That might help in understanding the issue better. |
My computer configuration |
From what I understand, you want the available memory calculation to be customizable so that it can be based specifically on standby memory instead of total memory. A checkbox list to select which memory regions to include in the calculation would allow for this flexibility. This way, you could see available memory based only on standby memory if needed. That makes sense—it would be a useful feature! |
Checklist
App version
3.5.1
Problem you are trying to solve
Hello herypp!
My device often experiences significant lag when using software due to Standby Memory occupying all available memory space. However, in reality, the memory usage during use usually does not exceed 40%, and Standby Memory usage exceeds 60%. Therefore, the percentage of memory usage during use cannot truly reflect the memory usage of my device. Even if 20% of the memory is in use, it is possible for the device to experience abnormal lag due to up to 80% of Standby Memory usage.
So I had to use mem reduce to clean the Standby list every 5-30 minutes,
Suggested solution
I think mem reduce can add an option to detect the percentage of Standby Memory usage to automatically clean it up
Screenshots / Drawings / Technical details
No response
The text was updated successfully, but these errors were encountered: