Welcome to MilkyWay@home

Posts by swiftmallard

1) Message boards : Number crunching : Long crunch time on new N-Body simulations? (Message 69162)
Posted 6 Oct 2019 by swiftmallard
Post:
That's fair, but when my settings are a minimum of 2 days, 5 days additional, how is it I can't complete tasks within a 2 week deadline? The computer runs 24/7 crunching, 100% of the CPU time and all cores. I am not restricting boinc from attempting to complete tasks at all.

Very few people can crunch both n-body and separation WUs on the same computer. The change from single thread to multi thread n-body work is only going to make it even more difficult to deal with the scheduler.
2) Message boards : Number crunching : How many CPUs? (Message 69132)
Posted 27 Sep 2019 by swiftmallard
Post:
I noticed the same thing on my six core machine when they switched to multi-threaded WUs. Simply set MW to No New Tasks, then suspend all the multi-threaded units and the old ones will clear out. While you are on NNT, reduce your cache to only a few hours worth of work or you will have scheduling problems when you start back up.
3) Message boards : Number crunching : Difference between 2 work units? (Message 69013)
Posted 9 Sep 2019 by swiftmallard
Post:
Yes, easily. Different runs of work units will have will have varying run times. They will be roughly consistent, as yours are. A quick look through your validated WUs will show this.
4) Message boards : Number crunching : Completed, validation inconclusive (Message 69002)
Posted 1 Sep 2019 by swiftmallard
Post:
It means awaiting confirmation by another cruncher.
5) Message boards : Cafe MilkyWay : Badges (Message 69000)
Posted 31 Aug 2019 by swiftmallard
Post:
Try here: https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3423&postid=60567#60567
6) Message boards : Number crunching : MilkyWay takes a backseat to Einstein ??? (Message 68964)
Posted 11 Aug 2019 by swiftmallard
Post:
I like to run MilkyWay with Einstein WUs on the same GPU, a perfect pairing. However, Einstein will continue to request work but MilkyWay stops requesting work and runs out. To get more MilkyWay WUs I have to Suspend Einstein to stock up on MilkyWay.
Is it possible to make MilkyWay as aggressive as Einstein???

Are both projects set to the same Resource Share?
7) Questions and Answers : Windows : Number crunching halted on GPU units (Message 68959)
Posted 8 Aug 2019 by swiftmallard
Post:
Unhide your computers on the MW preferences page.
Open the Boinc manager and click on the tools tab, then open the event log.
Hold down the Ctrl key while you highlight the appropriate lines, i.e. all the lines that pertain to any given stopped WU.
Then click on "copy selected".
You can then paste those lines into this thread.
8) Message boards : Number crunching : Benchmark thread 1-2019 on - GPU & CPU times wanted for new WUs, old & new hardware! (Message 68956)
Posted 6 Aug 2019 by swiftmallard
Post:


Have made some improvements to that aspx app

https://stateson.net/HostProjectStats

A much more accurate program (but not web based) is available and described here

https://forum.efmer.com/index.php?topic=1355.0

Both program sources are at github. Feel free to PM me any suggestions or you could also post over at the boinctasks forum.

Wow! That's pretty slick! I would have loved to have this sort of analysis available when I was GPU crunching
9) Message boards : Number crunching : Benchmark thread 1-2019 on - GPU & CPU times wanted for new WUs, old & new hardware! (Message 68954)
Posted 5 Aug 2019 by swiftmallard
Post:
N body work units, ver 1.76
Intel Core i5 @ 3.79GHz no hyperthreading, no overclocking
last ten valid work units 2018 sec avg, 30.7 credits avg
10) Message boards : Number crunching : Long crunch time on new N-Body simulations? (Message 68945)
Posted 2 Aug 2019 by swiftmallard
Post:
So, I think something is going on here. I currently have four N-Body 1.76 tasks running that so far have elapsed 2 or 3 DAYS, with most of those having 10+ hours to remain. These tasks were downloaded over a week ago (6 June 2019, 9 June 2019), and I am pretty sure I would have noticed estimated times of that long. Marmot, I did try adjusting the half life as you suggested and it had not picked up this discrepancy in ETA. This morning I have adjusted my half life setting down to 1.

I feel that this is a problem that shouldn't be happening. The CPU, despite being a laptop, is from 2017 so it isn't a slow processor. It has a higher GFLOPS/core than an i7-8700. Is there any kind of debugging I can do to evaluate this?

My aging dual core AMD Phenom II is processing N-Body 1.76 tasks in just a few hours, all have been pretty close to the estimated time.
11) Message boards : Number crunching : Don't understand errors or how to clear them (Message 64302)
Posted 6 Feb 2016 by swiftmallard
Post:
Were you running successfully on Windows 10 before? Or is that part new too?
12) Message boards : Application Code Discussion : Why I've ceased participating in MilkyWay@Home via BOINC (Message 64246)
Posted 15 Jan 2016 by swiftmallard
Post:
...I do have 2 projects on each pc, one for the gpu and one for the cpu, that way the caches don't conflict and cause problems.

Precisely!
13) Message boards : Application Code Discussion : Why I've ceased participating in MilkyWay@Home via BOINC (Message 64243)
Posted 14 Jan 2016 by swiftmallard
Post:
An easy way around this problem is to simply run one project at a time. Let one run for a month, them do something else. Over time it all evens out.
14) Message boards : Number crunching : Problems with latest Windows 10 update (Message 64227)
Posted 6 Jan 2016 by swiftmallard
Post:
Enough nonsense. Back to Win 7
15) Message boards : Number crunching : Problems with latest Windows 10 update (Message 64218)
Posted 2 Jan 2016 by swiftmallard
Post:
Here is my Boinc start-up info:

1/2/2016 1:57:04 PM | | Starting BOINC client version 7.6.22 for windows_x86_64
1/2/2016 1:57:04 PM | | log flags: file_xfer, sched_ops, task
1/2/2016 1:57:04 PM | | Libraries: libcurl/7.45.0 OpenSSL/1.0.2d zlib/1.2.8
1/2/2016 1:57:04 PM | | Data directory: C:\ProgramData\BOINC
1/2/2016 1:57:08 PM | | CAL: ATI GPU 0: ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (CAL version 1.4.1848, 1024MB, 991MB available, 5440 GFLOPS peak)
1/2/2016 1:57:08 PM | | OpenCL: AMD/ATI GPU 0: ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (driver version 1800.8 (VM), device version OpenCL 1.2 AMD-APP (1800.8), 1024MB, 991MB available, 5440 GFLOPS peak)
1/2/2016 1:57:08 PM | | OpenCL CPU: AMD Phenom(tm) II X3 720 Processor (OpenCL driver vendor: Advanced Micro Devices, Inc., driver version 1800.8 (sse2), device version OpenCL 1.2 AMD-APP (1800.8))
1/2/2016 1:57:08 PM | | Host name: Phenom
1/2/2016 1:57:08 PM | | Processor: 3 AuthenticAMD AMD Phenom(tm) II X3 720 Processor [Family 16 Model 4 Stepping 2]
1/2/2016 1:57:08 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni cx16 popcnt syscall nx lm svm sse4a osvw ibs skinit wdt page1gb rdtscp 3dnowext 3dnow
1/2/2016 1:57:08 PM | | OS: Microsoft Windows 10: Core x64 Edition, (10.00.10586.00)
1/2/2016 1:57:08 PM | | Memory: 4.00 GB physical, 8.00 GB virtual
1/2/2016 1:57:08 PM | | Disk: 465.22 GB total, 390.19 GB free
1/2/2016 1:57:08 PM | | Local time is UTC -6 hours
16) Message boards : Number crunching : Problems with latest Windows 10 update (Message 64216)
Posted 2 Jan 2016 by swiftmallard
Post:
Thanks for your help. Where you suggest is where I got the info I quoted.

Instead of resetting the project, I did a complete detach/reattach. No change.
17) Message boards : Number crunching : Problems with latest Windows 10 update (Message 64214)
Posted 2 Jan 2016 by swiftmallard
Post:
Thank you. I installed the AMD SDK but there is no change.
Not sure exactly what you mean by the WU log file but my computer is not hidden and one can see the invalid WUs in my tasks. The portion of the stderr output that catches my eye is:
Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00007FF9137DD8A0 read attempt to address 0x00000010

but I do not know what this means.
18) Message boards : Number crunching : Problems with latest Windows 10 update (Message 64212)
Posted 2 Jan 2016 by swiftmallard
Post:
Here is where I am with my current set-up:
HD5870
Catalyst 15.7.1
MS C++ Runtime package installed
Win 10

All WU complete is less than 10 seconds and error out.
I'm running out of ideas how to get going again.
19) Message boards : Number crunching : Problems with latest Windows 10 update (Message 64211)
Posted 2 Jan 2016 by swiftmallard
Post:
Alas, it did not work. I installed the x86 version and it made no difference at all. Do I need to do anything other than what it will by default?
20) Message boards : Number crunching : Problems with latest Windows 10 update (Message 64209)
Posted 2 Jan 2016 by swiftmallard
Post:
Some BOINC projects now require you to download and install the latest runtime package for C++ in order to run under Windows 10; this does NOT happen automatically.

I've lost the information on where to find this package, though.

I have never done this, can anyone point in the right direction?


Next 20

©2019 Astroinformatics Group