It is because Folding needs lower latency. That is, the output of one completed work unit is needed to start work on the next in the series. So they can't take the long buffer times in BOINC. That is why the Folding client starts downloading a new work unit when the present one reaches 99% complete.

I don't quite know why BOINC couldn't do that with a little tweaking though, but I don't think anyone has looked into it for several years. BOINC actually has some advantages; it is able to report more information to the server on the driver you are using, for example, and a lot of other information about your hardware. Also, BOINC detects your GPU cards properly, and allows you some degree of individual control. That has been a never-ending headache with Folding, though they are attempting to fix it now with their new client, currently in Beta. We will see.

It is because Folding needs lower latency. That is, the output of one completed work unit is needed to start work on the next in the series. So they can't take the long buffer times in BOINC. That is why the Folding client starts downloading a new work unit when the present one reaches 99% complete.

This project needs lower latency as well in order to provide a more contiguos flow of work.
I proposed a similar strategy in this post but while I was hopeful in its implementation that hope is now evaporating.

https://gpugrid.net/forum_thread.php?id=4501

It is because Folding needs lower latency. That is, the output of one completed work unit is needed to start work on the next in the series. So they can't take the long buffer times in BOINC. That is why the Folding client starts downloading a new work unit when the present one reaches 99% complete.

This project needs lower latency as well in order to provide a more contiguos flow of work.
I proposed a similar strategy in this post but while I was hopeful in its implementation that hope is now evaporating.
https://gpugrid.net/forum_thread.php?id=4501

It's up to the BOINC developers, or this project should be outside of BOINC just like folding@home. It would be sufficient to have different queue length in BOINC for different projects to achieve this behavior. This queue length even could be set to a fixed amount by the project itself.
But it's possible even now to achieve this behavior, if you set a low queue length (0.01 days = 14 minutes 24 seconds), and make the BOINC manager to estimate the remaining time on the progress of the workunit. (As this project does not set correct values for the <rsc_fpop_est> field in a workunit's properties.)

Because of the lack of work, I have put all of my processors on folding@home. I let BOINC run with network activity on always in the background and manually shut off folding when it eventually downloads a GPUGrid WU.

Because of the lack of work, I have put all of my processors on folding@home. I let BOINC run with network activity on always in the background and manually shut off folding when it eventually downloads a GPUGrid WU.

Working on FAH, childhood cancer, cancer mapping, rosetta, asteroids, zika, TB.

I will return to GPUGrid as soon as there is work.

---

John

When can we expect normal supply?

;-))

---

I would love to see HCF1 protein folding and interaction simulations to help my little boy... someday.

How about now? ;)

Thanks! MUCH better, I love it. Keep it up please!
Besides, does the server now respond faster ... or is that just my imagination?

---

I would love to see HCF1 protein folding and interaction simulations to help my little boy... someday.

25mar2017:

Tasks ready to send 2,847
Tasks in progress 4,100

Yet when I force a project update, I get no tasks.

I've joined other projects which use my GPU instead because GPUGRID is unreliable at issuing work units.

25mar2017:

Tasks ready to send 2,847
Tasks in progress 4,100

Yet when I force a project update, I get no tasks.

I've joined other projects which use my GPU instead because GPUGRID is unreliable at issuing work units.

- If your GPUs already have enough work to meet your setting for "Store at least X days of work", then it won't get more.
- If GPUGrid is not the next project in line to receive work, according to your Recent Estimated Credit (REC), then it won't get any.
- If you'd like to figure out the real problem, turn on Options > Event Log Options... > Work Fetch Debug, and then read through the Event Log to see WHY you weren't given work, and try to step through that logic by looking at the log.
- If you need help, post one iteration of that work fetch debug logic where you thought it was suspicious, and someone here might help you further.