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

BOINC uses slow cores #1462

Closed
davidpanderson opened this issue Jan 7, 2016 · 3 comments
Closed

BOINC uses slow cores #1462

davidpanderson opened this issue Jan 7, 2016 · 3 comments

Comments

@davidpanderson
Copy link
Contributor

(from a user email)
I noticed that BOINC can't use 2, 4 and 6 cores together and instead to use the first two cores (1.8 GHz), it uses the last four (1.44 GHz) when I select "1 core", that should activate only in stressed conditions. Please solve this problem

@ChristianBeer
Copy link
Member

This most likely refers to certain ARM CPUs that have fast cores and slow cores.

@Ferroin
Copy link

Ferroin commented Apr 11, 2017

If it's Android or just regular Linux, then it's probably not BOINC but the OS level process scheduler. Linux's scheduler is smart enough (when built with the right options) to put low priority tasks on less powerful (more correctly, more energy-efficient) cores, and short of manipulating it's own CPU affinity (which can't be done on Android, but I would love to have support for for other reasons), there's not really much BOINC could do about this.

@brevilo brevilo added this to Longterm in Android Apr 19, 2017
@brevilo brevilo removed this from Longterm in Android Apr 19, 2017
@Ageless93 Ageless93 added this to Backlog in Client and Manager via automation Nov 11, 2017
@JuhaSointusalo
Copy link
Contributor

Duplicate of #2549

@JuhaSointusalo JuhaSointusalo marked this as a duplicate of #2549 Jul 11, 2018
Client and Manager automation moved this from Backlog to Done Jul 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

4 participants