System: AMD 1100T, 12Gig RAM, HD6990 GPU, Win7-Pro 64b, BOINC 7.0.26.

Loaded YAFU work unit first time and wouldn't start unless I first suspended ALL other CPU/GPU/NCI tasks. First WU ran fine after that.

Soo, I let everything go again and let it DL a couple more WU's to try. This time it started after I suspended the CPU tasks, but it stopped the GPU tasks and in the process crashed the Explorer Desktop. Rebooted, tried again, same result.

Soo, tried it again with the GPU work suspended and this time it ran fine...

Me thinks there is something buggy in the way that works. I see no reason to stop GPU tasks to run CPU tasks and this is the only project that demands such.

Is this a BOINC 7.0.26 problem or project problem or what ya think?

Thanks!

8-)

Seems to me there is a bug somewhere's

the same here.
yafu and gpu task(s)is a problem.

Am experiencing the same phoenomena with ubuntu 11.10. My GPU's worked in tandem with YAFU before the break but now YAFU seems to hog the total cpu resources. It's my uneducated guess that since most of my gpu work needs an assist with up to 50% of a single core, they won't initiate and merely stand by until BOINC hands off the resources to another project. I am running an i7 with Ubuntu 11.10, current on updates. As most of my Windows boxes are not presently running YAFU I can't confirm the problems with a Windows OS.

Has this system been fully tested ?

I am currently running another work unit on another PC.

Remaining elapsed time has expired but unit is still running, hopefully it will finish eventually.

The project does not use checkpointing.

Return times for work units are quite tight (2 days).

CPU time is repeatedly shown as negative at -0.08.08

Numerous messages also appear in the log to this effect.

No idea of percentage progress is shown.

Scoring seems low for this project.

I agree with all the problems indicated below and would also add that scoring semms to be based on elapsed time not CPU time, is this right.

The unit I have processed took 1 hour 34 minutes elased however across 2 CPU's I would have anticiapted around 3 hous CPU time .

Just aborted a work unit.

Elapsed time remaining expired at 47 mins.

Unit given 3 CPU's and still running after 2 hours elapsed.

Sorry but won't be doing any more of these until problems are sorted out.

Has this system been fully tested ?

Read the home page of the project, it starts with: "YAFU is a alpha project,..." This should answer your question.

I am currently running another work unit on another PC.

Remaining elapsed time has expired but unit is still running, hopefully it will finish eventually.

It will finish.

The project does not use checkpointing.

Long workunits have checkpoints. The checkpointing will be improved in upcomming versions.

Return times for work units are quite tight (2 days).

Yes, it is intended to be so.

CPU time is repeatedly shown as negative at -0.08.08

This seems to be a bug of Boinc not of the application.

No idea of percentage progress is shown.

Percantage progress is currently not possible.

Scoring seems low for this project.

The standard Boinc scoring system is used: http://boinc.berkeley.edu/trac/wiki/CreditNew

yoyo

Yafu over rides or ignores BOINC checkpoint options. I have checkpoint set at 60 second intervals. Yafu seems to be 30 mins when it does checkpoint.

Correction to lat thread Yafu checkpoint interval seems to be at least 60 mins.

Also indicated elapsed time seems to be much lower than real elapsed time. Unit I am doind said 2 hours 1 Minute. Currently over 2 Hours 30 mins. Am aborting unit if it does not finsh at 2 Hrs 45 Mins. Unit continued processing after remaining elased time had expired.

The remaining time is calculated by Boinc itself, not by the yafu app. I do not know the strange algorithm how Boinc does it and why remaining time is set to 0 even if yafu reports 0% progress.
yoyo

Have loaded the latest version of BOINC just to see if it makes any difference.

Unfortunately not.

Current work unit showing Minus cpu time (again).

Current work unit elapsed time, supposed to be 2 hours had reduced to zero and still running.

As it does not checkpoint will not reprocess as I have no idea how long it will take.

Sorry can't waste any more time on this project.