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

CPU limit penalizes parallel GC #44

Open
wingo opened this issue Aug 19, 2019 · 2 comments
Open

CPU limit penalizes parallel GC #44

wingo opened this issue Aug 19, 2019 · 2 comments

Comments

@wingo
Copy link
Contributor

wingo commented Aug 19, 2019

The CPU limit in the bench script is 300 seconds of CPU time (5 minutes). Compilation has 5 minutes, then running has 5 minutes. But unfortunately this penalizes parallelization, whose goal is usually to minimize wall-clock time rather than CPU time; and the end result of the benchmarking process is wall-clock time. Of course this result is worse the more cores you have.

I think Guile has hit this limit in ctak at run-time, and now that some optimizations allow for better visibility into compile, we hit it there at compile-time as well.

I think the limit should be raised to 15 minutes. It's a decent trade-off between the concern of wanting short benchmark runs and allowing for parallelism in GC.

wingo added a commit to wingo/guile-benchmarks that referenced this issue Aug 28, 2019
@ecraven
Copy link
Owner

ecraven commented Jul 29, 2024

Does anyone know whether there's a simple way to limit wall-clock time, not user time?

@lockbox
Copy link

lockbox commented Aug 17, 2024

could https://linux.die.net/man/1/timeout help here? (probably not going to be entirely as precise as ulimit but may work well enough)

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

3 participants