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

Evaluate performance penalty of the recommended kernel options #66

Open
a13xp0p0v opened this issue Jul 3, 2022 · 2 comments
Open

Evaluate performance penalty of the recommended kernel options #66

a13xp0p0v opened this issue Jul 3, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@a13xp0p0v
Copy link
Owner

As the first step, @BlackIkeEagle made some performance tests and described the results in this article.

@a13xp0p0v a13xp0p0v added the enhancement New feature or request label Jul 3, 2022
@a13xp0p0v
Copy link
Owner Author

a13xp0p0v commented Dec 8, 2022

Create a solution for automating this process:

  1. Take defconfig as a basic kernel configuration.
  2. Build the Linux kernel.
  3. Start test system with this kernel (a hardware machine may give more consistent results than a virtual machine). If the system doesn't boot, go to step 6.
  4. Run the chosen performance tests (hackbench, kernel compilation, network throughput evaluation, etc).
  5. Save the test results.
  6. Set another kernel option from the kconfig-hardened-check json output and go to step 2 (see Create a tool that changes kconfig options according to the recommendations #67). If all recommendations are already tested, then proceed to step 7.
  7. Analyze the results of the performance testing.

That approach would save us from plenty of boring manual routine.

@a13xp0p0v
Copy link
Owner Author

Similar performance testing of a group of security hardening options may give interesting results as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant