Hey All,

I just released the newest version of nbody, version 1.64, for Mac single and multi-threaded. Please let me know if there are any issues.

PLEASE NOTE: We only have one mac machine for building and testing, meaning I had to test the binaries on the same machine that I built them on. So please let me know if anything strange crashing is seen.

Thank you all for your continued support,
Sidd

from general user
Do you have any packages that are custom made for users?
IE. My Tesla card takes two minutes to finish NVidia app and 8 cpu's takes 11 minutes to finish nbody sim, or 6 nbody sims an hour and 30 NVidia apps an hour.
One package = 6 nbody sims + 30 NVidia apps per hour.
Right now my tesla burns the NVidia apps up and sits idle for 2 to 3 hrs while the cpu's play.
Idea or going fishing?

Shayol Ghul, I would suggest not running Milkyway on your CPU, in your situation.

Find a project that does not have a GPU app, and run that on your CPU instead.

To the Admins/developers: Do you STILL have a much too low limit (80 tasks?) for Milkyway?

Hi 10esseeTony,

We have done things to mitigate the low task limit. We have started bundling workunits so instead of it being 80 single workunits, they are now 80 bundled workunits with 5 workunits each. This means that you effectively have 400 workunits.

Jake

I just began with milkyway some days ago.
I'using a iMac Corei7 from 2009, quad core (I let 6 of them working, from 50% to 65 /75 each), without GPU, it is an ATI GC non compatible.

Some of the units are doing quick and well, I already see them in the statistics (App called MilkyWay@home 1.46).

Yesterday I crunch a unit called "ps_nobody_8_24_****" (App called MilkyWay@home N-Body simulation 1.64).
Boinc told me that it would have been finished in 3h with my actual settings, but yesterday evening, the elapsed time was 6h40 and estimated time to finished up to 5d23h something and this morning it is 5 days3h something.

What can I do ? it is normal ? Have to abort this kind of N-Body unit ? If it continues I'll be late as the unit is due October 1st. I have more of this kind of units and I would rather use the Mac to crunch numbers I can actually finish on this project or the other ones I'm involve.

Thank you :-)

I finish the unit just in time, so it took 9 days to crunch it.
Some others with the same name don't take so much time.

I just began with milkyway some days ago.
I'using a iMac Corei7 from 2009, quad core (I let 6 of them working, from 50% to 65 /75 each), without GPU, it is an ATI GC non compatible.

Some of the units are doing quick and well, I already see them in the statistics (App called MilkyWay@home 1.46).

Yesterday I crunch a unit called "ps_nobody_8_24_****" (App called MilkyWay@home N-Body simulation 1.64).
Boinc told me that it would have been finished in 3h with my actual settings, but yesterday evening, the elapsed time was 6h40 and estimated time to finished up to 5d23h something and this morning it is 5 days3h something.

What can I do ? it is normal ? Have to abort this kind of N-Body unit ? If it continues I'll be late as the unit is due October 1st. I have more of this kind of units and I would rather use the Mac to crunch numbers I can actually finish on this project or the other ones I'm involve.

Thank you :-)