The last work my computer processed was over half a year ago.

May be it has an easy solution: Try updating your BOINC version from 7.16.11 to the newer 7.16.20 and resetting Gpugrid project.
After that, additionally, some patience is needed, as soon as work is lately scarce at Gpugrid...
Your GTX 1660 system should work.
Your GT 730 wouldn't

The last work my computer processed was over half a year ago.

Thanks!

ACEMD 3 task

I also didn't see new tasks appear with my Linux boinc version 7.16.16.
I think here is no updates available.

There is the latest 7.18.1 from the Ubuntu 22.04 LTS distro. I know of that one. Whether the other Linux distros have that version available I don't know.

I have no issues getting GPUGrid work every day on multiple hosts on Ubuntu 20.04 using a 7.17.0 client I use as a team client we compiled ourself.

Also have used a 7.18.1 client I compiled on my development partition and it works and gets tasks also.

I get new tasks almost every day. they are _0 which means they are brand new freshly minted tasks.

so new work is still coming out, but not in large volumes. so if you want work you need to ask for it very often to catch when they are available. my systems are set to request work every 60 seconds.
____________

I get new tasks almost every day. they are _0 which means they are brand new freshly minted tasks.

so new work is still coming out, but not in large volumes. so if you want work you need to ask for it very often to catch when they are available. my systems are set to request work every 60 seconds.

I get new tasks almost every day. they are _0 which means they are brand new freshly minted tasks.

so new work is still coming out, but not in large volumes. so if you want work you need to ask for it very often to catch when they are available. my systems are set to request work every 60 seconds.

my systems, too, are set to request work in short intervals.
However, I have not gotten any new ACEMD3 tasks for the past 3 days.
From what I saw, your systems run on Linux, mine on Windows.
Which means GPUGRID now provides ACEMD3 tasks for Linux only :-(

GPU Grid need to be removed from all compétitions.
No any respect to cruncher. No any reaction from admin.
Nice research, but no any WU. No reactions. Nothing !! Is this PRJ still active ???

____________

GPU Grid need to be removed from all compétitions.
No any respect to cruncher. No any reaction from admin.
Nice research, but no any WU. No reactions. Nothing !! Is this PRJ still active ???

Yes GPU Grid is in compétition !
Look on SETIBZH and Formula Boinc !

Yes I only run Windows, all my host are "open" with death line of 3 days. So enough to get work,

You misunderstood. GPUGRID has nothing to do with these “competitions”. They are third party events that have nothing to do with GPUGRID’s organization or control. You need to take it up with the event organizer.

To get any work here lately, you need to have your system setup with a script to run every minute or so asking for more work. When work becomes available it’s snatched up quickly.
____________

Well, the tasks availability has been really bad for the past few months.
Even worse: one of my hosts which is still trying to get GPUGRID work was lucky and received 2 WUs yesterday: however, both of them were terminated by the server :-(

I have been member here for more than 7 years, but I am sorry to say that the situation has never been as bad as it is presently :-(

And when someone here recently has criticized the lack of reponsiveness of the project people - unfortunately he is right, this is something I have found annoying over all the years.

To get any work here lately, you need to have your system setup with a script to run every minute or so asking for more work. When work becomes available it’s snatched up quickly.

the project could also help alleviate this by simply setting their requested delay to something much greater than 31 seconds. since they have an IP block on their network for DDoS protection, and it seems to also expire around the 30-60s mark, having their own configuration telling clients to bang away every 30s leads to situations where people with multiple hosts at the same IP get themselves perpetually blocked from accessing the site, with through the web browser or via BOINC. I've brought this up before.


maybe like 2-5 minutes would be more appropriate. the shortest tasks ive seen from this project have been about 20 mins crunch time, and that was like 2 years ago. all the tasks now run for hours, literally no reason for a ~30 second project delay.

but the script solution to stop requesting work while you have active tasks can be done utilizing boinccmd, some regex, and some simple loops.
____________

on the other hand: all these discussions would not be necessary if there was a sufficient number of WUs available :-)

the issue of a cooldown/delay being too short would still be a problem.

but the project can't just invent work for the sake of doing work. it needs to be meaningful and align with their goals.
____________

the issue of a cooldown/delay being too short would still be a problem.

but the project can't just invent work for the sake of doing work. it needs to be meaningful and align with their goals.

... As far as this project, the last few years have been rough

What else can you say?

Anyone willing and able to pick up the challenge of developing a 'work request' script which suspends the flow of update requests when the host has active tasks for the project?