Posts by QuintLeo

1) Message boards : Number crunching : Legacy Dual GPUs, BOINC assigned work to both but only one with load (Message 7790)
Posted 13 days ago by QuintLeo
Post:
What is the "max concurrent" line for?
I've never had that in any of my multi-GPU systems.
2) Questions and Answers : Windows : 2nd GPU issue (Message 7786)
Posted 14 days ago by QuintLeo
Post:
Even when running the actual DNet client, 2 GPUs won't "share work" - they are always working on different keyblocks.
What you *should* be seeing is each GPU working on a seperate workunit, and taking about the same time that they did before.
3) Questions and Answers : Windows : Hello Admin, can you update the app already? (Message 7773)
Posted 19 days ago by QuintLeo
Post:
The NVidia issue is that the Native CUDA cores are a LOT slower then the newer OpenCL cores - but the clients prior to 521 don't SUPPORT OpenCL usage on NVidia.

1080ti for example it's a difference from about 5-6 GKeys/sec to around 10 GKeys/sec - not as bad as your 970 but still a LOT.

It seems like 521 cleaned up some of the interaction with OpenCL driver code so it just WORKS in a lot of cases were the 520 client (or older) don't.

Since the client is literally a drop-in replacement, I don't understand why this small change wasn't made MANY MANY MOONS AGO - shouldn't take much of a change to tell whatever overrwites the client to use the newer client instead?
4) Questions and Answers : Windows : AMD R9 380 - Computation Errors - Distributed.net1.04 (opencl_ati_101) on dnetc_r72_1499529280_13_823_0 (Message 7772)
Posted 19 days ago by QuintLeo
Post:
One other possible option - grab the 521 OpenCL client from the Distributed.net downloads, rename the exe to match the 520 .exe client in data/projects/Moowrapper.net, then copy the renamed 521 client over the existing 520 client.

I had one machine that just wouldn't run on the 520 client but ran fine on the 521 for some wierd reason I never did figure out.
5) Message boards : Number crunching : Vega (Message 7771)
Posted 19 days ago by QuintLeo
Post:
Got my Vega 56 in today (Sapphire reference model).

It's WIERD - to get it to get anywhere near the officially specified "1590" core clock, you have to kick the power limit WAY up (+30% at least in Afterburner) AND you have to UNDERVOLT it quite a bit (-100mv ballpark) - and even THEN it won't get to 1590, though I did see mid-1500s after a bunch of settings work.

In stock form, it's not quite a 8 Gigakey/sec card (for perspective, the GTX 1080 ti can hit a little over 10 GKeys/sec with some overclocking).
Maxed out, I saw about 9.5 GKeys/sec though - which is not bad at all for a $460 card compared to the 1080 ti at $700+, and quite a bit more than the GTX 1080 manages in the same price ballpark.

Card also runs AMAZINGLY cool unless you push it very hard - never much past 55C at stock settings with less than 55% fan, and the settings I found to make it a 9GKey/s card was only pushing it to about 62-63C at under 68% fan (I run a straight-line "fan curve" in Afterburner by default that is "all in" at 80C and drops 20% every 10C below that).

I estimate that a stock 56 will exceed 1 million RAC by a bit, a pushed one should get into the 1.3-1.4 million RAC ballpark - in other words, a SINGLE CARD can exceed all but about the top 3 or 4 machines currently working Moo Wrapper.

Given wide reports that the air-cooled Vega 64 clocks higher reliably than the 56, and that it has 64 CU instead of 56 (1/7'th more cores), I am ready to state that the Vea 64 SHOULD be the current Dnet/Moo Wrapper single card performance king - especially if someone wanted to put out the kind of money to get the WATER COOLED version, which supposedly clocks a LOT higher than the air-cooled version.
6) Message boards : Status info : Latest ATI/nVidia requirements (Message 7757)
Posted 26 days ago by QuintLeo
Post:
The distributed.net client ITSELF does not support NVidia well if at all in versions prior to 521.
Yet another reason MooWrapper NEEDS to get updated to 521 asap - it fixed a TON of issues vs the version 520 client MooWrapper is currently using, and offers a LOT better performance on NVidia cards.
7) Questions and Answers : Windows : AMD R9 380 - Computation Errors - Distributed.net1.04 (opencl_ati_101) on dnetc_r72_1499529280_13_823_0 (Message 7756)
Posted 26 days ago by QuintLeo
Post:
Try backing out to the 16.9.2 or the 15.12 drivers - the Relive junk has a LOT of issues where it works at all, and a LOT of the newer driver versions flat out don't WORK with R9 series hardware.
8) Questions and Answers : Windows : Hello Admin, can you update the app already? (Message 7755)
Posted 26 days ago by QuintLeo
Post:
download the Distributed.net 521 client from https://www.distributed.net/Download_clients
Unzip the downloaded file
rename the dnetc.exe file to match the long file name dnetcxxxxx.exe file in the boinc projects/moowrapper.net directory, then copy it in place of the existing file.

Since moowrapper WILL overwrite the file on occasion, keep the renamed copy of the 521 client file around for later recopy.
9) Message boards : Number crunching : Nvidia OpeCL? (Message 7739)
Posted 6 Oct 2017 by QuintLeo
Post:
I'm not sure if OpenCL on NVidia is properly supported by the dnet 520 version of the client Moo Wrapper uses - it's one of the reasons I've been strongly in favor of Moo Wrapper upgrading to use of the CURRENT 521 dnet client, which definitely DOES work correctly with NVidia.

You may also have an issue with the driver version you have not having initiated OpenCL support correctly - there were a couple of NVidia driver versions that had that issue, backing out to around 378 seems to help (and if you're not GAMING on the same machine they run more reliably as well).
10) Message boards : Number crunching : How to throttle GPU? (Message 7738)
Posted 6 Oct 2017 by QuintLeo
Post:
It's just the way mixed GPUs and their drivers interact - or the Collaz application was soaking a lot of CPU cycles as well (like FAH does).
11) Message boards : Number crunching : Cannot upload (Message 7737)
Posted 6 Oct 2017 by QuintLeo
Post:
It was just you, though there DOES seem to be a Moo <-> Dnet issue happening in the last 24 hours.
12) Message boards : Number crunching : Problems running wus on AMD R9 380. Suddenly Moo crashes card. (Message 7736)
Posted 6 Oct 2017 by QuintLeo
Post:
Try the 15.12 drivers (15.300.something under LINUX as I recall) - the version you are using is the 15.7 which wasn't quite as stable on your generation of card.

Same advice if you're running Windows - the only later Windows drivers that were worth spit on older R9 series cards were in the 16.9 to 16.10 range, and those have NOTHING to offer an older card unless you also game on the machine, while being noticeably more bloated for similar performance.

You may also be overclocking the core a bit too much, the Dnet.c client is notorious for how hard it pushes the core of a GPU (while being VERY VERY light on memory usage).


WAY back in the day, it was often debated if the Dnet.c client or the Prime95 (GIMPS) client was a better stress test.
13) Questions and Answers : Web site : Stats page no longer shows names (Message 7723)
Posted 15 Sep 2017 by QuintLeo
Post:
Why did the "Your Computers" page stop showing the NAME of the computer?

This makes it a royal PAIN trying to figure out which machine has gone down, especially since Moo Wrapper (and BOINC in general) never seems to identify the GPUs in a machine correctly to the various stats pages.
14) Questions and Answers : Windows : AMD R9 380 - Computation Errors - Distributed.net1.04 (opencl_ati_101) on dnetc_r72_1499529280_13_823_0 (Message 7692)
Posted 10 Jul 2017 by QuintLeo
Post:
If you are on Windows 10, you probably got auto-updated to a driver version that doesn't work well on older hardware.

I can't tell for sure as that reported "driver version" doesn't match up to ANYTHING I've ever seen before.
15) Questions and Answers : Windows : X64 version for CPU computing (Message 7691)
Posted 10 Jul 2017 by QuintLeo
Post:
Unless you are doing CPU computing, there is ZERO advantage to a 64-bit version as your GPU(s) are doing all the work.

There is NO "gpu-based" DNet client that is 64 bit for that reason, all of the 64-bit clients are CPU-specific (and very SLOW even on current CPUs compared to very old GPUs).
16) Message boards : News : Disk failure on the main project server (Message 7690)
Posted 10 Jul 2017 by QuintLeo
Post:
Well, whatever the issue was, it's either fixed or was short-term.
17) Message boards : News : Disk failure on the main project server (Message 7689)
Posted 9 Jul 2017 by QuintLeo
Post:
Hopefully it's a different issue, but it appears that Moowrap stopped talking to the Distributed.net keyservers to report block ENTIRELY sometime early on July 8.
18) Questions and Answers : Getting started : Fake DB entries (Message 7684)
Posted 26 Jun 2017 by QuintLeo
Post:
I wonder what you mean by "fake groups on the db"?
19) Questions and Answers : Windows : Output file dnetc_r72_1498297335_3_192_0_0 for task dnetc_r72_1498297335_3_192_0 absent (Message 7683)
Posted 26 Jun 2017 by QuintLeo
Post:
Check your free disk space
20) Message boards : Number crunching : Multiple GPUs on same WU (Message 7681)
Posted 20 Jun 2017 by QuintLeo
Post:
It wouldn't be practical on Moo Wrapper to run one work unit on multiple GPUs even if BOINC specifically supported it, as Moo is nothing more than a "wrapper" for the Distributed.net client that client does not support running one "block" on more than one GPU at a time.

It's possible to have AMD and NVida GPUs mixed on a Linux machine - but an AMD GPU MUST be the one used for video output, you MUST install the AMD drivers first, THEN install the NVidia drivers from the .run package MANUALLY using the "--no-opengl-files" command line switch - otherwise the NVidia opengl stuff overwrites the AMD opengl stuff and completely borks the AMD drivers to the point the AMD GPUs flat out won't work at all.

In theory you can hand-install the applicable files but that's a royal pain at best and will leave you with an unusable system if you miss even ONE of them, or use ONE wrong file.

Mixed GPUs is one of the very few things Windows does better than Linux, and IMO one of only 2 things it does a LOT better (the other being "support games").


Next 20


 
Copyright © 2011-2017 Moo! Wrapper Project