Skip to content
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

ZRAM Optimizations for Odroid XU4/HC1/HC2 #18

Closed

Conversation

ChiefGyk3D
Copy link

@ChiefGyk3D ChiefGyk3D commented Oct 26, 2020

Made tweaks and tested them with Monero being built. Peaked at 1.85GB RAM used of 2GB with 120MB in swap but system was responsive and Monero compilation in 3 hours from forced update. CPU Seemed to be only maxing one core at a time may look into seeing if we can speed build time up just a bit more in other ways see Issue #16 for discussion and reasoning

@ChiefGyk3D ChiefGyk3D changed the base branch from master to Armbian-install October 26, 2020 03:48
@ChiefGyk3D
Copy link
Author

Tested and confirmed to work on Odroid XU4 platforms wonderfully and still going

Copy link
Owner

@shermand100 shermand100 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, let's get this included. I like the idea.

Because it's tested on the Odroid XU4/HC1/HC2 can you add in another whiptail dialog box that gives the user a choice. Something like:

"Memory optimisations are available for Odroid systems, would you like to apply them" Yes/No

YES:
echo "vm.vfs_cache_pressure=500" | sudo tee -a /etc/sysctl.conf
echo "vm.dirty_background_ratio=1" | sudo tee -a /etc/sysctl.conf
echo "vm.dirty_ratio=50" | sudo tee -a /etc/sysctl.conf
sudo sysctl -p

NO:
sudo sysctl vm.swappiness=10

Bump 24/01/22 @ChiefGyk3D

@shermand100 shermand100 deleted the branch shermand100:Armbian-install August 3, 2023 12:23
@shermand100 shermand100 closed this Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants