PS,
perhaps the camb_boinc2docker work generator shouldn't even work faster than it does. Given that the tasks have a run time of just a few minutes but produce results files that are 2.6 MB big, I wonder if Cosmology@Home's internet connection bandwidth is another limit which prevents a higher production rate here.

(In other words, camb_boinc2docker tasks are not very effective from the Distributed Computing point of view, because of too short of a run time and too large network transfers.)

I have to say that even access to the Cosmology website itself (just browsing) is sometime quite slow...so, maybe bandwidth is an issue.

But it would be helpful if more work was available...

Hi all,

It looks like the validator has reduced the 160,000 backlog down to something like 83,000, so that's really good news for the Sprint...

Maybe the validator has been fixed or at least some "tweaks" have been made so that tasks are being rewarded with credits...

So, well done to the project admins if that's the case :-)

Hi all,

It looks like the validator has reduced the 160,000 backlog down to something like 83,000, so that's really good news for the Sprint...

Maybe the validator has been fixed or at least some "tweaks" have been made so that tasks are being rewarded with credits...

Yea, I figured out the problem Friday and have set it to work on the backlog since then. It won't completely finish by the end of today but better than nothing.

So, well done to the project admins if that's the case :-)

Thank you!

My first post here but just wanted to say thanks for your hard work in getting things moving and on your work for a good cause in general Marius!

Yea, I figured out the problem Friday and have set it to work on the backlog since then. It won't completely finish by the end of today but better than nothing.

Hi Marius

That's great news...very well done to you and your helpers :-)

Marius, thank you.

I ran camb_legacy for half a day on Thursday until I had time to add Virtualbox on hosts which didn't have it before. Current status of my camb_legacy results: 90 % valid, 10 % pending validation (not counting tasks which I aborted once I had vbox sorted out).

PS,
I don't particularly like to have vbox's kernel modules on my machines due to their bad track record WRT kernel stability in the past (works for me currently though). And I do not like the footprint and subpar BOINC integration of vboxwrapper based DC applications. But I acknowledge that it may be a help to application development, and also recognize that results from camb_boinc2docker are of more value to the C@H project now.

Marius,
Is the project in need of hardware donations?

Yea, I figured out the problem Friday and have set it to work on the backlog since then. It won't completely finish by the end of today but better than nothing.

Thanks a lot Marius !!

atp1916 wrote:

Marius,
Is the project in need of hardware donations?

We need to send equipment (packed up safe for transport) to Marius and his fellow cosmologists until they finally figure out what's been up with all the as yet unaccounted matter in this universe.

Thanks for working overtime to fix the issues Admin!
I can report all but 8 of my tasks are validated at this point :D

I'm very happy to have C@H participate in the Formula BOINC sprint, however, I do wish the organizers would have contacted me earlier, then we could have built a much bigger work pool in preparation (by the time I saw this post yesterday it was too late). We could have also communicated better to the sprinters the ongoing issues with the camb_legacy app, and pointed everyone to be running only camb_boinc2docker.

To clarify / confirm what has been said, camb_boinc2docker validation is running completely smoothly. Work generation is also running at normal pace, but demand is very high so it is likely slow for clients to grab workunits. camb_legacy validation on the other hand is currently broken and has been for several weeks. For those participating in the sprint, its unlikely I can fix it in time for the Sunday deadline, unfortunately.

I think we all Wish this.
Thanks for looking into this.
I will Drop this Project until the Formula BOINC Sprint is over mostly because I do not care to have my computers running 24 Hours a Day for 3 Days with no work.
(Not due to the Project but due to the Sprint and lack of Formula BOINC lack of support to Projects and to Members)

---

Crunching@EVGA The Number One Team in the BOINC Community. Folding@EVGA The Number One Team in the Folding@Home Community.

Yeah cause F1 runs on equal ground when every car ends up a lap down except for the top 3 teams. And when the leader can lose 160HP and still no one can pass him.

If projects don't want to participate they can ask to not be included. FB is NOT NEW. It's been running for over a decade.

Maybe but how can a Project be excluded if they are never asked in the First Place?
Also by "equal ground" being they all get 100 Gallons of Full not some getting 100 Gallons and some only 50 Gallons of Full.

Because its over a decade old. That's how to not be included. FB is not new.

People complain every week about it. It's getting old.

I will Drop this Project until the Formula BOINC Sprint is over mostly because I do not care to have my computers running 24 Hours a Day for 3 Days with no work.

Hi

You do realise that if you are crunching on one main (primary) project and it runs out of work, you can get work from other projects, where the "Resource Share" of the secondary project(s) is set to ZERO.

So, once you run out of work from the primary project, BOINC Manager will download ONE work unit per CPU, so your PC will keep crunching but on the secondary project.

Once the primary project has work available and downloads it, normal service will resume.

So, your PC can always be crunching even if not on the primary project :-)

Marius,

FYI, the sprint is over since 14 hours now.
The server status page currently shows:

application ....................... unsent .... in progress
----------------------------------------------------------------
camb_legacy .................. 0 .............. 52906
camb_boinc2docker ....... 0 .............. 9137

0 unsent looks correct to me because no tasks are received by my clients now. (I didn't try hard though.)

But 62043 in progress is likely incorrect. My own tasks list shows 2 tasks in progress which the hosts reported as complete mid Friday, and 11 tasks which they reported complete mid Sunday. The clients must have received proper scheduler replies that the reports were taken by the server, otherwise I would still see these tasks locally, of course.

I don't worry about the credit for these 13 tasks. I am only mentioning it just in case there is something odd with the database in general.

Some graphs from stats3.free-dc.org:

Daily points added:

This dramatic increase in PPD is certainly to be attributed to the camb_legacy validator put back into operation, and only to a small part to the sprint activity. The validator began its work on Friday, July 20, 12:48 UTC, but stats-free-dc picked it up first with their Saturday update.

Daily teams added:

Nothing unusual to see here.

Daily users added:

Again, the effects of the camb_legacy validator operating again is dwarfing any effect that the sprint may have had. free-dc's Saturday stats update was the first to catch points of validated work from many users who joined during the 4 weeks during which the validator was off.

Daily hosts added:

Here we may see a certain effect of the sprint announcement on July 18 22:00 UTC, and then on Saturday again a huge effect of the validator fix. Most of these hosts were surely added during the past 4 weeks.