https://ibb.co/cTqYNMZ

What happened?

Sorry for the downtime.

Outta disk space.

Thanks Toni for dealing with this in busy time before Christmas.

Have good one.

Many Thanks Toni for keeping this project under control. Merry Christmas!
____________
Life's short; make fun of it!

when will GPUGrid support G-Force 3000?

when will GPUGrid support G-Force 3000?

Hello, Is there already a possibility to use RTX 3000 under Windows 10 (Boinc 7.16.11)?

Hello, Is there already a possibility to use RTX 3000 under Windows 10 (Boinc 7.16.11)?

Why is it taking so long to complete support for the 3000s?
The same problem was to support the 2000s. No one will use old Graphics cards

No one will use old Graphics cards

Why is it taking so long to complete support for the 3000s?
The same problem was to support the 2000s. No one will use old Graphics cards

With the current round of work units wrapping up in a matter of hours, it probably is easier to let them finish before updating the app.

You might be onto something. Could be a great stopping point to update the app with no more current work being distributed.

You might be onto something. Could be a great stopping point to update the app with no more current work being distributed.

You might be onto something. Could be a great stopping point to update the app with no more current work being distributed.

I'm confused. Is GPUGRID officially back up and running since Dec 22/2020?
My 2 Intel systems (both with Nivdia cards & Linuxmint 20) haven't had any GPUGrid jobs in several days. I've attempted more than once to communicate with server. Nothing. I've resorted to using my systems for other projects requiring Nvidia as a result.

I'm confused. Is GPUGRID officially back up and running since Dec 22/2020?
My 2 Intel systems (both with Nivdia cards & Linuxmint 20) haven't had any GPUGrid jobs in several days. I've attempted more than once to communicate with server. Nothing. I've resorted to using my systems for other projects requiring Nvidia as a result.

Thanks for the update. Now I understand.

Does anyone know when the new work units will be available?

Does anyone know when the new work units will be available?

Cheers for reply. Seems like those units are in progress forever.

Cheers for reply. Seems like those units are in progress forever.

Toni: When can we expect a new flow of work?

I second the question of when will new tasks become available.

Me three

No new work since Jan 2, 2021. What is going on?

____________

No new work since Jan 2, 2021. What is going on?

No contact with Tony for 25 days! Hope he has not been struck by Covid!

No new work since Jan 2, 2021. What is going on?

Nothing...
Maybe Toni stuck in the snow ?

No new work since Jan 2, 2021. What is going on?

Nothing...
Maybe Toni stuck in the snow ?

Hi all,
Winter Break occurs around the first of the year for most colleges. This batch likely ran out just as the break was starting. The next batch would probably be delayed by that.
- Hopefully we'll get a notice if this project is in the computation completed stage and no more batches are to come. In that case we will have to wait for the next project, which could be a 'good while'.

You should be able to hurry up the next project - by donating enough that they will reach the estimated 50,000 euros necessary to hire and support an intern for one year.

Hi,
the project is still down?
I have tried to remove and install the project in BOINC, but any task run.

Thank you for your availability and collaboration.

KR
Pietro
____________

On any BOINC project: check the server status page.

https://www.gpugrid.net/server_status.php

The project is running (we can type here), but there is no work available.

No new work since Jan 2, 2021. What is going on?

Nothing...
Maybe Toni stuck in the snow ?

Worse, stuck in grant writing... :(
Sorry, I will attend later when I can.

No new work since Jan 2, 2021. What is going on?

Nothing...
Maybe Toni stuck in the snow ?

Worse, stuck in grant writing... :(
Sorry, I will attend later when I can.

I just saw some WUs popping up. Does that mean the project is slowly starting new work generation again?

I see 10 tasks in progress now. Hmmmm

Well we are getting almost no work units these days and I can't tell if the WU's coming out are new or recycled from prior users after a timeout or WU error.

It would be wonderful for an Admin or moderator to post current Project status and news.

Thanks
Bill F

____________
In October of 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

It would be wonderful for an Admin or moderator to post current Project status and news.

Well we are getting almost no work units these days and I can't tell if the WU's coming out are new or recycled from prior users after a timeout or WU error.

It would be wonderful for an Admin or moderator to post current Project status and news.

Thanks
Bill F

One wonders if the project has in fact been restarted or is going thru a period of hibernation.

It would be wonderful for an Admin or moderator to post current Project status and news.

One wonders if the project has in fact been restarted or is going thru a period of hibernation.

It would be wonderful for an Admin or moderator to post current Project status and news.

One wonders if the project has in fact been restarted or is going thru a period of hibernation.

It would be wonderful for an Admin or moderator to post current Project status and news.

I just got two new WU's for my two PC's but they seem to be huge! 5.000.000 GFLOPS, holy cow! It will take a while to get those babies done! After 1h they are at 3%!

This is to thank once more all the efforts involved in bringing new tasks available for us, voracious crunchers.
I guess they don't grow spontaneously, but there is to be some kind of thinking minds and corporate resources behind, isn't it?
Thanks again!

All WUs that I receive now are failing, I don't see any errors but I don't really know where to look. I'm running Debian 10 on a machine with Optimus, so my NVIDIA GPU has device id 1 (at id 0 I have an intel graphics card). My NVIDIA driver is version 460.39

When I run the acemd3 binary directly, I get this output:

2,666% after 09:29 and deadliine 15/02...

All WUs that I receive now are failing, I don't see any errors but I don't really know where to look. I'm running Debian 10 on a machine with Optimus, so my NVIDIA GPU has device id 1 (at id 0 I have an intel graphics card). My NVIDIA driver is version 460.39

When I run the acemd3 binary directly, I get this output:

# Looking for node-locked license in [/opt/acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.htmd/license.dat]
# Looking for node-locked license in [/root/license.dat]
# Looking for node-locked license in [/root/.acellera/license.dat]
# Looking for node-locked license in [/root/.htmd/license.dat]
#
# ACEMD is running with a basic licence!
# Contact Acellera ([email protected]) for licencing.
#
# WARNING: ACEMD is limited to run on the GPU device 0 only!

Anyone has any suggestions? This is the first time I'm trying to crunch tasks for GPUGrid, so I'm not sure if the problem is with these new WUs or if it's my setup.

2,666% after 09:29 and deadliine 15/02...

2,666% after 09:29 and deadliine 15/02...

At that rate, you’ll take over 14 days to complete the task. Deadlines are 5 days.

I think your GTX 650 is just too slow for these tasks.

All WUs that I receive now are failing, I don't see any errors but I don't really know where to look. I'm running Debian 10 on a machine with Optimus, so my NVIDIA GPU has device id 1 (at id 0 I have an intel graphics card). My NVIDIA driver is version 460.39

When I run the acemd3 binary directly, I get this output:

# Looking for node-locked license in [/opt/acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.htmd/license.dat]
# Looking for node-locked license in [/root/license.dat]
# Looking for node-locked license in [/root/.acellera/license.dat]
# Looking for node-locked license in [/root/.htmd/license.dat]
#
# ACEMD is running with a basic licence!
# Contact Acellera ([email protected]) for licencing.
#
# WARNING: ACEMD is limited to run on the GPU device 0 only!

Anyone has any suggestions? This is the first time I'm trying to crunch tasks for GPUGrid, so I'm not sure if the problem is with these new WUs or if it's my setup.

All WUs that I receive now are failing, I don't see any errors but I don't really know where to look. I'm running Debian 10 on a machine with Optimus, so my NVIDIA GPU has device id 1 (at id 0 I have an intel graphics card). My NVIDIA driver is version 460.39

When I run the acemd3 binary directly, I get this output:

# Looking for node-locked license in [/opt/acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.htmd/license.dat]
# Looking for node-locked license in [/root/license.dat]
# Looking for node-locked license in [/root/.acellera/license.dat]
# Looking for node-locked license in [/root/.htmd/license.dat]
#
# ACEMD is running with a basic licence!
# Contact Acellera ([email protected]) for licencing.
#
# WARNING: ACEMD is limited to run on the GPU device 0 only!

Anyone has any suggestions? This is the first time I'm trying to crunch tasks for GPUGrid, so I'm not sure if the problem is with these new WUs or if it's my setup.

All your failed work units have failed on all other Hosts who tried the same work unit.
You have been unlucky in receiving a bad batch.
Keep trying, you may receive a valid Work Unit

At this point it seems to me that there is a bug in the app itself. Are there any Linux/NVIDIA hosts which manage to run these ADRIA tasks successfully?

All WUs that I receive now are failing, I don't see any errors but I don't really know where to look. I'm running Debian 10 on a machine with Optimus, so my NVIDIA GPU has device id 1 (at id 0 I have an intel graphics card). My NVIDIA driver is version 460.39

When I run the acemd3 binary directly, I get this output:

# Looking for node-locked license in [/opt/acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.htmd/license.dat]
# Looking for node-locked license in [/root/license.dat]
# Looking for node-locked license in [/root/.acellera/license.dat]
# Looking for node-locked license in [/root/.htmd/license.dat]
#
# ACEMD is running with a basic licence!
# Contact Acellera ([email protected]) for licencing.
#
# WARNING: ACEMD is limited to run on the GPU device 0 only!

Anyone has any suggestions? This is the first time I'm trying to crunch tasks for GPUGrid, so I'm not sure if the problem is with these new WUs or if it's my setup.

All your failed work units have failed on all other Hosts who tried the same work unit.
You have been unlucky in receiving a bad batch.
Keep trying, you may receive a valid Work Unit

At this point it seems to me that there is a bug in the app itself. Are there any Linux/NVIDIA hosts which manage to run these ADRIA tasks successfully?

All WUs that I receive now are failing, I don't see any errors but I don't really know where to look. I'm running Debian 10 on a machine with Optimus, so my NVIDIA GPU has device id 1 (at id 0 I have an intel graphics card). My NVIDIA driver is version 460.39

When I run the acemd3 binary directly, I get this output:

# Looking for node-locked license in [/opt/acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.acellera/license.dat]
# Looking for node-locked license in [/opt/acellera/.htmd/license.dat]
# Looking for node-locked license in [/root/license.dat]
# Looking for node-locked license in [/root/.acellera/license.dat]
# Looking for node-locked license in [/root/.htmd/license.dat]
#
# ACEMD is running with a basic licence!
# Contact Acellera ([email protected]) for licencing.
#
# WARNING: ACEMD is limited to run on the GPU device 0 only!

Anyone has any suggestions? This is the first time I'm trying to crunch tasks for GPUGrid, so I'm not sure if the problem is with these new WUs or if it's my setup.

All your failed work units have failed on all other Hosts who tried the same work unit.
You have been unlucky in receiving a bad batch.
Keep trying, you may receive a valid Work Unit

At this point it seems to me that there is a bug in the app itself. Are there any Linux/NVIDIA hosts which manage to run these ADRIA tasks successfully?

Check my host or many other linux hosts on the leaderboard. I’ve submitted many valid results. There’s no bug in the app

you missed that he was trying to run the executable directly (outside of BOINC), which is likely why he received that error message, it’s running in basic license “mode” because it can’t find the license files listed above. He probably didn’t move them correctly to be able to run the tasks in the same way that BOINC does. All of my machines have devices on dev 1+, and even one in the same situation with an unusable card at dev0 (which has been excluded) and only runs on the card on dev1
____________

# WARNING: ACEMD is limited to run on the GPU device 0 only!

Perhaps there's no bug in the app now, but there was when the programagor originally posted about it. This bug was that the app had a "basic" licence, thus it could run only on GPU device 0, while programagor has his/her NVidia GPU on device ID 1.

you missed that he was trying to run the executable directly (outside of BOINC), which is likely why he received that error message. All of my machines have devices on dev 1+, and even one in the same situation with an unusable card at dev0 (which has been excluded) and only runs on the card on dev1

Perhaps he installed the BOINC manager as a service?

Edit: programagor's Debian install on host 576641 looks OK from the outside. I'd suspect a driver problem - something like using a nouveau driver without the extra CUDA (computation) libraries provided through a manufacturer driver install.

The new Linux Mint (v20.1) offers me a driver manager:



It was defaulted to the open-source driver, but for computation, I think the proprietary driver is better.

When I ran the binary directly, I tried supplying the `--device 1` parameter, but to no avail; due to the basic license the binary always uses device id 0. Also, I don't see the `license.dat[.*]` anywhere on my system. And my drivers are straight from nvidia, no nouveau. I can compile and run CUDA programs/kernels without any issue. For completeness sake, I reinstalled my drivers, but the issue persists.

EDIT: I also looked inside the wrapper, and there is no string `license.dat`, which leads me to believe that the license file is missing, preventing me from running on GPU id 1

EDIT 2: I just noticed that the wrapper is launching the acemd with device id 0:

7.333% after 24 hours.
It is a pitty, GPUGRID is the only projects that is not cause my computer to lag.

When I ran the binary directly, I tried supplying the `--device 1` parameter, but to no avail; due to the basic license the binary always uses device id 0. Also, I don't see the `license.dat[.*]` anywhere on my system. And my drivers are straight from nvidia, no nouveau. I can compile and run CUDA programs/kernels without any issue. For completeness sake, I reinstalled my drivers, but the issue persists.

EDIT: I also looked inside the wrapper, and there is no string `license.dat`, which leads me to believe that the license file is missing, preventing me from running on GPU id 1

EDIT 2: I just noticed that the wrapper is launching the acemd with device id 0:

wrapper: running acemd3 (--boinc input --device 0)

7.333% after 24 hours.
It is a pitty, GPUGRID is the only projects that is not cause my computer to lag.

look in your BOINC event log at startup. Is your nvidia GPU device id 0? when you see "device [id]" in boinc, it's always the BOINC order, not the system order, which can vary due to the way BOINC decides what is the best device.

The app has not changed.
https://www.gpugrid.net/apps.php

2x GPUs are running on one of my PCs w/o issue.

I have aborted this WU, new one much more faster.

I have aborted this WU, new one much more faster.

I have aborted this WU, new one much more faster.

wait until it runs for a few hours. you will see that the initial percentage increase is not accurate, it is only an estimation from BOINC until it hits a real checkpoint. you'll see the % increase fast until it hits the checkpoint, then it will reset to 0.333 or 0.666% and will go very slow from that point.

Toni:

I have removed my laptop from crunching for GPUGRID. The laptop has a GTX 660M GPU which is inadequate for these large files. In my desktop there is a GTX 1060 which seems to have enough muscle to crunch these large files.

I hope all this crunching will benefit humanity in some way.

Clive

Toni:

I have removed my laptop from crunching for GPUGRID. The laptop has a GTX 660M GPU which is inadequate for these large files. In my desktop there is a GTX 1060 which seems to have enough muscle to crunch these large files.

I hope all this crunching will benefit humanity in some way.

Clive

These are the largest (longest) tasks in the history of the project I believe.

Previous longest was around 12 hours back in the acemd2 (long-runs) application days.

If these are to become the nominal type of task in the future, they really need to increase the deadlines.

Or restrict them to adequate hardware like discrete GTX 1060 or better.

The estimated task GFLOPS seems to be roughly correct at 5,000,000 value.

I agree that so long-running tasks should have their deadlines increased. Otherwise, we gradually go back to super-computers that no one can afford. And the purpose of crowd-computing is that many can participate.
As for limiting tasks to certain GPUs, that's not quite adequate. As I said, my GTX1060 isn't capable of handling those tasks, so it's not only the card that is important, but where it's installed, and what type of cooling is used. Unfortunately, my laptop isn't great at cooling, so both CPU and GPU heat up to 90-93 C. Putting the laptop in a fridge is not an option... And taking all parameters into account, such as cooling, power supply, throttling, even manufacture! - isn't feasible.

a normal full 1060 should be capable to process these tasks in 5 days. must be because it's a laptop version.
____________

My 1050ti in my laptop can finish a task in 66 hours. Must be something wrong.

My GTX 1060 finished one work unit in 38 hours.
http://www.gpugrid.net/results.php?hostid=512821

The GTX 1070 took 26 hours.
http://www.gpugrid.net/results.php?hostid=524425

But another GTX 1070 failed twice.
http://www.gpugrid.net/results.php?hostid=528983
The first time was due to a reboot, and then the next one failed immediately thereafter.

They are all on Ubuntu 18.04/20.04.
I think they are better used on Folding.

But another GTX 1070 failed twice.
http://www.gpugrid.net/results.php?hostid=528983
The first time was due to a reboot, and then the next one failed immediately thereafter.

They are all on Ubuntu 18.04/20.04.

I aborted the jobs for my GT 730 as there was no way they were going to finish them in time. And I suspended that computer from taking work. My GTX 1660 seems to take about a day and a half to finish the jobs.

Maybe make the WUs smaller or increase the deadlines? My GT 730 previously did quite a bit of work. I currently have that computer doing nothing but boinc stuff.

Maybe make the WUs smaller or increase the deadlines? My GT 730 previously did quite a bit of work. I currently have that computer doing nothing but boinc stuff.

Same here with a small GT 710. But the PC always runs 24/7 an did a few WUs per week.

It would be a pity if I could not continue to use this card :/

Work units got stuck at 14% and were canceled after 10 hours of running overnight

workunit 27023967
e2s547_e1s101p0f147-ADRIA_D3RBandit_batch1-0-1-RND7525_0

workunit 27023977
e2s557_e1s68p0f131-ADRIA_D3RBandit_batch1-0-1-RND8450_0

Log

Stderr Output

<core_client_version>7.16.11</core_client_version>
<![CDATA[
<message>
aborted by user</message>
<stderr_txt>
21:59:52 (17660): wrapper (7.9.26016): starting
21:59:52 (17660): wrapper: running acemd3.exe (--boinc input --device 0)
Detected memory leaks!
Dumping objects ->
..\api\boinc_api.cpp(309) : {1599} normal block at 0x000001FE55531F80, 8 bytes long.
Data: < NU > 00 00 4E 55 FE 01 00 00
..\lib\diagnostics_win.cpp(417) : {202} normal block at 0x000001FE55530DC0, 1080 bytes long.
Data: < > EC 0E 00 00 CD CD CD CD 0C 01 00 00 00 00 00 00
Object dump complete.
23:49:15 (10692): wrapper (7.9.26016): starting
23:49:15 (10692): wrapper: running acemd3.exe (--boinc input --device 0)
Detected memory leaks!
Dumping objects ->
..\api\boinc_api.cpp(309) : {1599} normal block at 0x0000027A5CB916D0, 8 bytes long.
Data: < \z > 00 00 B4 5C 7A 02 00 00
..\lib\diagnostics_win.cpp(417) : {202} normal block at 0x0000027A5CB900B0, 1080 bytes long.
Data: <DJ > 44 4A 00 00 CD CD CD CD B0 00 00 00 00 00 00 00
Object dump complete.
20:24:59 (4020): wrapper (7.9.26016): starting
20:24:59 (4020): wrapper: running acemd3.exe (--boinc input --device 0)
Detected memory leaks!
Dumping objects ->
..\api\boinc_api.cpp(309) : {1599} normal block at 0x000001525997F2E0, 8 bytes long.
Data: < 1[R > 00 00 31 5B 52 01 00 00
..\lib\diagnostics_win.cpp(417) : {202} normal block at 0x000001525997FE90, 1080 bytes long.
Data: < 1 X > 04 31 00 00 CD CD CD CD 58 00 00 00 00 00 00 00
Object dump complete.
23:10:11 (3712): wrapper (7.9.26016): starting
23:10:11 (3712): wrapper: running acemd3.exe (--boinc input --device 0)
Detected memory leaks!
Dumping objects ->
..\api\boinc_api.cpp(309) : {1599} normal block at 0x000001CA91D1FCA0, 8 bytes long.
Data: < > 00 00 CF 91 CA 01 00 00
..\lib\diagnostics_win.cpp(417) : {202} normal block at 0x000001CA91D204D0, 1080 bytes long.
Data: < > D0 1C 00 00 CD CD CD CD 0C 01 00 00 00 00 00 00
Object dump complete.

____________

I doubt it was stuck. These tasks take a LONG time to run.

The “memory leaks” messages seem to be common for the Windows app.

Just let it go next time. Will probably take ~48hrs to run on a 1060.
____________

Took me 245,275 seconds on a GTX 1050 Ti - that's a smidge under 3 days. Since these tasks update their progress 150 times over a full run, that's 1,635 seconds between updates - almost half an hour.

And I got the same memory leak warning, even though the task was successful and validated.

Don't despair if nothing seems to be happening - have a cup of coffee and come back later. It's probably still alive.

They are all on Ubuntu 18.04/20.04.

The error message:

ACEMD failed: Error initializing CUDA: CUDA_ERROR_NO_DEVICE (100) at /opt/conda/conda-bld/openmm_1589507810497/work/platforms/cuda/src/CudaContext.cpp:148

looks to me like it was due to a driver update, or some other intervention made your CUDA device inaccessible.

Is there a way to configure BOINC to start downloading a second task only when the first one is finishing? I got 2 tasks, each 5M GFLOPS, with the same deadline. Obviously, the second wouldn't be computed on time, so I had to abort it (it was in READY status, so hopefully it will come to someone else). Or, if that's not possible, can I limit BOINC to 1 task only? Less preferrable, as time will be spent on comms and downloads, but better than expiring tasks someone else could've processed...

Or, if that's not possible, can I limit BOINC to 1 task only? Less preferrable, as time will be spent on comms and downloads, but better than expiring tasks someone else could've processed...

Is there a way to configure BOINC to start downloading a second task only when the first one is finishing?

You can set the work cache to exactly zero, if you like. In that case, BOINC will nominally initiate the request for work three minutes before the final task is estimated to finish. I say 'nominally', because BOINC only performs the 'work needed?' check once per minute, so the actual request may happen any time between three minutes and two minutes before the new task is needed.

You can set the work cache to exactly zero, if you like. In that case, BOINC will nominally initiate the request for work three minutes before the final task is estimated to finish.

Yup, that's exactly the same. Setting it through BOINC Manager activates it immediately, going via resource share means a visit to the website and a project update.

Edit - using 'work cache 0' affects all attached projects, using 'resource share 0' only affects that one project.

Or, if that's not possible, can I limit BOINC to 1 task only? Less preferrable, as time will be spent on comms and downloads, but better than expiring tasks someone else could've processed...

I think the problem will be solved after BOINC processes the first one and gets better time estimates. It should not then download the second one.

But that begs the question of why don't they either give them better estimates to begin with, or limit them to one? They limited the earlier ones to two anyway.

Wouldn't you be able to set the max_concurrent variable in the GPUGRID app_config file to 1?

Such as this:

<app_config>

<app>
<name>acemd3</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>

</app_config>

That only affects how many jobs run concurrently. Not how many get downloaded.
____________

Abort for every task, that shows 0.333%, 1,333% and so on.
Every time i look at the app, there is a bad WU, i am abort them and 1:00 minute later next U show me normal work.

So... Every second WU working normal.


By the way, here is qute from log of the aborted task

I wouldn't mind if it waited for this download until the first task was approaching its finish, though. But note that the estimated time to completion is not a reliable way of deciding when it is about to finish until at least a few tasks have completed successfully.

I now solved my issue with all WUs failing with CUDA error 999.
The error I was receiving was the following:

I crunch only during office hours*. It looks like my GTX 1060 will just make the 5 day limit on these biggies, but only if I hand massage it each week. :( If I start one each Monday then the weekend won't get in the way.

(* more like 10-12 hours, computers are set to preheat my little office before I arrive.)

No, normal WU shows me a % after 1 minute after star.
It`s took them aabout 5 minutes for 1%.
Big one would show 0,333 after a hour.

No, normal WU shows me a % after 1 minute after start.

It`s took them about 5 minutes for 1%.
Big one would show 0,333 after a hour.