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

This makes more sense as a repo of shell scripts #2

Open
gardotd426 opened this issue Sep 6, 2024 · 2 comments
Open

This makes more sense as a repo of shell scripts #2

gardotd426 opened this issue Sep 6, 2024 · 2 comments

Comments

@gardotd426
Copy link

Just create folders for IO, RAM, Filesystems, CPU governing and scheduling, etc, and have each one contain scripts of the command blocks listed.

Or, create one large script that's interactive and asks the user before each step.

This is the 4th attempt at an Ultimate Linux Gaming Optimization Database I've seen attempted in the past few years, and they never help anyone cause anyone willing to get this granular already knows most of it and can find all of it in seconds on their own.

Maybe work with the developer of Fastgame on adding some of your tips to his GUI app. Go check it out, its rather amazing. https://github.com/wwmm/fastgame

@jazir555
Copy link
Owner

jazir555 commented Sep 6, 2024

@arunk140

I've just merged the .md file, I greatly appreciate @quartz270 taking the time to format this.

@jazir555
Copy link
Owner

jazir555 commented Sep 6, 2024

This makes more sense as a repo of shell scripts

Once there's more clarification from the community of which commands do and don't work I will absolutely compile the beneficial commands into a script file so they can be applied all at once.

I don't want to create them yet as I'm sure something in this giant batch has the potential to hurt performance given the emphatic responses on the Reddit post which indicated the potential of that, so I'd rather not have all of the changes these commands applied in one shot until I can weed out the potentially detrimental ones.

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

No branches or pull requests

2 participants