there are no available jobs. Generally there are no jobs. There is no short or long for the GPU. It's in my computer a problem with getting jobs or something with the project?

http://www.gpugrid.net/show_host_detail.php?hostid=170640

http://www.gpugrid.net/show_host_detail.php?hostid=170784
____________

It's the project. Take a look at the server status page (top right corner).
The current simulations reached their final steps (workunits generated from finished tasks here at GPUGrid), so there's only very scarce work available for a while until the staff will release new simulations.

About a month ago, we had a bunch of WUs (SDOERR_CASP22S) posted, then canceled, but never re-released. I wonder what happened to them?

I still have 5 ghost units, on one of my computers from that time.

May I repeat my previous proposal ... if we cannot increase the number of studies for using GPUGRID to capacity, why don't we aim at larger and more sophisticated molecules?

I seem to recal a F@H posting where the scientists stated that truly thrilling investigations stand and fall with crunching power and it was hardly possible to derive something valuable before the 2010s because of lacking speed. The hardware was simply not fast enough to handle larger proteins.

Well, here we have a supercomputer now stuffed with all kinds of Kepler, Maxwell and Pascal GPUs running idle... and craving for big data.
____________
I would love to see HCF1 protein folding and interaction simulations to help my little boy... someday.

Perhaps they could shorten the length of the WUs, I say this even as a fast card owner. The work just isn't being done efficiently and with more WUs more people could have a chance to contribute in parallel rather than waiting for a gt640 to finish a BNBS2.

The new ADRIA_FAAH_WT_ Long WUs only run about 75% on my 970 on windows 10. The Bus interface load is less than BNBS2 and Pablo's adaptive goal. Not sure if you guys can improve this. Haven't gotten one of these new ones on my windows XP 64bit 980ti yet so I can't say if WDDM has much difference.

Haven't gotten one of these new ones on my windows XP 64bit 980ti yet so I can't say if WDDM has much difference.

It's the project. Take a look at the server status page (top right corner).
The current simulations reached their final steps (workunits generated from finished tasks here at GPUGrid), so there's only very scarce work available for a while until the staff will release new simulations.

I see two topics that talk about the same...
Can project managers tell us when there will be new research and new tasks?
Thank you.

I certainly would appreciate being able to get more than one long run and one short run every 3-5 days. I bought a new GPU specifically so that this project would no longer take nearly the deadline time to process one long run WU, now that I can do a long run in about 7 hours, having no GPU work for the same amount of time my old system used to crunch one WU isn't something I appreciate. :(

Einstein is getting a lot of Priority-Zero work from me with the new GPU though. I just wish there were more GPU projects for bio/medical sciences... or more consistently available WU's here!

There is folding@home :)

6th day in a row none of my computers have gotten a single WU, despite manually updating when the new WUs were released. The event log never said too many updates, it just spit out the normal 0 new tasks sent.

It might have something to do with the fact that all of them are doing Einstein both CPU and GPU just trying to keep my house warm and perhaps because of this they don't ask for GPUGrid work as often, is there anyway I can change this?

There is folding@home :)

PappaLitto - Set your GPUGRID Resource share to the maximum of 99,999. That will give this project the highest possible priority in BOINC.

If you have other GPU projects you want to run while waiting for GPUGRID work set the Resource shares lower. I have Milkyway set to 500, Einstein set to 100 and Seti set to 0. The same is also true for CPU projects but they are two separate groups of work so the relative priority is split between CPU and GPU groups.

Also set your work queue low so it doesn't download lots of work from other projects that would stack up and excessively delay starting a GPUGRID work unit when one comes in. Mine is set at .05 days work and .05 additional. That gives a little buffer but not more than 2.4 hours total.

Folding is another option however it is completely separate from BOINC. It is possible to run them both on the same computer and have the folding application run on the GPU only and use BOINC for the CPU only projects. I have a major investment in BOINC so I decided to stick with that.

I have a major investment in BOINC so I decided to stick with that.

I was referring to my time investment with setting up systems running BOINC, configuring and optimizing them. I also am using BoincStats to monitor and control these systems. Another consideration is I am participating in the Gridcoin group and I didn't see a way to use folding@home with the same setup.

I think it's extremely silly that folding@home doesn't also put themselves on BOINC. The entire reason I use BOINC is the ability to have backup projects and Gridcoin. Folding could significantly increase their FLOPS if they supported BOINC.

I think it's extremely silly that folding@home doesn't also put themselves on BOINC.

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.

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

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.

When can we expect normal supply?

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

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.