-
Notifications
You must be signed in to change notification settings - Fork 58
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
Add compilers.rules #80
Conversation
We have explicity removed compiler, because when it spawns many tasks/threads, ananicy-cpp will quite much cpu power at some point. |
On my testing, it got completely fixed on BORE +4.5.2 with -9, -1, 1, 5, 10, and 19 niceness values with the scan interval set to 1 second. |
It should be stable on nice 10 and 19. |
Maybe linkers, like lld, ld, ld.bfd, mold can be also added. |
We should also check, if this brings a noticeable performance regression. |
b877dc5
to
d5f49e6
Compare
Added. Seems fine on my end, then again, it should be tested by the reviewers. |
2fd8f7f
to
b60161d
Compare
@aarrayy |
What kind of testing? How much time does it adds? or... |
Likely if BORE shows issue together with it again. |
I currently use 10 and its fine on my system, it leaves room for multitasking without hurting too much the build process itself, for example web browsing while compiling the linux kernel with thin lto i got a total time of 22 mins |
Sure, i'll do some testing with 13 and 9 |
I agree. Though I am using 9 on normal cachyos kernel with sched-ext rustland |
Ill also need to do in the coming days some throughput tests, since ananicy-cpp uses quite much cpu time, when applying this compiler rules |
BORE is totally fine with any nice value, on 4.5.2 i tested from 1, 3, 6, 9, 12, 19 and couldn't manage to get a lockup and ananicy is set to an scan interval of 1 second so it has to happen no matter what, 5.0.3 is the same history Passed on 10 and 13 |
there is no scan interval. it does push into buffer on every sched_process_exec and sched_process_fork. the poll from that buffer is done "non-stop" with non-configurable timeout of 500ms |
I was referring to check_freq in ananicy.conf that by default is set to 15 seconds and i personally use 1 second |
thats only for when flag |
Oh. |
So... should I modify the config "nice" "latency-nice" to 13 in this PR? |
C and C++, Go, Java, and Rust compilers are added Also added Bazel, Cmake, Ninja, and Meson build systems
Change to uppercase Compiler
b60161d
to
291598a
Compare
@aarrayy @ptr1337 I have been daily driving at 13 nice for two weeks now. It stays stable on high load. Waiting for your final approval :) |
I approve these rules, i haven't had any lockup with any nice value since BORE +4.5.2 |
C and C++, Go, Java, and Rust compilers are added
Also added Bazel, Cmake, Ninja, and Meson build systems