Thanks. I'll keep an eye on them, and see what happens when they report. No change on the running conditions here: the only unusual thing is that I ran some of the WCG covid betas on the GPUs yesterday. It would be a big snafu if they had left the cards in an dodgy state after running, but I don't think it's likely.

http://www.gpugrid.net/workunit.php?wuid=27021719

it looks like in this case, even though you returned it within 5 days, you were processing a resend. the person before you missed their deadline, and it was resent to you, but shortly after that, the original person submitted their late result.

when processing resend, and there's a timeout involved, it becomes first come first serve, or first to the finish line, whatever analogy you prefer. even though the person submitted it late, they submitted it first, and you submitted your result about 4.5 days later. I know if you would have submitted your result earlier, you would have received equal credit, so there must be some grace period, maybe if two results come in within 1 day? I'm just guessing. but your result was over 4.5 days later, so i can understand that the validator might have some limits in this case.

but this WU already had a long delay. the first result was received 7 days after inception, and your result over 11 days. I know it's unfortunate, but that seems to be the "why"

thank for the explanations.
So it seems to be kind of lottery whether a task crunched by a GTX750ti succeeds or fails after 5 days. Really a waste of CPU and GPU power and time :-(
Even more, my decision to change to Folding@home was a good one.

So it seems to be kind of lottery whether a task crunched by a GTX750ti succeeds or fails after 5 days. Really a waste of CPU and GPU power and time :-(
Even more, my decision to change to Folding@home was a good one.

I have my GTX 750ti overclocked to 1366 MHz and can finish within the time constraints if it crunches 24/7. However, the base credit puts it well below the 100K/day it earned doing Toni's methods development MDAD project. Of course it's about bonus for quick turnaround. However, Toni used the same window of expiration for WUs which were miniscule by comparison. There is no adjustment here for the relative size of the jobs.

I sense that this project is discouraging participation by the "small timers" with older or budget cards. It is IMO more fair to grant credit solely on FLOPS completed, but turnaround time is a major factor in distributed supercomputing. That makes the fastest hosts the most desirable. Extra credit keeps them hooked.

Although I am presently committing 2 of my hosts to GPUG, I have my GTX 750ti crunching FAHcore tasks and gaining around 175K points there each day.

It's said that a stopped clock shows the exact time twice a day...

From time to time, Gpugrid Project status makes this thread title "Down to 5 tasks in progress" come true.
This was a screenshot of Gpugrid Server Status page today, July 18th 2021 at 09:05 UTC...



Then, usually comes Gpugrid Team into action, replaces the battery to the clock, and a new cycle starts ;-)

🤔️

There was a small batch of tasks yesterday, but they disappeared very quickly: mainly because most users returned them with an error after about three seconds. WU 27077711 was created at 18:33, and ran through the maximum error count in half an hour.

I don't think there was anything wrong with the task data (I completed another from the same batch), but there is a problem with the application deployment - which should be fixed.

There was a small batch of tasks yesterday, but they disappeared very quickly: mainly because most users returned them with an error after about three seconds. WU 27077711 was created at 18:33, and ran through the maximum error count in half an hour.

One of my hosts catched also two of these shorter CRYPTICSCOUT_pocket_discovery tasks.
Since I have applied the same WORKAROUND to every of my hosts, both tasks were finished successfully:
0_1-CRYPTICSCOUT_pocket_discovery_9f6d15b7_c2ff_4a6e_a594_7cc0797a7231-0-1-RND3838_0
0_0-CRYPTICSCOUT_pocket_discovery_9f6d15b7_c2ff_4a6e_a594_7cc0797a7231-0-1-RND1209_0

Additionally, the same host had previously catched one of the very few remaining ADRIA_New_KIXcMyb_HIP_AdaptiveBandit long tasks.
I'm estimating it to finish on next Tuesday July 20th, at about 19:50 UTC.

Additionally, the same host had previously catched one of the very few remaining ADRIA_New_KIXcMyb_HIP_AdaptiveBandit long tasks.
I'm estimating it to finish on next Tuesday July 20th, at about 19:50 UTC.

Finally, task e3s455_e1s595p0f274-ADRIA_New_KIXcMyb_HIP_AdaptiveBandit-1-2-RND9459_1 come out today at exactly 19:52:25 UTC.
It took 279050 seconds of total processing time. That is: 3 days, 5 hours, 30 minutes and 50 seconds in a non-stop journey.
These ADRIA long tasks pose a hard birth for a GTX 1650 GPU...

Currently, #Tasks in progress is reduced to 4.

Down with only 2 now but still 20 Anaconda.

Looks like they will stay there for while.