Seti work on GPU, but not on CPU


log in

Advanced search

Questions and Answers : Windows : Seti work on GPU, but not on CPU

Author Message
Profile M3rlin
Avatar
Send message
Joined: 29 Jun 12
Posts: 2
Credit: 294,154
RAC: 0
France
Message 1296170 - Posted: 17 Oct 2012, 14:24:07 UTC

Hello,
I have a computer where GPU work while those of my CPU are pending.
would anyone have an idea?

-Boinc Version: 7.0.28
-Windows Seven 32Bits
-2Go Ram
-NVidia
-Intel Core2 Duo E7500

Profile BilBg
Volunteer tester
Avatar
Send message
Joined: 27 May 07
Posts: 2894
Credit: 6,619,710
RAC: 7,931
Bulgaria
Message 1296493 - Posted: 18 Oct 2012, 10:08:33 UTC - in response to Message 1296170.


You repost the same unclear question (no answers because no one can understand what you ask)

Rephrase the question in more detail.


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 12467
Credit: 2,690,814
RAC: 1,162
Netherlands
Message 1296502 - Posted: 18 Oct 2012, 12:05:15 UTC

All work is sent to at least 2 computers, which both have to return the results. These two results will be compared against each other, to see if they match.

If they match, both will get credit and that's that.
If they do not match, the task is sent out to a third computer, which has to return it before it's checked against the original two results, and only when it matches will credit be given out.
If still not a match, the task is sent out again to a 4th computer, etc.

Since there are about 200,000 computers attached to Seti, with varying amounts of work in cache, and validation matches not happening all the time every time, it can take quite a while for your tasks to be credited. Especially when you're matched against someone with a huge cache (thousands of tasks).

Be patient, eventually it'll all work out.
____________
Jord

Fighting for the correct use of the apostrophe, together with Weird Al Yankovic

Questions and Answers : Windows : Seti work on GPU, but not on CPU

Copyright © 2014 University of California