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

Various sysctl cleanups #107

Merged
merged 6 commits into from
Nov 26, 2024
Merged

Various sysctl cleanups #107

merged 6 commits into from
Nov 26, 2024

Conversation

1Naim
Copy link
Member

@1Naim 1Naim commented Oct 24, 2024

Currently there seems to be a bit of a redundancy in the settings set here, so I'd like to clean it up a bit. There are also some removals/tweaks to settings that don't make quite sense to me (based on my limited knowledge), so I've opted to removed them in the PR, but I am very open for discussion.

This is already set by Arch via `/usr/lib/sysctl.d/10-arch.conf` from the `filesystem` package.

Signed-off-by: Eric Naim <[email protected]>
According to [Arch Wiki](https://wiki.archlinux.org/title/Sysctl#Increase_the_maximum_connections) this only helps
on high-loaded servers. Desktops won't become high-loaded servers ever probably, so on the basis of that knowledge remove this.

If increasing this value does indeed has tangible benefits, I can revert this.

Signed-off-by: Eric Naim <[email protected]>
Copy link
Member Author

@1Naim 1Naim left a comment

Choose a reason for hiding this comment

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

Guess I can't add further snippet reviews so I'll add it here

# This tunable is used to define when dirty data is old enough to be eligible for writeout by the
# kernel flusher threads.  It is expressed in 100'ths of a second.  Data which has been dirty
# in-memory for longer than this interval will be written out next time a flusher thread wakes up
# (Default is 3000).
#vm.dirty_expire_centisecs = 3000

We are also not setting this.

# Only experimental!
# Let Realtime tasks run as long they need
# sched: RT throttling activated
kernel.sched_rt_runtime_us=-1

I'm skeptical about this, maybe we can set it to a higher predefined value than the default instead?

usr/lib/sysctl.d/99-cachyos-settings.conf Outdated Show resolved Hide resolved
We already have this set in the kernel, and having a duplicate here can cause instances when users want to test
the default algorithm in another kernel, but will still have BBR set.

Signed-off-by: Eric Naim <[email protected]>
@1Naim 1Naim marked this pull request as ready for review November 22, 2024 16:25
@1Naim 1Naim requested a review from ventureoo November 22, 2024 16:27
@1Naim
Copy link
Member Author

1Naim commented Nov 25, 2024

This PR seems finished now. @ventureoo when you have the time, it would be nice for this to go through one more review before merging.

This has always been commented. Even if not, the value set is the same as the kernel default. Unless we want
to tweak the value, keeping this here is redundant.

Signed-off-by: Eric Naim <[email protected]>
This is the default value. No reason to enforce a default, especially if its in a package where it can be
overrided anyway from /etc or from cmdline.

Signed-off-by: Eric Naim <[email protected]>
Copy link
Member

@ventureoo ventureoo left a comment

Choose a reason for hiding this comment

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

LGTM

@ptr1337 ptr1337 merged commit ab0dcb2 into master Nov 26, 2024
@ptr1337 ptr1337 deleted the chore/sysctl-cleanup branch November 26, 2024 18:15
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.

4 participants