Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Proth Prime Search :
Proth Prime Search (Cuda23) has a bug.
| Author |
Message |
|---|
|
|
|
Your GPU has only 255 MB, that is 1 MB short of the BOINC-requirement.
But it is no bug.
rytis will lower the requirement but to do so he needs to recompile the server-software.
For this he want to wait until the recent problems with the validator and the database have sorted out. | |
|
 Michael Goetz Volunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13513
ID: 53948
Credit: 236,922,854
RAC: 0
                           
|
OK.
I'll set no new tasks on the project for now since I have those two PSP's already running in order not to receive more of these Proth's.
Or you could set your PrimeGrid preferences to not use the GPU. Then you would still get CPU tasks for PrimeGrid, GPU tasks for SETI, and not get anymore faulty GPU tasks from PrimeGrid.
____________
My lucky number is 75898524288+1 | |
|
|
|
So there was a bug there?
I had to read through the last posting in this thread.
For a little moment I was wondering in which way I could still get (functional) WU's from Seti, while still (as long as there may be a problem) keeping those CUDA tasks out from PrimeGrid.
just disable GPU-use on your PrimeGrid settings.
Just for comparison: Would it matter if those long tasks were being run by means of CUDA rather than by my Pentium D 3.40 GHz?
CUDA is speedy, but I always thought the Pentium D beat the graphics processor on my screen-/monitor card. Anyway, those Seti@home WU's that I ran had some numbers in them that were reported that I don't think would have been found through CUDA, though.
i never ever ran a single WU for YETI, but they got a measly GPU-app.
on the other hand you are running 32-bit OS's - not the right choice for sieving..
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13513
ID: 53948
Credit: 236,922,854
RAC: 0
|
So there was a bug there?
That depends on your definition of what a bug is. You were getting errors because your video card has "too little memory" to run the application. Technically, that's working as designed, and isn't a bug. However, "too little memory" is actually an amount specified by the project (PrimeGrid), and currently they're specifying a lot more memory than is actually needed. If they lower that amount, these tasks would work on your video card. This change is expected to happen in a couple of days. Whether this is a bug or not is a matter of semantics.
For a little moment I was wondering in which way I could still get (functional) WU's from Seti, while still (as long as there may be a problem) keeping those CUDA tasks out from PrimeGrid.
Very simple to do: on the PrimeGrid website, go to PrimeGrid Preferences and set "use Nvidia GPU" to NO. If you're using more than one location (i.e., "Home", "School", or "Work"), make sure you change the CPU setting for the correct location. If you have no clue what I'm talking about, you should change the default setting, since that's what is used if you don't specify a location.
Just for comparison: Would it matter if those long tasks (PSP's) were being run by means of CUDA rather than by my Pentium D 3.40 GHz?
Those two that I have right here are psp_llr_54050958_3
(46:32 elapsed, progress 26.260 %) and
psp_llr_54050496_3 (31:52 elapsed, progress 18.760%).
The PSP LLR tasks are NOT available to run on CUDA. At this time, only PPS Sieves have a CUDA application. Also note that you were talking about PPS sieves and PSP LLRs. PPS is not the same as PSP.
CUDA is speedy, but I always thought the Pentium D beat the graphics processor on my screen-/monitor card.
As far as speed is concerned, chances are even a slow CUDA card is a lot faster than a CPU when running the PPS sieve application. My GTX280 runs the PPS sieve about 10 times faster than one of the cores on my Core 2 Quad Q6600.
____________
My lucky number is 75898524288+1 | |
|
Message boards :
Proth Prime Search :
Proth Prime Search (Cuda23) has a bug. |
