Max # of simultaneous Milkyway@home tasks 7

Set this to "no limit". This setting is actually intended for projects with applications, which for example use a lot of RAM and running more than x of them simultaneously might cause issues. No need for that here for the average user, the cache settings alone will make sure, that you have your 0.2+0.3 days of work in your cache if that's what you want (I however suggest changing it to something like 0.49+0.01 or simply to 0.5+0.0, in particular if you are running more than one project simultaneously).

It is a problem with volunteer relations. The process sending out tasks could trivially issue a quorum in rapid succession even if the number of workunits in the queue is large.

What useful purpose is served by operating in a manner that causes unnecessary concern for people who are donating their resources?

I agree that the lack of proper communication requires us to extrapolate information. From our side, a sudden stop of credits being awarded is a big cause for concern.

However, I feel the sole developer here is overburdened and the lack of engagement is the consequence.

Getting the homepage or for that matter any page to load is a long process.
Homepage takes around 15 seconds to load and this page was not much better.

It would also be nice if you could clear out all the dead GPU tasks from our acccounts.
I am flooded with Validation pending (22) [all GPU] · Validation inconclusive (50) ·[all GPU] Valid (190) [11 are the new CPU tasks, the rest are GPU from a long time ago]· Invalid (83) [all GPU] · Error (225) [all GPU]

I believe buried somewhere down in all the forum threads is a post from the admin/devs that the attempt to develop a N-body gpu app was deemed infeasible and the attempt abandoned.

They need Petri's help, at least that way a Linux app would be available. It doesn't need to be incremently faster than cpu crunching, just comparable would help alot. Incremental steps can come thru time.

I'm on WIndows 10 with latest BOINC client and can't get any work. I'm using BAM so it still is pointed to the HTTPS site instead of the HTTP site I keep messages to point to.

From my log:

11/11/23 8:24:02 AM |  | Project communication failed: attempting access to reference site
11/11/23 8:24:02 AM | Milkyway@home | Scheduler request to url failed: Couldn't resolve host name
11/11/23 8:24:02 AM | Milkyway@home | Sending scheduler request: Requested by user.
11/11/23 8:24:02 AM | Milkyway@home | Requesting new tasks for CPU
11/11/23 8:24:02 AM | Milkyway@home | [sched_op] CPU work request: 28505.99 seconds; 0.44 devices
11/11/23 8:24:02 AM | Milkyway@home | [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 devices
11/11/23 8:24:02 AM | Milkyway@home | [sched_op] Intel GPU work request: 0.00 seconds; 0.00 devices
11/11/23 8:24:03 AM |  | Internet access OK - project servers may be temporarily down.
11/11/23 8:24:04 AM | Milkyway@home | Scheduler request completed: got 0 new tasks
11/11/23 8:24:04 AM | Milkyway@home | [sched_op] Server version 721
11/11/23 8:24:04 AM | Milkyway@home | This project seems to have changed its URL.  When convenient, remove the project, then add http://milkyway-new.cs.rpi.edu/milkyway/

(I'm not currently running any GPU work for ANY project)

Best,

Yav

Thank you for all the hard work. On my Linux machines, I have now added MilkyWay@home back successfully.

Question - Is credit for work done now working as well?

Not that I was aware of.
Are validated runs not awarding credit?

Credit "on" project appears to be fine. Credit and Stat's Export have not resumed yet

Last update user XML 2023-10-31 17:04:29 UTC (5 days 23:30:05 old)
Last update host XML 2023-10-30 17:04:30 UTC (6 days 23:30:04 old)
Last update team XML 2023-10-31 17:04:29 UTC (5 days 23:30:05 old)

Thanks
Bill F

Thank you for all the hard work. On my Linux machines, I have now added MilkyWay@home back successfully.

Question - Is credit for work done now working as well?

Not that I was aware of.
Are validated runs not awarding credit?