Okay, I'm getting a LOT of tasks that have estimated completion times in DAYS rather than hours like these:



This has the effect of telling the BOINC client that a 1-day cache is already FULL and it won't fetch any more work from ANY project if all the cores are loaded up with same. Believe me, I have a 24-core setup that STOPPED fetching ANY new WU's from ANY project because it had 24 of these 4-Day long tasks loaded up.

The REALLY BAD THING is the tasks complete in no more than 4.8 hours!!! I've scanned hundreds of my tasks and the LONGEST I could find took 17334 seconds.

Sooo, for whatever reason, something has changed in the estimated completion times and it isn't on my end. This is totally screwing up my setups, especially those that have trouble getting WU's from other projects that have FEW WU's to go around. As the tasks near completion, naturally the estimated time decreases, but very slowly until about 4 hours done.



Meanwhile, BOINC thinks my 1-Day cache is full... what a lie...

Please fix this.

8-)

One setup has 62 of these 4-day long tasks in the cache... guess it won't be running anything else for years... sheesh...

For same batch of tasks, one of my machines shows 13 minutes, other one - 7 days... It's not project settings problem but different versions of manager differently calculate parameters sent by server...

---

Krzysztof 'krzyszp' Piszczek

Member of Radioactive@Home team
My Patreon profile
Universe@Home on YT

For same batch of tasks, one of my machines shows 13 minutes, other one - 7 days... It's not project settings problem but different versions of manager differently calculate parameters sent by server...

You're right, the 7.x clients with the per-application correction factor handle things a lot different from the previous BOINC versions.

For me all workunits I received in the past few weeks had fairly good estimated runtimes - but I disabled that per-application factor with a patch.

My current (project-wide, not per app) DCF is 91 but my core client shows 8:19 hours for a 5:30 hours result so it seems to have adjusted the DCF not too bad. Currently this project together with SETI Beta are the ones with the best estimated runtime - but keep in mind that I'm using a patched client.

p.s.: Not to be misunderstood ... I do think that the per-application correction factor is a good thing - but only if it works properly. I don't think that the current core client does it right.

Everything was fine on all my setups until a couple days ago... I don't think there is anything I could do on my end...

Well, we will see how things go and I will upgrade to 7.6.22 and see if that does anything...

8-)