Posts by bowlinra

1) Message boards : News : New Nbody version 1.48 (Message 63226) Posted 14 Mar 2015 by bowlinra Post: I keep having the New Nbody version 1.48 continue to run after it shows 100% completion. Is there a way to keep from down loading these files. I do not want to suspend the whole Milkyway program, just want to stop this from happening. Here is an example: This file de_nbody_2_13_orphan_sim_1_1422013803_566832_0 showed a total run time of about 8 minutes and now has run for 8:58:56 with a remaining time of ---. Login your MilkyWay@Homeaccount. Edit MilkyWay@Home preferences -> Run only the selected applications Uncheck - MilkyWay@Home N-Body Simulation I'm only seeing the stalling on the 16C versions.
2) Message boards : News : New Nbody version 1.48 (Message 63223) Posted 12 Mar 2015 by bowlinra Post: Another stalled 1.48, usually runtime 17mins.. this one 3hr 32m. Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_1_1422013803_709308_1 03:32:22 (03:52:51) 100.0 100.0 - 10d,10:40:41 16C Running 26.99 MB fah23 - Amd 6176se 2.713Ghz
3) Message boards : News : New Nbody version 1.48 (Message 63215) Posted 12 Mar 2015 by bowlinra Post: Another stalled task 19+Hrs, other WU in this series (ps_nbody_12_20_orphan_sim_314*) run under 18 mins Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) ps_nbody_12_20_orphan_sim_3_1413455402_1997284_5 19:48:43 (19:49:19) 100.0 100.0 - 11d,00:16:35 16C Suspended by user fah24 - Amd 6272es 3.1Ghz
4) Message boards : News : New Nbody version 1.48 (Message 63196) Posted 3 Mar 2015 by bowlinra Post: Another one today: Project, Application, Name, Elapsed Time, Completed, Reported, Use, CPU%, Status, Computer, Virtual, Memory Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) ps_nbody_12_20_orphan_sim_3_1422013803_316785_5 09:23:50 (09:23:58) 100.0 100.0 - 11d,12:51:16 16C Running 22.22 MB fah21 - Amd 61xxes 3.0Ghz
5) Message boards : News : New Nbody version 1.48 (Message 63193) Posted 3 Mar 2015 by bowlinra Post: Another observation, the 1.48 16C units are not full utilitizing all the cores. I would expect to close to 1600 on the %CPU. I have 48 core AMD 6100ES, currently running 3x 1.48 16C and is only showing about 55% usage: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 57743 boinc 39 19 164m 25m 1788 R 936 0.1 21:28.01 milkyway_nbody_ 57169 boinc 39 19 157m 16m 1824 R 897 0.1 1885:26 milkyway_nbody_ 57711 boinc 39 19 154m 14m 1792 R 813 0.0 64:59.87 milkyway_nbody_ 267 root 20 0 0 0 0 S 0 0.0 0:16.82 kworker/28:1 1503 root 20 0 203m 21m 7532 S 0 0.1 26:24.08 Xorg Another server 32 core AMD 6272ES, currently running 2x 1.48 16C and is only showing about 70% PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 32002 boinc 39 19 168m 29m 1848 R 1184 0.2 45:34.81 milkyway_nbody_ 31999 boinc 39 19 154m 14m 1856 R 1082 0.1 102:30.81 milkyway_nbody_ 1206 root 20 0 214m 21m 7460 S 0 0.2 29:40.73 Xorg 32302 horde 20 0 17476 1408 944 R 0 0.0 0:00.18 top
6) Message boards : News : New Nbody version 1.48 (Message 63192) Posted 3 Mar 2015 by bowlinra Post: I cleared out all the 1.46.. I'm still get some rare 1.48 that are stall at 100%. Here are all the one I can easily find from my BoincTasks History. 3 Unbuntu 32/48 core server on boinc 7.0.65 and 1 i7-920 PC on boinc 7.4.36. I'd be glad to give you more information if you need it. Here are some: Project, Application, Name, Elapsed Time, Completed, Reported, Use, CPU%, Status, Computer, Virtual, Memory Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_1_1422013803_601749_1 01d,08:43:36 (01d,08:43:47) 25-02-2015 01:35 AM 25-02-2015 11:09 AM 16C 100.0 Aborted (203) fah20 - Amd 6272es 3.1Ghz Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_1_1422013803_643065_2 00:03:56 (00:03:56) 25-02-2015 01:35 AM 25-02-2015 11:09 AM 16C 100.0 Aborted (203) fah20 - Amd 6272es 3.1Ghz Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_1_1422013803_475467_1 00:01:19 (00:01:19) 25-02-2015 01:35 AM 25-02-2015 11:09 AM 16C 100.0 Aborted (203) fah20 - Amd 6272es 3.1Ghz Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_2_1422013803_808241_1 00:05:00 (00:05:00) 03-03-2015 12:21 AM 16C 100.0 Aborted (203) fah20 - Amd 6272es 3.1Ghz 24.54 MB 6.82 MB Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_1_1422013803_782698_1 10:10:25 (10:10:26) 02-03-2015 07:29 AM 02-03-2015 09:53 AM 16C 100.0 Aborted (203) fah20 - Amd 6272es 3.1Ghz 26.34 MB 8.85 MB Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) ps_nbody_12_20_orphan_sim_3_1422013803_339990_3 14:13:21 (14:13:36) 26-02-2015 01:40 AM 26-02-2015 05:25 AM 16C 100.0 Aborted (203) fah21 - Amd 61xxes 3.0Ghz 22.35 MB 4.68 MB Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_12_20_orphan_sim_3_1413455402_1688519_7 07:39:32 (07:39:39) 26-02-2015 06:31 PM 26-02-2015 09:08 PM 16C 100.0 Aborted (203) fah21 - Amd 61xxes 3.0Ghz 21.19 MB 3.65 MB Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_1_1422013803_730744_0 04:02:34 (04:02:36) 28-02-2015 02:35 AM 28-02-2015 03:14 AM 16C 100.0 Aborted (203) fah21 - Amd 61xxes 3.0Ghz 26.73 MB 9.07 MB Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_1_1422013803_505170_3 03:11:49 (03:12:03) 25-02-2015 01:33 AM 25-02-2015 01:36 AM 16C 100.0 Aborted (203) fah18 - Amd 6176se 2.713Ghz Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_1_1422013803_563877_0 00:51:54 (00:52:08) 25-02-2015 01:33 AM 25-02-2015 01:36 AM 16C 100.0 Aborted (203) fah18 - Amd 6176se 2.713Ghz Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_2_1422013803_652564_0 03:45:25 (21:35:00) 24-02-2015 06:34 PM 24-02-2015 07:34 PM 8C 100.0 Reported: Computation error (4,) Christy-i7-920 33.69 MB 34.88 MB * This one has an ODD time stamp; I just start crunch in 2/14/15 Milkyway@Home 1.48 MilkyWay@Home N-Body Simulation (mt) de_nbody_2_13_orphan_sim_2_1422013803_760581_0 05:20:30 (05:20:10) 01-03-2015 04:28 AM 01-03-2015 04:32 AM 8C 99.9 Aborted (203) Christy-i7-920 5.42 MB 6.52 MB
7) Message boards : News : New Nbody version 1.48 (Message 63184) Posted 28 Feb 2015 by bowlinra Post: I have heard what to do with all these stalled 100% done WUs, except abort them. Am I in the wrong message board to post these problems?
8) Message boards : News : New Nbody version 1.48 (Message 63182) Posted 26 Feb 2015 by bowlinra Post: Had another 4-6 stalled units, most appear be going thru ok.
9) Message boards : News : New Nbody version 1.48 (Message 63179) Posted 24 Feb 2015 by bowlinra Post: I've been running boinc for about 10 days now and was ran into your 1.46 wu. Pulled out most of my hair, because I thought I was doing something wrong. I've clear them out and have found two hung 1.48 WUs on different boxes. I'm not sure how best to report / show this issue, that could help someone solve it. So here goes.. Server is 48 cores - Amd 61xxes 2.8Ghz 877 Watts [H] v9.1 Client: 7.0.65 on Ubuntu 12.04 Expected run should be about 1hr 30mins App: ps_nbody_12_20_orphan_sim_3_1422013803_339990_3 Elapsed time: 03d,04:31:57 (03d,04:33:46) 100.0 100.0 - Deadline: 08d,17:27:28 16C Suspended by user Server is 32 cores - Amd 6272es 3.1Ghz 495 Watts [H] v9.1 Client: 7.0.65 on Ubuntu 12.04 Expected run should be about 45mins App: de_nbody_2_13_orphan_sim_1_1422013803_601749_1 Elapsed time: 01d,08:40:36 (01d,08:40:45) 100.0 100.0 - Deadline: 10d,02:05:59 16C Suspended by user Also the WU doesn't appear to be running with all 16C.. here is a top screen shot with 2 1.48 16C WUs running between 26% & 46% completed. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7191 boinc 39 19 154m 14m 1860 R 1056 0.1 136:32.74 milkyway_nbody_ 7320 boinc 39 19 25260 7440 1684 R 100 0.1 3:39.90 milkyway_nbody_ 1206 root 20 0 214m 24m 7640 S 0 0.2 4:50.99 Xorg Please let me know, if there a better way to report things like this in the future.