1)
Message boards :
News :
nbody 1.64 release for Mac
(Message 66675)
Posted 2 Oct 2017 by teo_paris Post: 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. |
2)
Message boards :
News :
nbody 1.64 release for Mac
(Message 66661)
Posted 22 Sep 2017 by teo_paris Post: 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 :-) |
©2024 Astroinformatics Group