New CPU applications deployed for 32-bit Windows and 64-bit Linux. Windows version should also run on 64-bit Windows systems. So you should now disable CPU applications on project preferences if you don't want to use your CPU for this project.

There's a known problem with checkpoint interval (uses a default 2h interval) and core selection (selected core is shared with ATI/nVidia on the same host) for these applications. Both problems should be fixed in next application version so you should wait for that if you have a problem due to either limitation.

Additionally, CUDA requirements were changed to accept cards with only 64MB of memory.

With the new nvidia memory requirnment, does http://moowrap.net/forum_thread.php?id=16 need updating? I updated http://boinc.berkeley.edu/wiki/GPU_computing#Attach_to_projects_with_GPU_applications pointing to it so users can get the most curent info.

Since you now have a CPU client, do you plan to add OGR support to Moo! Wrapper ?

I changed http://boinc.berkeley.edu/wiki/GPU_computing#Attach_to_projects_with_GPU_applications, thanks for pointing.
Teemu will have to change the original post here.

I'm not sure we'll support OGR-27, since yoyo@home ( http://www.rechenkraft.net/yoyo/) is actually doing it.
Also, there's no GPU client for OGR at the moment.

A little heads up might have been nice as I came home to all 4 cpu cores cooking at 100% load in a 90'F room when I had CPU use set to disabled in my Moowrap preferences but then found it had been automagically enabled. Maybe default admin changes to not enable CPU and GPU use and let us enable to prevent possible meltdowns at our end.

A little heads up might have been nice as I came home to all 4 cpu cores cooking at 100% load in a 90'F room when I had CPU use set to disabled in my Moowrap preferences but then found it had been automagically enabled. Maybe default admin changes to not enable CPU and GPU use and let us enable to prevent possible meltdowns at our end.

I agree, the Default should have been not to run the CPU Tasks & let those that want to run them Enable it themselves ...

I also agree, CPU tasks should be disabled by default.
Like we already discussed, the CPU tasks won't make a huge impact, so i'm okay with disabling it by default.

However, the GPU utilization should be enabled by default.

Thanks for suggestion.

I'm not sure we'll support OGR-27, since yoyo@home ( http://www.rechenkraft.net/yoyo/) is actually doing it.
Also, there's no GPU client for OGR at the moment.

Your first argument is not valid since there are two wrappers for RC5 ;)

And since Moo! Wrapper is the only one allowing us to use our distributed.net account, I'd rather use it for OGR too instead of joining yoyo ...

A little heads up might have been nice as I came home to all 4 cpu cores cooking at 100% load in a 90'F room when I had CPU use set to disabled in my Moowrap preferences but then found it had been automagically enabled.

I did try to warn about this change (that CPU apps are coming) in some post here, although, obviously didn't make it clear enough. Too late now, I think. :(

Odd that the CPU units got enabled by default. That's a default feature of BOINC server software and I didn't make any decision to enable or disable them by default. I would have thought that a previously disabled CPU would have stayed so.

Where did you set CPU disabled? We didn't have that setting in project preferences beforehand (it's not visible there unless we have one or more CPU apps deployed) so it must have been somewhere else.

I apologize from anybody who had problems due to me adding CPU applications.

-w

With the new nvidia memory requirnment, does http://moowrap.net/forum_thread.php?id=16 need updating?

Latest requirements are documented in http://moowrap.net/forum_thread.php?id=41 post and that's kept updated as I make changes.

-w

However I set up nvidia based rigs gpu usage is minimal....50% peaks and constant drops to practically zero.

This is even with 50% processors dedicated to feeding the gpu's.

Just checking if that is normal?

Addendum: Just changed core selection thingy fron -1 default to 1 and now getting a steady 50%....still rubbish but better than it was.

Anyone know the best setting for cuda please?

---

Team Renegades
Forum

Darn.....it only worked for the one wu.....now gpu usage is all over the place again, fluctuating betwen zero and 50% constantly.

Addendum: Nevermind.

Sacrificing 2 cpu cores and get a max of 60% efficiency from my dual Cudas is pretty poor.

Relocated rig to target my other milestones....PG and Aqua.

---

Team Renegades
Forum

Addendum: Just changed core selection thingy fron -1 default to 1 and now getting a steady 50%....still rubbish but better than it was.

For CUDA, best core value to use has been 9-11. You would need to run a benchmark (there's instructions on another post here) to find out for sure which is the best one on your host, though.

-w