Welcome to MilkyWay@home

Posts by Cautilus

1) Message boards : Number crunching : Finally getting new tasks only seconds after running out. May not be worth the hassle. (Message 69561)
Posted 14 hours ago by Cautilus
Post:
Hi I see you guys mentioning editing "coproc" or something like that to download 900 WUs at a time instead of 150 - 300? I was wondering how you go about doing that, because I've been searching around for a bit and I can't find any instructions.

Also how do you install the ubuntu version? I'm a complete novice with Linux and you mention you need to "use 0751 on program and 0664 on the xml" but I have no idea what that means.
2) Message boards : Number crunching : multithread (Message 68944)
Posted 2 Aug 2019 by Cautilus
Post:
You can just run multiple single-threaded WUs concurrently to use more threads, which BOINC should be doing automatically unless you've changed your CPU utilisation parameters.
3) Message boards : News : New Separation Runs [UPDATE] (Message 68934)
Posted 28 Jul 2019 by Cautilus
Post:
Vester those aren't "bgset_2" work units. Those are the bugged "bgset" work units.

"bgset_2" work units have the "_2" right next to the "bgset", like this:

de_modfit_84_bundle4_4s_south4s_bgset_2_1564052102_378831_1
4) Message boards : News : New Separation Runs [UPDATE] (Message 68913)
Posted 25 Jul 2019 by Cautilus
Post:
Is this from a "...bgset" run, or a "...bgset_2" run? The new "...bgset_2" runs ran fine on my client. This looks identical to the last error for the previous bugged runs. Thank you for the input, though!

Tom


Oh right yes my mistake, that was from a bgset run, not a bgset_2 run. Looks like bgset_2 is running all good on my end.
5) Message boards : News : New Separation Runs [UPDATE] (Message 68910)
Posted 25 Jul 2019 by Cautilus
Post:
This is what I got:
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
Incorrect function.
(0x1) - exit code 1 (0x1)</message>
<stderr_txt>
<search_application> milkyway_separation 1.46 Windows x86 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Switching to Parameter File 'astronomy_parameters.txt'
<number_WUs> 4 </number_WUs>
<number_params_per_WU> 25 </number_params_per_WU>
Number of streams does not match
06:50:25 (6780): called boinc_finish(1)

</stderr_txt>
]]>
6) Message boards : Application Code Discussion : GPU RAM Requirements (Message 67322)
Posted 11 Apr 2018 by Cautilus
Post:
Yeah it seems like the work units use up to 1.5GB of VRAM on NVIDIA cards for whatever reason. On AMD cards they only use like 100MB per work unit, I'm not sure why NVIDIA work units use so much more VRAM. But I would also like to know if there's a way to reduce the VRAM usage for NVIDIA cards.
7) Message boards : Number crunching : Can't get work for NVIDIA GPU (Message 67275)
Posted 25 Mar 2018 by Cautilus
Post:
I will mention that the developers are reducing work units to GPUs without very high double precision capability. Pretty much all of the NVIDIA GPUs mentioned in this thread have *very low* FP64 (double precision) capability, which would explain why you haven't been getting many work units. You should allocate your GPUs elsewhere.
8) Message boards : Number crunching : How to reduce VRAM usage for NVIDIA GPU tasks? (Message 67101)
Posted 18 Feb 2018 by Cautilus
Post:
Well maybe that's how it's set out in NVIDIA's guidelines, but Milkyway still allocates up to 12GB of VRAM. Here's a graph from HWiNFO64 that shows my VRAM usage with 8 WUs running simultaneously, clearly showing it's above the 3GB threshold (Y-axis is from 0 to 12500MB of VRAM allocation).

https://i.imgur.com/665amcH.png
9) Message boards : Number crunching : MW@H DBase problems (Message 67092)
Posted 16 Feb 2018 by Cautilus
Post:
Great to hear a permanent solution is on the way, thanks Jake!
10) Message boards : Number crunching : How to reduce VRAM usage for NVIDIA GPU tasks? (Message 67086)
Posted 15 Feb 2018 by Cautilus
Post:
Yeah look trust me, I'd need probably 16 WUs simultaneously to saturate the TITAN V's FP64. I know on 280X's the VRAM usage is significantly lower, for some reason on the TITAN, each WU uses about 1.5GB of VRAM. I'm not sure if this is because of the new architecture or if it's just an NVIDIA thing. The WUs process in about 55 - 65 seconds even with 10 WUs running simultaneously, and that's still peaking at only 70 - 75% usage, indicating there's still headroom left.
11) Message boards : Number crunching : How to reduce VRAM usage for NVIDIA GPU tasks? (Message 67084)
Posted 15 Feb 2018 by Cautilus
Post:
So I have a TITAN V that I want to use on this project while it's not doing anything important. The problem is I can't max out its usage by running more WUs simultaneously because I max out the VRAM on the TITAN and all of the work units end in 'computation error'. I can run about 8 or so WUs simultaneously if I micromanage them so they don't hit 12GB VRAM usage, but surely there's a way to set the WUs to use less VRAM somehow right?
12) Message boards : Number crunching : Is anybody going to buy a TITAN V? (Message 66920)
Posted 2 Jan 2018 by Cautilus
Post:
Just gunna bump this because it'd actually be ridiculous the amount of RAC you'd get on a Titan V boosting up to ~1800 MHz if someone was willing to try it. Probably get something like 3 - 4 million RAC off a single card.
13) Message boards : Number crunching : I have pages of completed work units but (Message 66888)
Posted 27 Dec 2017 by Cautilus
Post:
Yeah I've got a 50/50 ratio of validation inconclusive and valid aswell on my machines, and my RAC is dropping. Probably something's gone wrong on their end.
14) Message boards : Number crunching : Errors (Message 66620)
Posted 16 Sep 2017 by Cautilus
Post:
I'm getting errors on these work units as well:

"de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy"

"de_modfit_fast_20_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy"

Running a 290X and 280X, both of them seem to get errors only with these units, no others.




©2020 Astroinformatics Group