Hello Crunchers,

We will no longer be sending work units out through the Modfit project. You will still receive work units tagged as Modfit, but they will not be coming from the official MilkyWay@home application.

Thank you for your patience during the transition.

Jake

Thanks for the heads up Jake.

But i get new WUs for some hours now, they look like this:

de_modfit_fast_15_3s_fixedangles_simBPL_1_1468263296_787598

all WUs with "fixedangles" just error out.

I just took them down.

Jake

More fixedangles today. They are quickly erroring out in hundreds, deferring next communication up to 24 hours - a major downside for unattended machines.

Have to agree with Vortac, the tasks got fewer, but there are a lot of them again now.

Hey guys,

I started new fixedangle runs today. Had a different, but still bad parameter file. Sorry.

Jake

Thanks Jake.

It looks better now, some of the "fixedangles" still error out.

At a closer look, the fixedangles_simBPLfixed2_3 (2_2 and 2_1) run through, the 1_1 and 1_2 error out.

I guess we have to run the 1_x versions through until they are gone?

Edit: Some of the 2_1 error out as well.

Yes, things are better now than yesterday, but some computational errors are still appearing from time to time. Normally, it wouldn't be a problem, but every computational error further postpones next communication with the server and the machine quickly runs out of workunits (unless you force manual updates all the time).

Hey everyone,

I put up fixed runs, but it will take a little while for all of the old ones to filter out of the scheduler. Hopefully everything should be running smooth soon.

Sorry.

Jake

It's a job well done Jake. I am closely following the total average computing figures on Applications page - it's hitting 79 TFLOPS already, even with the bad batches still being filtered out. It was around 55 TFLOPS only few days ago.

Good to hear! I am still going to keep trying to tune what I can server side to make sure all of your machines are getting enough work units to keep them busy. Hopefully you will see higher numbers soon!

Jake

All modfit workunits I get automatically abort themselves now even though I haven't aborted them. They abort themselves immediately after downloading.

All modfit workunits I get automatically abort themselves now even though I haven't aborted them. They abort themselves immediately after downloading.
de_modift_fast

I wonder if someone can answer me definitively on the following questions, I've scoured through the forums but can only find a partial answer.

Am I right in saying that there is no more mod fit app, & the mod fit program is now the main milkyway app? With it's only WUs being the 133.66 credit WUs?
Which in turn means the MW v1.0x app & it's WUs (106.88 credit) are now no more?

I've been running the MW benchmark threads for a few years & it'd be handy to know if the benchmark WU has gone for good! ;)

TIA

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Am I right in saying that there is no more mod fit app, & the mod fit program is now the main milkyway app? With it's only WUs being the 133.66 credit WUs?

That's most likely true.
Current WU name is:
de_modfit_fast_*_*_*_bundle5_ModfitConstraints*_*_*_*_*

So I think that we won't ever be back to old WUs. Since those are "fast" and most likely compute the same results using less GPU time.

Currently my AMD R280X (7970) when computing 4 Bundled (*5) WU at the same time gets a bundle in average time of 120s. This gives us:
4*Bundle = 120s
1 Bundle = 120s/4 = 30s.
1 WU = 30s/5 = 6s.

Credits throughput is similar to old WU (currently between 380k and 400k credits/day). CPU usage is higher. Bundles did increase throughput and stabilized server. I'd hope for Bundle20 or Bundle100, these would increase stability even further and allow my PC to contact it even less often, gave me a bigger work buffer, but... :)

Cool, thanks, yea I've noticed the higher CPU load, CPU type & speed now has a significant affect on GPU times.
I'll be starting a new benchmark thread here soon, you can see the 1 I've started at AnandTech if you like here https://forums.anandtech.com/threads/milkyway-h-benchmark-thread-winter-2016-on-different-wu-gpu-cpu-times-wanted.2495905/
Still ironing out some issues atm (HT related) & there's no stupid time limit on editing posts there ;).

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Cool, thanks, yea I've noticed the higher CPU load, CPU type & speed now has a significant affect on GPU times.
I'll be starting a new benchmark thread here soon, you can see the 1 I've started at AnandTech if you like here https://forums.anandtech.com/threads/milkyway-h-benchmark-thread-winter-2016-on-different-wu-gpu-cpu-times-wanted.2495905/
Still ironing out some issues atm (HT related) & there's no stupid time limit on editing posts there ;).

Have you heard of WUProp? It should have a lot of data.
http://wuprop.boinc-af.org/results/delai.py

Nope, I had a look though, can't see how much data at all, am I missing something?
All I see for MW@H is this graph http://wuprop.boinc-af.org/results/graph_delai.py?projet=Milkyway@home&application=MilkyWay@Home

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Nope, I had a look though, can't see how much data at all, am I missing something?
All I see for MW@H is this graph http://wuprop.boinc-af.org/results/graph_delai.py?projet=Milkyway@home&application=MilkyWay@Home

http://wuprop.boinc-af.org/results/projet.py?projet=Milkyway%40home&application=MilkyWay%40Home

Computational time across CPUs and GPUs for any project/application. It doesn't have clock speeds, just if HT is on/off

Where did you find that? lol ;)

Anyway, yea without clock speeds it's of limited use, ok for a general idea of h/w performance differences.
My benchmark thread is about getting accurate times for specified h/w, so we know the differences between different h/w or clock speeds more precisely.
That's the aim anyway, it's not always easy ;), but mostly it works.

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7