[riot-notifications] [RIOT] make: limit max system load for buildtests (#3267)
notifications at github.com
Sun Jun 28 19:41:52 CEST 2015
Avg load should be chosen according to the number of processors in the
system. A system with one single core CPU is fully loaded at avg load 1.0.
A load average of 30 is quite a lot for most desktop systems even today,
but it might be fine for some 16 core server though.
Maybe a lower default would be wise and let the users who have access to
powerful servers increase it instead of over loading more common systems.
What do you think?
On Jun 28, 2015 7:10 PM, "Philipp Rosenkranz" <notifications at github.com>
> Currently, the buidtest target executes #(virtual) CPU core + 1 tasks
> when started. This number can be reduced by setting the NPROC env
> However, it may make sense to dynamically increase or decrease this number
> according to the
> average system load.
> This PR allows a user (or a CI system) to set a maximum average system
> load via the env variable MAKE_MAXLOAD which will be honored by make.
> This is especially useful when:
> - multiple buildtests are executed on the same machine (otherwise you
> will end up with a system load near 30...).
> - a user wants to ensure that a buildtest running on their dev machine
> doesn't hog all the CPU resources
> Regarding the maximum average load I am not sure. For now I choose 30.
> You can view, comment on, or merge this pull request online at:
> Commit Summary
> - make: limit max system load for buildtests
> File Changes
> - *M* Makefile.buildtests
> <https://github.com/RIOT-OS/RIOT/pull/3267/files#diff-0> (6)
> Patch Links:
> - https://github.com/RIOT-OS/RIOT/pull/3267.patch
> - https://github.com/RIOT-OS/RIOT/pull/3267.diff
> Reply to this email directly or view it on GitHub
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications