Mine was a bad translation into English by a poster at Rechrenkraft. Word order is important in English.

I finished looking at it yesterday. I could not find anything that helps me, a mere mortal cruncher, to do a better job. Most changes look like change just for the sake of change or for the sake of giant egos. I can say that recent releases are doing a better job seperating GPU crunching from CPU crunching. I also checked around some of the message boards and almost no one seems to like this release. The major complaints seems to be over the possible abuse of "notices" as you indicated.

Anyway ... I fell back to 6.10.58 and plan to stay there until there is some real need to make a change.

New & Improved? Berkeley seem to be in a rush to promote 6.12.6, but the new spiffy looking Simple View is buggy still, and that's only the surface... some buttons disappear or do not function ;?)



Screenshot on W7-64 with Aero on. The messages button is really giving access to the Notices view. Off late, my cache is not being backfilled timely even though the TTC total per BOINCtasks is substantially less than the buffer setting. No deferral tickers running, all parms nominal. Be warned!

Not fit for production: e.g. the additional buffer is multiplied it seems by the number of cores. On my duo, a 2.5 day cache gives 5 days work, a 2 day cache 4 days. This on 6.12.8 and 6.12.10. Reverting to 6.12.6 normalizes. Anyone testing with HCC selected as project and a cache setting of around 3.5 days and up will have a HP state or with 1 day and above after a while no more repair jobs or A Type ;>)

Also it seems the zero_debt flag is broken. Wanted to zero the LTD, but on client restart the work_fetch_debug still reports the (inflated) NEGATIVE values I'm having on WCG.

Just go to the check-in list (think you know where to find it)... and quite unsure everything in alterations gets entered there.

And something new I noticed: Before, the BM would not launch the core service if stopped (even if having rights). Now, a new app alert appears with W7 about a "boincsvcctrl.exe" needing permission to be launched (unsigned app). Could be some security software will start barfing when that newee arrives at members... here it alerted same way as were we back at the beginning of the Vista days.

--//--

txyankee, good idea; the Boinc Alpha/Beta is really just for testing, not set and run crunching.

Thanks for the comments. I have 6.12.8 on my local host which does limited crunching and I still have to give it a thumbs down. I have Milkyway CPU/GPU on it and it does have problems handling LTD. Milkyway CPU has some very long running wu's (N-body simulation) and it gives me much more than a 0.01 cashe. On a humerous note, I got my first "Notice" ... a ballon poped up with a 'lost connection with host" message. Since using BoincTasks, I rarely look at BOINC on the individual machines so some of the other "new features" are less irritating. I honestly can't understand where they are going in the future.



EDIT: BTW does anyone know how to delete "notices"?