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?

Arivald,

It looks like you a running a homebrew application on that host. I would recommend recompiling to be the latest version on the github code or running it with the application provided from the server. If there are still issues, let me know.

Jake

It's not that they can't be contacted. They don't care, of they don't know that there is a problem. Some people want to use their AMD GPUs, but aren't aware that they do not have DP capability.

That part caught my eye. I have an older Nvidea that SETI keeps sending a message through BOINC saying "upgrade your driver" to run SETI on your graphics card, but there isn't a newer driver, and it runs tasks anyway. Presumably this lacks DP? Funny thing is, they're showing as completed and validated.

[1] I don't use AMD GPU's, mine are NVidia.
[2] As to BOINC's anti trashing code, I wasn't aware it even existed
[3] I've not checked on who trashes what on MW@H, I agree if someone repeatedly
trashes WU they shouldn't get any until they stop doing so.

[4] Unfortunately projects using BOINC still persist in allowing anon users who cannot be contacted. I believe there is NO valid reason to allow anon crunchers,
its a license for abuse, of both the project and those who are contactable and do crunch with more valid than otherwise tasks.

[5] There always going to be tasks that fail to validate, for some reason, computer malfunction, driver problems or power failure whatever, but if you cant
even contact such a user, there is no way of stopping them carrying on trashing tasks. Other than possibly the facility you mention if it can be implemented server side.

However given the recent problems with MW@H servers, and the number of folks complaining about lack of WU and server errors I don't know if implementing that facility might not be a great a problem as the trahers:-/

Hi Arivald,

Actually that was logical. It wouldn't be easy to make task validation per chunk. There is such validation method in ClimatePredicion.net, but I believe it's rather custom, and only because each part takes 2 days or so :)

IMHO, fixing issues with Hosts that all generate only invalid issues will go a long way towards decreasing invalid results as a whole.

Having a bundle end up as a computational error isn't that important, it will be resent to others so anyone winging it will still get a valid result [if it completes ok and IS valid].

Its only the person[s] that generate an error that doesn't get credited for it.

if the app processes all of the bundle BUT fails on the last of the 5, with
a computational error.. ALL 5 are lost, not just the one that actually failed.

Since the entire bundle is labelled as computational error..

Well, if that is correct, then Jake has to go back to the bench and improve the server logic with respect to the validation code.

Michael.

if the app processes all of the bundle BUT fails on the last of the 5, with
a computational error.. ALL 5 are lost, not just the one that actually failed.

Since the entire bundle is labelled as computational error..

Well, if that is correct, then Jake has to go back to the bench and improve the server logic with respect to the validation code.

Michael.

Are you sure? I've compared all the cards and worked out the cost of buying them plus the electricity they use, and an R9 Fury X is the best by far. Everything else uses as much electricity but does less work. The electricity is the main cost, not the card itself.

Hello everyone,

Is anyone running a 390 or 390X (290 or 290x may have the same problem)

I still have the problem, when i run several WUs at once, then after some time (from minutes to one hour or so) some WUs start to hang, and go on for ever, while one or two crunch on.

I have tested drivers since 15.9, always the same problem, win 7 or win10 does not matter either. Tried different hardware setups, new installations of windows or old ones no difference.

I hope someone can confirm the problem, so we can start searching for the root cause and maybe even a fix.

PS. Running on the 280X or 7970 doesn't give me the error. Also running one WU at a time is fine.
Running 2 Einstein@home WUs at the same time causes calculation error (invalid tasks)

Discriminating against failed WU or similar does make more sense to me though as that might gunk up the works a bit, even though I might technically fall under this category for the time being. I can assure you that isn't my intent. Hopefully my comments in this thread have helped shed some light on these issues as well.

Pointing fingers doesn't solve the problem. My computer has done a lot of good work for this project, and as mentioned, has been within the top 5 performing hosts in the not too distant past. Off the top of my head, I think it got up to 4th place, but had been within the top 10 for a few months. I hope to get it back up there again after I get these issues sorted out.

Hey Everyone,

Sorry for the silence yesterday, I decided to take a day off yesterday to recharge a bit after the huge push I've been doing for the last two weeks. I will be working on the Linux GPU apps today, the Mac applications, and if I have time I will look into fixing the cosmetic issues with the progress bar.

Jake

I seem to be getting some computation errors now though, so I'm going to try dialing it back down to 5 task per GPU to see if that fixes it. We'll see. I've typically been running 4 per GPU in the more recent past (last few months).

Still getting some errors. It may be on the CPU end as the tasks seem to occasionally error out at the same time when they switch between the bundled tasks and load the CPU.

See my previous post for Titan Black performance. If left running, this will likely place my host PC within the top 5 performing PCs crunching for MW@H.

Updated to 6 MW@H 1.43 WU bundles running per GPU, 12 total. Also allocated more CPU headroom so WUs are finishing about 3:28 (88s) total. GPUs are loaded up to around 93%, VRAM up to around 3668MB (59% on SLIed Titan Black cards, so the memory usage is double from being mirrored between cards – expect roughly half this on independent cards).

Like what? I have a 600W PSU on the XP machine but limited cooling. The Win10 machine is an HP slimline requireing a half-height boad and only has a 350W PSU.

Please observe these work units.

This is expected.
https://milkyway.cs.rpi.edu/milkyway/result.php?resultid=1887793313
Name: de_modfit_fast_19_3s_136_bundle5_ModfitConstraints3
Run time: 20 min 41 sec
Credit: 133.66

This is not expected.
https://milkyway.cs.rpi.edu/milkyway/result.php?resultid=1887790878
Name: de_modfit_fast_19_3s_136_ModfitConstraints3
Run time: 4 min 5 sec
Credit: 26.73

It appears there are some work units getting thru that are not bundled, but run 5x as long as an old single work unit and pay 1/5 as much. I have a handful of these.

On the XP machine, Milkyway WUs taking about 20 min of run time and using about 40% CPU.

On the Win10 machine, Milkyway WUs taking about 30 min of run time and typically using less than 10% CPU time (fairly large variation in CPU time).

I don't consider that running the current Milkyway WUs on my XP machine is an efficient use of the machine due to the high CPU usage, so I have discontinued running them until such that (or if...) a new version of the app is released that requires less CPU time.