Message boards : Questions and problems : 2 task running after installing Boinc ??
Message board moderation
Author | Message |
---|---|
Send message Joined: 27 Apr 11 Posts: 4 ![]() |
I have 2 task running and eating up my cpu at 100%... I only want ONE task running...It will not let me delete THE OTHER ONE...or suspend just 1 ..?? OR HOW did I get 2 running in the first place ? Thanks fordraiders |
![]() Send message Joined: 29 Aug 05 Posts: 15628 ![]() |
BOINC will, by default, allow one science application running a task per CPU core. If you only have one core, you'll only see one task running. However, today's CPUs either have hyper-threading --where the physical core is accompanied by a virtual core-- or it's a dual-core or quadro-core CPU. Or it has even more cores (6 or 8 isn't unusual, these can have hyper-threading as well, making them 12and 16 core). So, I assume that your CPU is either a dual-core (Intel Core 2 Duo for instance) or it can do hyper-threading (Late models Pentium 4, with the 800MHz FSB motherboard). In this case BOINC will use both threads to run work on, thus you see two tasks running. Deleting work won't help, suspending it neither, as you have told BOINC to use both cores. This it tries to do. You can tell BOINC to use only one core by adjusting your preferences. Open BOINC Manager->Advanced view->Advanced->Preferences->Processor usage. Find the option On multiprocessors, use at most 100% of the processor and change its value to 50%. Then click OK. You'll see immediately that BOINC changes to use only one core of your CPU. :) |
Send message Joined: 27 Apr 11 Posts: 4 ![]() |
"Deleting work won't help, suspending it neither, as you have told BOINC to use both cores. This it tries to do" ok..I did not tell it do to do anything...It defaulted. But Thanks for the help. BOINC should let user decide preferences. during setup. or maybe I miseed it.. appreciate the help..! |
![]() Send message Joined: 29 Aug 05 Posts: 15628 ![]() |
BOINC should let user decide preferences. The default setting for BOINC is to only allow the science applications to use the hardware when it is otherwise idle and then to use all possible hardware found/detected. This can include any GPUs in the system. However, as soon as you start using your system, BOINC will stop the science applications doing their work. So in essence, if you didn't change any preferences ever before, not through the project preferences and not through the local preferences, you wouldn't have seen it using 2 CPU cores at all. Since your first post indicates that you saw BOINC using two CPU cores while you were using the computer, you must've changed preferences somewhere before. And then forgot about it. That happens. |
![]() Send message Joined: 29 Aug 05 Posts: 15628 ![]() |
However, as soon as you start using your system, BOINC will stop the science applications doing their work. I must say that there are one or two situations in which this doesn't work: 1. You installed BOINC clean and never rebooted. But this isn't very much possible as it would mean you manage to run BOINC without its limited user accounts, a feat not even Bill Gates would be capable of doing. ;-). 2. You installed BOINC over a previous installation. This then causes the file boinctray.exe to stop running. This file is used in Windows Vista and Windows 7 to detect whether or not you're tapping on the keyboard/wiggling your mouse. A BOINC upgrade installation will delete all presently running BOINC files from memory and then delete them from the BOINC directory, before placing the new files back. Thus boinctray.exe gets removed from the memory. At present though, the installer doesn't reactivate it after the new installation is complete. So after a BOINC upgrade, the idle detection program isn't running. This will be fixed in a future version of BOINC (probably BOINC 7.x). You can restart boinctray.exe by double-clicking on it in the BOINC programs directory, or by rebooting the system, since it is started from the registry. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.