Science United reports for every project the CPU usage and the GPU usage, and the relative weight. Mostly CPU usage is greater tha GPU usage. There is only a project, GPUGRID where the reverse is true.
Tullio

---

Science United will be reporting the BOINC figures - it has no independent source of data. The BOINC estimates of how much CPU support will be needed for a GPU application are notoriously unreliable: they take no account of the programming language used (which makes a huge difference), and they are not adjusted in the light of observed reality.

found a Science United Account with 2.8K hosts and a lot of tasks in progress ...

Science United is a collection of thousands of different people that use that platform to crunch BOINC projects instead of manually attaching to projects. no one person is managing all of the computers on that account.
https://scienceunited.org/

It's a dumbed down way to run boinc for the social media generation. One step towards the society depicted in the movie 'Idiocracy'.

. . I recommend a Sci-Fi short story called 'The Marching Morons' by C.M.Kornbluth (also nicely subtle in the title 8-})

Stephen

:)

+1 I have always liked that story :)

Tom M

---

A proud member of the OFA (Old Farts Association).

"Results waiting for db purging" may exceed " Results returned and awaiting validation" in the next few hours !

At this rate soon they will pass the Results out in the field too. LOL

---

At this rate soon they will pass the Results out in the field too. LOL

I think that will probably be at least 24 hours at the current rate.

Average turnaround times are now more than 7 days for both V8 and AstroPulse, they were below 7 days for the last few days.

Will they send out one last wave of forced resends? I still have Validation inconclusive WUs that need a third wingman

At this rate soon they will pass the Results out in the field too. LOL

I think that will probably be at least 24 hours at the current rate.

Average turnaround times are now more than 7 days for both V8 and AstroPulse, they were below 7 days for the last few days.

. . That was only because the resends were mostly being processed pretty much immediately.

Stephen

. . .

Will they send out one last wave of forced resends? I still have Validation inconclusive WUs that need a third wingman

I think at this stage, it might be more effective to Cancel unstarted Tasks for Workunits that are Already Validated.
There are probably now more than 100,000 Tasks still In Progress that are not needed.

This might help more quickly than just sending out more
The ones In the field will probably be returned eventually, but they might be waiting for their Hosts to process unnecessary duplicates first !

Will they send out one last wave of forced resends? I still have Validation inconclusive WUs that need a third wingman

I think at this stage, it might be more effective to Cancel unstarted Tasks for Workunits that are Already Validated.
There are probably now more than 100,000 Tasks still In Progress that are not needed.

This might help more quickly than just sending out more
The ones In the field will probably be returned eventually, but they might be waiting for their Hosts to process unnecessary duplicates first !

That is an interesting idea. I manually went through my list of WUs and prioritized the ones that didn't already have a matching valid, but it was effort on my part. Most people don't do anything but let boinc run. I'm now just crunching WUs that already have matching valids.

edit: secondary projects with shorter deadlines might also be delaying seti WUs

That is an interesting idea. I manually went through my list of WUs and prioritized the ones that didn't already have a matching valid, but it was effort on my part. Most people don't do anything but let boinc run. I'm now just crunching WUs that already have matching valids.
edit: secondary projects with shorter deadlines might also be delaying seti WUs

. . That is why I have my secondary project set to resource 0%. It mean there is very little waiting to run S@H work if any turns up. But since there is none that doesn't make much difference ...

Stephen

. .

. . I recommend a Sci-Fi short story called 'The Marching Morons' by C.M.Kornbluth (also nicely subtle in the title 8-})

Stephen

:)

+1 I have always liked that story :)

Tom M

+1
Nice to see it's online now for free reading.

---

I'm now just crunching WUs that already have matching valids.

I'd simply abort them, on point wasting time on them.

I'd actually expect aborting such tasks by the server as part of "nice" shutdown, wasting other people's electricity and eventually slowing down science done by other BOINC projects by generating data for dev/nul isn't what I imagine as nice way to finish the project.

But somehow I've expected it, so I didn't even try to cache many WUs, just finnished what I had and moved to Einstein, there are more than enough machines who can crunch ready what's left. Perhaps even too many and that leads to the current situation...

---

Perhaps even too many and that leads to the current situation...

The problem is that Boinc prefers handing any new tasks to those hosts that already have work.

Hosts that have work do scheduler requests as often as the cooldown allows. Empty ones end up having several hour backoffs between requests. So the empty hosts that could return the results almost immediately never get them.

It's a dumbed down way to run boinc for the social media generation. One step towards the society depicted in the movie 'Idiocracy'.

As time passes, Idiocracy is looking more like a documentary. [:o(

---

David Anderson has updated the list of the 100 top users. Most of them run Collatz, so the list does note reflect the real position of users, like me, who do not Collatz- But I am only a dumb user, those running Collatz are geniuses.
Tullio

---

The problem is that Boinc prefers handing any new tasks to those hosts that already have work.
Hosts that have work do scheduler requests as often as the cooldown allows. Empty ones end up having several hour backoffs between requests. So the empty hosts that could return the results almost immediately never get them.

. . It isn't just that, I am running a batch file to hit the server at the minimum backoff period every time so NO prolonged backoffs, but I get ZERO resends. It is very much a lottery, a matter of hitting the server at just the right moment within windows that are/were very short. Some get lucky (Wiggo) and some don't (me). BTW, I bought that scratchie .. as expected nothing :( Your turn when you 'get into town' :)

Stephen

:)

. . It isn't just that, I am running a batch file to hit the server at the minimum backoff period every time so NO prolonged backoffs, but I get ZERO resends.

Now that may have been your problem Stephen as I was just letting it do its own thing. ;-)

Cheers.

April 22 0:40 UTC
I've still got 259 Pendings and 342 Inconclusives

April 22 23:20
My Pendings are down to 145 and Inconclusives 237.

April 23 22:21
65 Pendings, 145 Inconclusives.

25 Pendings, 101 Inconclusives.

---

Grant
Darwin NT

. . It isn't just that, I am running a batch file to hit the server at the minimum backoff period every time so NO prolonged backoffs, but I get ZERO resends.

Now that may have been your problem Stephen as I was just letting it do its own thing. ;-)

Cheers.

. . But then as Ville says (or was it Siran), it simply stops polling for work when you have none to return. I was letting it do that but it was only polling a few times a day, it was ridiculous.

. . Either way ... no work :(

Stephen

:(