I looked for the standard wrapper app name in the processes and didn't see it. So you just renamed the standard wrapper app with the 'g' name.

I have yet to receive any of the 5_Gaia tasks and app. Are we going to have to exhaust all the 4_Gaia tasks before we get to the 5_Gaia tasks?

[Edit]
Spoke too soon. I see I have crunched two of the 5_Gaia tasks and one them errored out on 'exceeded time limit' The task only ran for 662 seconds. So obviously didn't reach the new rsc_fpops_est limit.

I also see that almost all of the tasks since you changed the limit have errored out for exceeding the time limit. And that is only having crunched for just several hundred seconds.

So the new app didn't entirely solve this other problem.

I suggest reverting the task generator template back to your original settings that was working for everyone except mmonin. The issue is with your app speed in your template. I have never see other researchers modify that value in the templates. They just normally push out the rsc_fpops_est value.

I am remove Gaia 5 ......

What about all the 4Gaia tasks which are erroring out too. Only 1 of my 412 errored tasks was a Gaia_5 task.

If Gaia 5 will be working correctly (5 is only for test new solution), will take over tasks from Gaia 4

I don't control the benchmark and have done nothing to influence it. I believe it runs most of the time after client start.

That's not even the highest benchmark I have for a 5950x and a 9950x is above that. I see clients of older generations or fewer cores with higher scores than my 5950x PCs and other scores above mine. My PCs are within what I see here from the other clients.

I re-uploaded Gaia 5 with a calculation limit of 3 hours inside the program. If the returned results are acceptable, this will be the solution with the calculation time. This score behaves strangely.

score does not really reflect the speed of computer calculations

It DOES affect the accuracy of task estimations. The benchmark scores are directly implemented into the APR of a host (average processing rate) of each application after 11 validated tasks for that specific app is completed by the host for that app.

Still not getting the Gaia_5 app and tasks on most of the hosts.

theoretically yes, but practically according to this indicator the program should execute faster without timeout and it doesn't

All 4_Gaia tasks still erroring out for exceeded time limits with the new task properties.

So why haven't you deleted all these 4_Gaia tasks which are pointless so that hosts can get the new 5_Gaia tasks that you say have been fixed with proper app speed changes?

It's alright Keith, I am helping to get rid of them, they don't run long.

Yes could be cleared out if you know the exact batch that is faulty, but we are getting through them slowly.

zupa is working hard to fix the problems, and I appreciate his efforts, for keeping the project going, as a lot of us thought it dead after nearly a year of nothing.

Conan

---

If he doesn't understand what he is tweaking in the task properties, he should ask for help in the Boinc developer forums or from other knowledgeable project admins. I can suggest the admins/scientists at GPUGrid who know the ins and out of the rsc_fpops_est values for the work generator templates quite well as one project also with very short task deadlines.

@Conan Appreciate you helping to remove all the bad tasks. My hosts have plenty of other cpu work they could be crunching with the wasted cycles on Gaia@home. So I set NNT this morning when I saw this issue was not going to be fixed quickly.

@Conan He could just kill all the 4s and recast them with the 5 settings, couldn't he?

Well, I just took another batch of Gaia 4s and looks like all 60+ of them are erroring out after running for 1h39m. I'm NNT till they're all gone from the que. Back to Asteroids for tonight...

@Conan He could just kill all the 4s and recast them with the 5 settings, couldn't he?

Well, I just took another batch of Gaia 4s and looks like all 60+ of them are erroring out after running for 1h39m. I'm NNT till they're all gone from the que. Back to Asteroids for tonight...

+1

@Conan He could just kill all the 4s and recast them with the 5 settings, couldn't he?

Well, I just took another batch of Gaia 4s and looks like all 60+ of them are erroring out after running for 1h39m. I'm NNT till they're all gone from the que. Back to Asteroids for tonight...

+1

Well you will do what you want to do.

Things will be worked out, sometimes takes a bit of time.

Conan

---

@Conan He could just kill all the 4s and recast them with the 5 settings, couldn't he?

.

Better to just delete those tasks that have not been sent out yet or returned for recycling when the tasks errored out. Those already sent to the crunchers, please leave the tasks alone and let the crunchers complete or abort them (their choice).. Don't want a similar incident that happened with gpugrid recently. Just a good practice in my opinion.

As long as there are successful tasks been completed and validated, best not to cancel tasks already on active hosts. As of this writing, free-dc latest stat update still show credits been granted, so people are still returning validated result albeit getting less than before.

The number of 4_Gaia@home tasks has dropped to less than 3,000 now.

The number of 5_Gaia tasks has increased to almost 21,300, but these are yet to be released as none are being processed yet.

Maybe cleaning out the 4's before the 5's are started?

Conan

---

The number of 5_Gaia tasks has increased to almost 21,300, but these are yet to be released as none are being processed yet.
Maybe cleaning out the 4's before the 5's are started?

Conan

I killed 2 wus 4_Gaia, 'cause i have to restart my linux machine sometimes and these restarted every time from 0%
And now downloaded other 2 4_Gaia :-(

All 21,000+ 5_Gaia work units have been removed, maybe to fix a setting.

Conan

And a minute later 2,700 work units reappear.

---