1) Message boards : Number crunching : download of milkyway_nbody_1.83_windows_x86_64__mt.exe: can't resolve hostname (Message 76663) Posted 29 Nov 2023 by keputnam Post: Deleted the hung download and reset the project again All is good and I'm crunching a new WU

2) Message boards : Number crunching : download of milkyway_nbody_1.83_windows_x86_64__mt.exe: can't resolve hostname (Message 76653) Posted 29 Nov 2023 by keputnam Post: I removed and reattached the project to get it pointed back at the correct server (losing 10 WUs in the process) Now I'm getting 2023-11-29 8:58:59 AM | Milkyway@home | Started download of milkyway_nbody_1.83_windows_x86_64__mt.exe 2023-11-29 8:59:00 AM | | Project communication failed: attempting access to reference site 2023-11-29 8:59:00 AM | Milkyway@home | Temporarily failed download of milkyway_nbody_1.83_windows_x86_64__mt.exe: can't resolve hostname The two other downloads all went smoothly

3) Message boards : Number crunching : WUs completed from "-new" URL (Message 76643) Posted 28 Nov 2023 by keputnam Post: I've got a bunch of WUs that were issued from the "-new" URL I have now reattached to the "correct" URL Is there any way to get the completed WUs accepted now? or were those wasted cycles?

4) Message boards : Number crunching : Some tasks seem never-ending. (Message 76426) Posted 13 Oct 2023 by keputnam Post: N-Body seems to be broken like this When you notice it, end BOINC and restart, and they should finish normally

5) Message boards : Number crunching : Milkyway@home N-Body Simulation v1.82 (mt) windows_x86_64 stuck (Message 76385) Posted 13 Sep 2023 by keputnam Post: No, it is not I've rebooted and the stuck WUs remain stuck

6) Message boards : Number crunching : Milkyway@home N-Body Simulation v1.82 (mt) windows_x86_64 stuck (Message 76377) Posted 12 Sep 2023 by keputnam Post: That will indeed limit Milkyway to 1 task But it will STILL use all "CPUs" This is my app_config, which also limits Milky way to three "CPUs" <app_config> <app> <name>milkyway_nbody</name> <max_concurrent>1</max_concurrent> <report_results_immediately/> <fraction_done_exact/> <gpu_versions> <gpu_usage>1</gpu_usage> <cpu_usage>.5</cpu_usage> </gpu_versions> </app> <app_version> <app_name>milkyway_nbody</app_name> <plan_class>mt</plan_class> <avg_ncpus>3</avg_ncpus> <cmdline>--nthreads 3 </cmdline> </app_version> <report_results_immediately/> </app

7) Message boards : Number crunching : Milkyway@home N-Body Simulation v1.82 (mt) windows_x86_64 stuck (Message 76374) Posted 12 Sep 2023 by keputnam Post: So I am averaging about one bad WU in 4-5 But if I don't catch it and abort it, I will tie up 3 "CPUs" forever Sorry, but this project isn't worth the hassle I'll check back periodically to see if you've fixed it

8) Message boards : Number crunching : Milkyway@home N-Body Simulation v1.82 (mt) windows_x86_64 stuck (Message 76369) Posted 3 Sep 2023 by keputnam Post: And, of course, now that I've posted here, 6 of the last 7 WUs have completed successfully

9) Message boards : Number crunching : Milkyway@home N-Body Simulation v1.82 (mt) windows_x86_64 stuck (Message 76368) Posted 2 Sep 2023 by keputnam Post: Yes, I have CPU set to 100%, but BOINC limited to 3 "processors" Two WUs have completed, most still "runaway"

10) Message boards : Number crunching : Task Remaining time Increasing (Message 76366) Posted 1 Sep 2023 by keputnam Post: Yes CPU is set to 100%, but I've limited BOINC to 3 "processors" I've had two WUs sneak through since making those settings and had three more runaways, We were out of town, and one went to 1,211,658.39 seconds wall clock time hate to say it, but I've set to "no new work" for now

11) Message boards : Number crunching : Milkyway@home N-Body Simulation v1.82 (mt) windows_x86_64 stuck (Message 76340) Posted 14 Aug 2023 by keputnam Post: I have observed similar behavior Win10 Pro, Core i-7 11700K, 8 cores hyper threaded. Milkyway limited to 3 threads to allow other projects to share the system Most, but not all, of the new CPU Nbody jobs start fine, but after a while, the time remaining starts climbing, and Resource Monitor shows the job using .01% CPU I've left several to run for quite a while, and none of them ever end. When looking at my returned tasks on the this site, you can see that processor time of the aborted tasks is nowhere near 3x wall clock time

12) Message boards : Number crunching : New Benchmark Thread - times wanted for any hardware, CPU or GPU, old or new! (Message 68135) Posted 11 Feb 2019 by keputnam Post: I’ve got an I-7 5820 over clocked to 4.1 GHz with a Radeon 7870 2 GB video card I’m averaging right at 410 sec run time with 10.5-11 sec CPU time I do have this in my APP_CONFIG file <app> <name>milkyway</name> <max_concurrent>4</max_concurrent> <cpu_usage>4</cpu_usage> <gpu_versions> <gpu_usage>0.45</gpu_usage> <cpu_usage>0.5</cpu_usage> </gpu_versions> </app> If I didn’t limit GPU time,the keyboard and mouse were almost unusable

13) Message boards : Number crunching : Can a GPU be throttled? (Message 67859) Posted 1 Nov 2018 by keputnam Post: this is part of my app_config.xml file for milkyway <app> <name>milkyway</name> <max_concurrent>4</max_concurrent> <cpu_usage>4</cpu_usage> <gpu_versions> <gpu_usage>0.45</gpu_usage> <cpu_usage>0.5</cpu_usage> </gpu_versions> </app> did this so that when two GPU apps are running, the mouse and keyboard are still usable

14) Message boards : News : New Nbody release tomorrow (Message 63565) Posted 14 May 2015 by keputnam Post: I've only had one of the new N-Body WUs complete The rest reach 100% adn the keep "running" forever, until I abort them I've also seen the behavior described in another thread. BOINC Manager shows N-Body using 12 CPUs (multi-threading), but Task Manger shows only one processor in use At the same time BOINC Manager won't let any other WUs run because all teh CPUs are:"in use" I have, as a result, stopped accepting N-Body WUs

15) Message boards : Number crunching : Milkyway@Home preventing other applications from running (Message 62507) Posted 7 Oct 2014 by keputnam Post: "It just makes sense that BOINC is going to spend a LOT of time processing Milkyway work until Milkyway "catches up". " And that has been one of my major gripes about the scheduler for quite a while I really don't care what the total credits or recent averages are When I set 33% resource share for a project, what I expect is 33% FROM THAT POINT FORWARD, until I change it (I do agree that micromanaging tends to create a lot more headaches than it fixes, tho)

16) Message boards : Number crunching : Malware Concerns over Bitcoin Utopia (Message 62150) Posted 11 Aug 2014 by keputnam Post: Both Adaware and Spybot tell me that the BitCoin Utopia download contains a Trojan,so much as I'd love to contribute, I think I'll pass

©2024 Astroinformatics Group