I have a GTX550Ti and according to skgiven this is better for cuda 4.2 than cuda 3.1 tasks. I can confirm that as a cuda 3.1 WU takes 41xxx seconds to complete.
So I have set to accept beta and cuda 4.2 short runs for this card, but however there is plenty of work according to the server page, I don't get any and there is another cruncher who gets no taks either.

How can this be solved?
Thanks.
____________
Greetings from TJ

This machine with 550Ti and driver 306.97 can do cuda 4.2 as it did 2 beta's today that finished good and a third beta is in process.
So why not getting cuda 4.2 short runs?
____________
Greetings from TJ

If you're not getting the short 4.2 it's because there isn't any, the server status page is inaccurate.

Edit: I see you were told this already in another thread.

If you're not getting the short 4.2 it's because there isn't any, the server status page is inaccurate.

If you're not getting the short 4.2 it's because there isn't any, the server status page is inaccurate.

I don't belief this unless I hear it from a project member like Nathan of GDF.
Looking at the server status page several times a day, I see all numbers changing, so it is updating. And moreover Nathan mentioned that they had a whole lot new WU's.

I have updated to the latest nVidia driver 314.07, cuda version 5000 for the GTX550Ti.
And guess what happened, I got a: Short runs (2-3 hour on fastest card) 6.52 (cuda42)

So it seems a driver issue after all then...?

I will see how long it takes to complete, estimated 12:32 hours. It is now finishing Einstein@home (they take 35 minutes while BOINC continuously estimate 1hour and 50 minutes).

@microchip, if you can check which driver you are using on the pc that is not getting cuda42 tasks, and is the same as I had before (306.97) then we are pretty sure it's a driver thing. Thanks for your help.
Your statement that you didn't got these tasks either, convinced me to update my drivers.
____________
Greetings from TJ

I have updated to the latest nVidia driver 314.07, cuda version 5000 for the GTX550Ti.
And guess what happened, I got a: Short runs (2-3 hour on fastest card) 6.52 (cuda42)

So it seems a driver issue after all then...?

I will see how long it takes to complete, estimated 12:32 hours. It is now finishing Einstein@home (they take 35 minutes while BOINC continuously estimate 1hour and 50 minutes).

@microchip, if you can check which driver you are using on the pc that is not getting cuda42 tasks, and is the same as I had before (306.97) then we are pretty sure it's a driver thing. Thanks for your help.
Your statement that you didn't got these tasks either, convinced me to update my drivers.

Guys....

If there are tasks in the queue the server will send you one. The server does not know which driver you have installed and it doesn't care which driver you have installed.

The reason you do not get tasks when the server status page says there are tasks is because the server status page lies. If you think that when you click the Server Status link that the server then goes and counts all the tasks in the queue and puts the number in the Status Page you see then you are wrong. It does not happen that way. I will explain what happens...

The server counts the tasks in the queues about every 10 minutes then it saves those totals in memory. You come along five minutes later and click the Server Status link and it gives you the numbers it saved from the previous count which happened 5 minutes earlier. Now here is the very, very tricky part so read very, very carefully and think very, very hard, OK? In between the time it counts the tasks in the queues and the time you look at the Server Status other hosts sometimes request work and grab all the tasks. If you understand that then you can understand how you can be looking at the Server Status page and it's telling you 359 tasks (for example) are available but then you click Update in BOINC manager and the Event Log says "no work available". The numbers on the Server Status page are never current which means they are not up to date, they are old info. The report of "no work available" in the Event Log is based on current info therefore you should trust it rather than the Server Status page.

OK, there you have all the information you need to understand this riddle that confuses you. If you still do not understand then you need to start again at the top of my post and read it, repeatedly if necessary, until you understand because that is exactly the way it happens. And if you think I am mistaken then note that there are least 40 other regular readers/posters here who would correct me if I am wrong on this matter and you will note that none of them do.

Yah, Nathan said he put 1,000 tasks in the queue but stop and think.... maybe there are 5,000 hosts that are requesting work from that queue so they gobble it all up within a few minutes?

____________
BOINC <<--- credit whores, pedants, alien hunters

The server does not know which driver you have installed and it doesn't care which driver you have installed.

The server does not know which driver you have installed and it doesn't care which driver you have installed.

This is not true. I have had many occasions for several projects for AMD as well as nVidia cards that BOINC tells that I need to update my drivers to get work. And indeed after an update I got work then.

And if you think I am mistaken then note that there are least 40 other regular readers/posters here who would correct me if I am wrong on this matter and you will note that none of them do.

Thank you, Richard, for correcting some of the details I've got wrong. You seem to think that makes me entirely wrong so do explain why TJ sees tasks in the queue on the Server Status page but cannot get a task.

____________
BOINC <<--- credit whores, pedants, alien hunters

I agree with Dagorath, please do tell, you seem to be more informed than either of us and I'm sure there has to be a reason other than just drivers.

I lost during the reinstall nvidia driver, 3 long tasks of course im lost rac for them..sad..
Within last three days I had lost about 50,000 rac in users rankings.Why??? if im turn off my computer im dont lose soo many,exemple.. But I Crunching 24/7 without any errors on my part, but i see some fail jobs in my results.
Now two days i cannot get over 577000..just im circled around..
But i see , many people have same problem..so what happened?
sorry for engl.

Jozef J

Stop doing the short runs and just do the long runs, you're RAC will jump up a bunch. With 2 GTX680's they should take about 5 1/2 hours a wu (the new toni's). I leave the short runs to the less powerful cards.

Not there, uh huh. Well, I apologize if this ruffles feathers but where I come from if it says tasks are there when they're not there then it's lying. Some say it's telling "porkies" and that's fine, you know whatever slang works for you, here we call it lying. Not suggesting somebody should be taken out and whipped over it, not saying all operations must cease until it's fixed, just saying it's not truthing i.e. it's lying. If this same situation should occur again in the future and nobody is providing the detailed explanation and guys are needlessly flailing around with driver upgrades... would it be OK if I say something like "the server is not truthing again"? Would that be less offensive?

____________
BOINC <<--- credit whores, pedants, alien hunters

To me lying is intentionally trying to deceive. I'd say in this case it's simply a mistake, an error with no intention of deception. BOINC client/server has many problems, some far far worse than this. I doubt many of them are intentional.

Only as info: Very soon we run out of long queue Work ;)
____________
DSKAG Austria Research Team: http://www.research.dskag.at

TJ, are you getting tasks consistently now, or as erroneous as before the driver update? The driver version really shouldn't cause such behaviour (unless the BOINC log said "driver version xxx too low, please upgrade to at least xxx").

MrS

TJ, are you getting tasks consistently now, or as erroneous as before the driver update? The driver version really shouldn't cause such behaviour (unless the BOINC log said "driver version xxx too low, please upgrade to at least xxx").

MrS

TJ, are you getting tasks consistently now, or as erroneous as before the driver update? The driver version really shouldn't cause such behaviour (unless the BOINC log said "driver version xxx too low, please upgrade to at least xxx").

MrS

Hello MrS, Yes I get tasks consistently. Directly after I did a clean install of the driver and a reboot I got them (cuda42). They take 25xxx to 26xxx seconds on the 550Ti. No BOINC didn't came with a driver this time (306.97 should do it as it ran beta's (cuda42) consistently.

Thanks for the updates, guys. So in this case it really seemed to be some weird driver issue!

MrS

Thanks for the updates, guys. So in this case it really seemed to be some weird driver issue!

MrS

Not on my side, though. I didn't change drivers at all but work started flowing after one of the scientists submitted 1000 WUs to the short 4.2 queue.

Now that that is settled... we still aren't sure if this server (GPUgrid server) will refuse to send tasks due to the driver on the host being "unacceptable", however you want to define unacceptable. It appears Einstein's server is configured to do so but that doesn't mean this project's server is. Can anybody verify it or think of a quick and easy way to test it? I suppose one could install an unacceptable driver and see if they still receive tasks. In fact I would do such a test but I'm not sure which driver(s) might be deemed unacceptable and I don't want to flail about with guesses.

____________
BOINC <<--- credit whores, pedants, alien hunters

Now that that is settled... we still aren't sure if this server (GPUgrid server) will refuse to send tasks due to the driver on the host being "unacceptable", however you want to define unacceptable. It appears Einstein's server is configured to do so but that doesn't mean this project's server is. Can anybody verify it or think of a quick and easy way to test it? I suppose one could install an unacceptable driver and see if they still receive tasks. In fact I would do such a test but I'm not sure which driver(s) might be deemed unacceptable and I don't want to flail about with guesses.

How come one of the "short" queues on the server status page has 10,000+ WUs, but I can't seem to get any of them? I'm running the long WUs fine.

And, come to think of it, why are there two "short" queues? One for 3.1? So are there a bunch of WUs in the 3.1 queue that the server refuses to give me because I can run 4.2 WUs?

How come one of the "short" queues on the server status page has 10,000+ WUs, but I can't seem to get any of them? I'm running the long WUs fine.

And, come to think of it, why are there two "short" queues? One for 3.1? So are there a bunch of WUs in the 3.1 queue that the server refuses to give me because I can run 4.2 WUs?

How come one of the "short" queues on the server status page has 10,000+ WUs, but I can't seem to get any of them? I'm running the long WUs fine.

And, come to think of it, why are there two "short" queues? One for 3.1? So are there a bunch of WUs in the 3.1 queue that the server refuses to give me because I can run 4.2 WUs?

Indeed top is cuda31 and the second is cuda42. This is the same order as on the compute preferences settings. So the 10000+ are the cuda42 ones.
The server can see (I think) for which WU the GPU is best. I get only long runs on my GTX285 when I disable all the others.

Edit; MrS posted when I was typing...
Edit 2, Thanks MrS.

So, were out of long runs now? Any idea when we'll be getting more?

We seem to have dried up on short WUs. Can we get some more? Thanks
____________

Team Belgium

Perhaps there is something not quite good with the server. I got these messages from time to time (when I was not watching the pc):
26/02/2013 16:03:06 GPUGRID Sending scheduler request: Requested by project.
26/02/2013 16:03:06 GPUGRID Requesting new tasks for CPU and GPU
26/02/2013 16:03:08 GPUGRID Scheduler request completed: got 0 new tasks
26/02/2013 16:03:08 GPUGRID Message from server: No tasks sent
26/02/2013 16:03:08 GPUGRID Message from server: No tasks are available for Short runs (2-3 hours on fastest card)
26/02/2013 16:03:08 GPUGRID Message from server: No tasks are available for ACEMD beta version
26/02/2013 16:03:08 GPUGRID Message from server: No tasks are available for the applications you have selected.

However, when I request manually by clicking the "update" button I almost immediately get new work.
Perhaps more people have this "issue"?

____________
Greetings from TJ

Are you sure? According to Nate in the News forum, the top one is the 4.2 queue

http://www.gpugrid.net/forum_thread.php?id=3298&nowrap=true#28658

Are you sure? According to Nate in the News forum, the top one is the 4.2 queue

http://www.gpugrid.net/forum_thread.php?id=3298&nowrap=true#28658

Pretty sure as it is mentioned in several posts that the cuda42 is faster then the cuda31. And looking at the server state page and the time WU's are sent back, the fastest must be the cuda42. Or I might have missed something.

This is all I get:

GPUGRID 02-26-13 13:54 Sending scheduler request: Requested by user.
GPUGRID 02-26-13 13:54 Requesting new tasks for NVIDIA
GPUGRID 02-26-13 13:55 Scheduler request completed: got 0 new tasks
GPUGRID 02-26-13 13:55 No tasks sent
GPUGRID 02-26-13 13:55 No tasks are available for Long runs (8-12 hours on fastest card)

Sure, it can say "no tasks available for long runs" in Event Log and then 5 minutes later you receive a long run. One explanation is that there are in fact none available when you request one but a few minutes later someone returns an errored result so then a resend is made available. Or there are none available then someone returns a success result which allows the server to generate a new task based on that success result (since they generate some tasks "on the fly", IIUC).

____________
BOINC <<--- credit whores, pedants, alien hunters

it again dried out :(
____________

Team Belgium

it again dried out :(

it again dried out :(

You can do the 3.1 then, they take longer on my 550Ti, but it keeps the RAC flowing.

it again dried out :(

You can do the 3.1 then, they take longer on my 550Ti, but it keeps the RAC flowing.

Can't. They all error out on my GTX 560. I have the long queue enabled and am crunching a TONI one. Let's see how it goes.

There's over 2200 people hammering the long queue and only 323 on the short one. Now that's greed for ya, they just can't let their RAC's slip down.

My machine with twin GTX590's is not getting any GPUGRID work. the reply to BOINC's request for work is, no work available for short or long. What's up with this? The server status page says, there are plenty of wu's available to send. Are others having the same problem? Rick
____________

There's over 2200 people hammering the long queue and only 323 on the short one. Now that's greed for ya, they just can't let their RAC's slip down.

We're all having problems Rick, the server polls the queue every hour or so when new wu's get generated and dumped in they go pretty quickly. They pulled most of the NOELIA's because they had major issue's.

Thanks for the reply flashawk. Times are tuff all over, SETI@Home can't download wu's fast enough, and GPUGRID is running out of work. I guess Donate@home, and World Comunitee Grid will get some bonus donations from my hungry for work machines:) Rick
____________

We've dried out again...
____________

Team Belgium