Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1037466 - BOINC ignores CPU usage and runs all the time
Summary: BOINC ignores CPU usage and runs all the time
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: boinc-client
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milos Jakubicek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1039258
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-03 08:58 UTC by Vratislav Podzimek
Modified: 2015-06-30 00:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:45:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot of the running top utility (301.51 KB, image/png)
2014-01-08 16:07 UTC, Vratislav Podzimek
no flags Details
computing preferences (1.13 MB, image/png)
2014-01-08 16:08 UTC, Vratislav Podzimek
no flags Details
screenshot showing exclusive app (xchat) restriction doesn't work (571.68 KB, image/png)
2014-01-08 16:09 UTC, Vratislav Podzimek
no flags Details

Description Vratislav Podzimek 2013-12-03 08:58:09 UTC
Description of problem:
No matter how I setup computing preferences, the boinc-client and its tasks run all the time even with high CPU usage.

Version-Release number of selected component (if applicable):
boinc-client-7.0.65-2.git79b00ef.fc20.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. set computing preferences to stop computing at e.g. 15% CPU usage
2. put some heavy load on the CPU
3. run the top utility

Actual results:
BOINC tasks running in parallel with the heavy load taking a lot of CPU time

Expected results:
BOINC tasks suspended due to a heavy CPU usage

Additional info:
worked well on F19

Comment 1 Vratislav Podzimek 2013-12-03 09:02:09 UTC
Additional info:
it seems that BOINC ignores exclusive applications settings as well

Comment 2 Mattia Verga 2013-12-20 09:43:20 UTC
What projects are you running?
On my system the "suspend if CPU exceed %" works well. The only thing I found is that it doesn't suspend work on GPU apps.

Can you provide a screenshot of your boinc settings? You can also try to remove your local preferences and reset them (in the upper right corner of the preferences window you will find the button "Remove").

Also, in the Fedora updates-testing repository there's a new version of boinc, you can try if it fixes your problem.

Comment 3 Vratislav Podzimek 2014-01-08 16:07:00 UTC
Created attachment 847231 [details]
screenshot of the running top utility

Comment 4 Vratislav Podzimek 2014-01-08 16:08:09 UTC
Created attachment 847232 [details]
computing preferences

the 10 in CPU usage specification really is 10 not partially displayed 100

Comment 5 Vratislav Podzimek 2014-01-08 16:09:33 UTC
Created attachment 847233 [details]
screenshot showing exclusive app (xchat) restriction doesn't work

Comment 6 Vratislav Podzimek 2014-01-08 16:15:36 UTC
Using boinc-client-7.2.33-2.git1994cc8.fc20.x86_64 now with the same issues (screenshots were taken with that version).

Comment 7 Vratislav Podzimek 2014-01-08 16:18:13 UTC
Clearing preferences and setting the values back doesn't make a change. One piece of additional information that may help is that I don't use password for authentication between the manager and client. Could that make a difference?

Comment 8 Mattia Verga 2014-01-09 16:34:47 UTC
I will investigate this. My main machine is a F19 with KDE, I will try to install a virtual machine with F20 and GNOME to try this out.
Seems there are lot of problems between Boinc and F20 with GNOME. Probably bug #1047044 is somehow related...

Comment 9 Vratislav Podzimek 2014-01-10 09:50:06 UTC
CPU constraints are respected on F19 BOINC even on my machines. It's the F20 version ignoring it.

Comment 10 Fedora End Of Life 2015-05-29 09:54:20 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 11 Fedora End Of Life 2015-06-30 00:45:33 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.