Message boards : Questions and problems : 6.4.7 - Slower than a turtle
Message board moderation
Author | Message |
---|---|
Send message Joined: 31 Mar 08 Posts: 46 ![]() |
Why is 6.4.7 so slow? |
Send message Joined: 25 Nov 05 Posts: 1654 ![]() |
As measured in what way? |
Send message Joined: 4 Mar 09 Posts: 3 ![]() |
I've also noticed a significant slowdown using BOINC 6.4.5 and 6.4.7 on Windows Vista (32bit) running on a dual-core CPU. Prior versions worked fine on the same machine. My problem is that the whole machine is slower, regardless which settings in the "Computing preferences" are set. Currently i have CPU and GPU suspended, while the computer is not in use. But my client (Seti@home) seems to ignore these settings. Examining the behavior more closely indicated that the rendering performance on Windows Vista (with Aero enabled) is also significantly decreased. The CPU usage (%) and CPU time of BOINC+Seti@home is zero, but the system keeps it's poor performance until the BOINCMGR and client is closed. This leads to the following analysis: 1) CPU-context switches are almost equal, if BOINC is running or not 2) GPU-context switches are significantly(!) higher while BOINC is running Therefore the reason for the problem appears to be the new support for CDUA. I am using a "GeForce 8600 GT" with 512MB of dedicated video-memory (767MB shared). From my point of view this seems not to be sufficient for BOINC using CDUA, but I was not able to disable the CDUA support. Therefore my only workaround is to stop BOINC until a fixed version of the client is available. |
Send message Joined: 25 Nov 05 Posts: 1654 ![]() |
BOINC version 5.* doesn't have support for cuda, so it should work OK for you. |
Send message Joined: 4 Mar 09 Posts: 3 ![]() |
Boinc 5.* did not properly work on Vista. Therefore I've re-installed 6.2.18, which worked fine before the updates. Now really nothing happens: system is responding fine, but Seti@home client does not start (which is most likely the cause for the good performance). The BOINC console reports "Missing a CUDA coprocessor". |
![]() Send message Joined: 29 Aug 05 Posts: 15632 ![]() |
If you had CUDA work appointed (Seti application 6.08), you will have to detach and re-attach. This will send word to the Seti server that all that work can be reissued, while you will get the Seti CPU app (6.03) and work for it only. |
Send message Joined: 4 Mar 09 Posts: 3 ![]() |
detach and re-attach worked, thanks! (now i'm working with boinc 6.2.18 - without any impact) |
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.