Used to have several running at once. Now, for the past several weeks, nothing. I've even expanded the amount of disk space for GPU.

Used to have several running at once. Now, for the past several weeks, nothing. I've even expanded the amount of disk space for GPU.

Beta tasks?

Couldn't find anything saying Beta.

Couldn't find anything saying Beta.

Thank You! It worked, have 2 tasks now. Any other suggestions welcome. Your replies aren't notifying me, only if I happen to logon.

Read the main thread on these tasks in News >> ATM

https://www.gpugrid.net/forum_forum.php?id=24

They cannot be stopped or they error out.

Tasks with naming convention 2-5 through 5-5 will show 100% completion when started, this is normal, so just let them run until they finish.

The tasks DO NOT checkpoint.

I have over a TB of space for GPU, but no projects.

Current tasks are still the few acemd and the new Quantum Chemistry on gpu tasks.

There was a big slug of them released this morning. All gone now.

You need test applications selected and ALL applications in project preferences to get them.

https://www.gpugrid.net/forum_thread.php?id=5429

There are WUs in progress but for about a month they always go to someone else. I wonder if I need to set BOINC to not run other projects atm, or some kind of nag addon to BOINC that makes it hammer the server for requests every minute or so. We don't seem to be getting work to those who don't have tasks already.
____________

There are WUs in progress but for about a month they always go to someone else. I wonder if I need to set BOINC to not run other projects atm, or some kind of nag addon to BOINC that makes it hammer the server for requests every minute or so. We don't seem to be getting work to those who don't have tasks already.

Probably a holdover from previously running the acemd tasks.

You needn't have to resort to such drastic procedures of removing BOINC and the project.

The task_duration_factor is simply a parameter value in the client_state.xml file.

You could have just stopped BOINC and edited the dcf value for GPUGrid in its section.

I just set dcf values to 0.01 for all my projects. For the projects that still use the dcf parameter, any new tasks will simply recalculate from that low value to what the true dcf value for the ATMBeta tasks really are.

But be advised, the dcf value applies to ALL the applications in a project. Changing to a different app than what you were running will and can produce a large variance in the dcf value simply because one app may be more efficient than another app.

Which puts you right back into your original issue of not getting work because BOINC thinks you can't finish in time.

Solution then is to just edit client_state.xml again back to a low dcf value.

Probably a holdover from previously running the acemd tasks.

You needn't have to resort to such drastic procedures of removing BOINC and the project.

The task_duration_factor is simply a parameter value in the client_state.xml file.

You could have just stopped BOINC and edited the dcf value for GPUGrid in its section.

I just set dcf values to 0.01 for all my projects. For the projects that still use the dcf parameter, any new tasks will simply recalculate from that low value to what the true dcf value for the ATMBeta tasks really are.

But be advised, the dcf value applies to ALL the applications in a project. Changing to a different app than what you were running will and can produce a large variance in the dcf value simply because one app may be more efficient than another app.

Which puts you right back into your original issue of not getting work because BOINC thinks you can't finish in time.

Solution then is to just edit client_state.xml again back to a low dcf value.

Make sure you actually have run BOINC benchmarks on your host. If you don't, the client will report the default low 1,000,000 FLOPS value for the host.

That will produce erroneous estimated calculation times.

Make sure you actually have run BOINC benchmarks on your host. If you don't, the client will report the default low 1,000,000 FLOPS value for the host.

That will produce erroneous estimated calculation times.

The last time I ran a 1080 Ti, the project only had the single acemd3 executable which only took a couple of hours max to compute.

The python tasks are a different animal. I don't know offhand how long a 1080 Ti takes to compute the ATMbeta tasks.

I would have to scour the hosts and see if I could find someone else running that card to compare times.

I still run a 2080 Ti on my two hosts along with some 3080's and never have seen any instance where I couldn't return tasks within 24 hours to get the credit bonus. I think my 2080 Ti's have taken as long as 14-18 hours sometimes.

The 1080 Ti is a generation older with slower clocks and memory. I could imagine it might take over a day to compute. But still within the five day expiration limit. So never should see a "won't finish" message.

Granted Linux is always faster than Windows.

Don't have any other theories for your experience now.

Any other theories?

The last time I ran a 1080 Ti, the project only had the single acemd3 executable which only took a couple of hours max to compute.

The python tasks are a different animal. I don't know offhand how long a 1080 Ti takes to compute the ATMbeta tasks.

I would have to scour the hosts and see if I could find someone else running that card to compare times.

I still run a 2080 Ti on my two hosts along with some 3080's and never have seen any instance where I couldn't return tasks within 24 hours to get the credit bonus. I think my 2080 Ti's have taken as long as 14-18 hours sometimes.

The 1080 Ti is a generation older with slower clocks and memory. I could imagine it might take over a day to compute. But still within the five day expiration limit. So never should see a "won't finish" message.

Granted Linux is always faster than Windows.

Don't have any other theories for your experience now.

Any other theories?

Yes.
Try setting "Store at least XX days of work" parameter as low as possible for BOINC Manager to start requesting for GPU work.
A detailed explanation can be found at Message #54300.

The last time I ran a 1080 Ti, the project only had the single acemd3 executable which only took a couple of hours max to compute.

The python tasks are a different animal. I don't know offhand how long a 1080 Ti takes to compute the ATMbeta tasks.

I would have to scour the hosts and see if I could find someone else running that card to compare times.

I still run a 2080 Ti on my two hosts along with some 3080's and never have seen any instance where I couldn't return tasks within 24 hours to get the credit bonus. I think my 2080 Ti's have taken as long as 14-18 hours sometimes.

The 1080 Ti is a generation older with slower clocks and memory. I could imagine it might take over a day to compute. But still within the five day expiration limit. So never should see a "won't finish" message.

Granted Linux is always faster than Windows.

Don't have any other theories for your experience now.

On average, my 1080Ti took 5hrs to complete an ATM WU, so I completed just shy of 5 WU's per day. This was back in October, when I still received them. So GPU age/performance is definitely not the issue. Unless of course they changed the WU size recently.

Yes, Steve said they did indeed increase the size of the tasks so they run longer now. Was only 50 atoms originally and is now doubled to 100.