Posts by QuintLeo

\n studio-striking\n
1) Message boards : Number crunching : All my GPU WU finishes "computation error" after a few seconds !!! (Message 8002)
Posted 1 Jun 2018 by QuintLeo
The core issue is that Moo Wrapper continues to use the old, outdated, and flat out buggy in certain ways 520 Dnet client instead of the current 521 client.
2) Message boards : Number crunching : Moo Wrapper to DNet outage? (Message 7937)
Posted 26 Feb 2018 by QuintLeo
Issue seems to have resolved a day and some ago, the Gridcoin pool accounts are now at the top of the Dnet stats list obviously playing catchup - though I suspect their output is going to drop to near nothing pretty quick with MooWrapper having been removed as a "whitelisted" project for Gridcoin.
Workunits waiting for assimilation has also dropped though it's still got a ways to go.

If anyone can't figure out what my new email is by now, they're not bothering to look at the Dnet stats page this past week - and I find it interesting but not shocking that my output per day went UP a little after switching the rigs over to running the Dnet client directly (Moo Wrapper block sizes are a too small for optimum crunching on some of my GPUs + the wrapper itself has a small amount of "lost time" overhead vs. pulling workunits direct from my personal proxy.
Don't bother trying to email me there though, that account is a "throw-away" and I don't plan to ever look at it again.

Next step - I really need a higher capacity personal proxy, the current one only stores 200,000 blocks work of info while I routinely go through more than a million blocks per day.
3) Message boards : Number crunching : Moo Wrapper to DNet outage? (Message 7923)
Posted 16 Feb 2018 by QuintLeo
Seems like it was a good time for me to pull out of Moo and go back to working with D.Net directly.
My next project is to figure out how to dig up a proxy that will hold more than 5 or so HOURS of my normal workload - the current "personal proxy" hasn't been updated in a while and it's hard-coded 200,000 block limit is turning into a joke.
4) Message boards : Science : Time for some more recent about what we're up to? (Message 7922)
Posted 16 Feb 2018 by QuintLeo
Unfortunately, I had "forwarded" my old accounts so I'm not able to put the stats onto my current email - and their site seems to be having issues generating passwords right now.
It's not a real big deal - *I* know what my old accounts were, and it's pretty obvious anyway.
5) Message boards : Science : Time for some more recent about what we're up to? (Message 7911)
Posted 11 Feb 2018 by QuintLeo
Well, according to a majority of the vote (but not a majority of the VOTERS, as the vote was VERY WARPED due to one HUGE whale) in the Gridcoin community, Moo Wrapper and Distributed.Net RC5-72 work has "NO" scientific value - and Moo Wrapper is to be delisted from the Gridcoin "whitelist" very shortly.

Personally, I think that the so-called "standard" used should also be applied to Gridcoin-backed projects like Enigma (which is beating an EVEN OLDER dead horse by THAT standard).

As a result, there is no reason left for me to bother with the hassles of BOINC or to get irritated any more at the long-standing issue with Moo Wrapper never bothering to upgrade from the OUTDATED 520 client and the resulting issues THAT keeps causing.
I am returning to working directly with Distributed.Net and have shut down ALL of my BOINC-based operations (I think, I'll be double-checking to make sure I didn't miss one in a day or two).

The rest of you should notice that pretty much all competition from those 3 "gridcoin pools" will mostly disappear soon, though it might take time for the word to get around.

You'll be able to figure out my new identity in a couple days - just look at the top 10 on the Dnet stats I'll be back up there, probably not tomorrow but day after.
Unfortunately, my old account I can't "roll over" to the new one, as I was never able to get a password to it, so I'll have to start my chase of the "top 10 alltime" all over again.

20 years I've been working with D.Net (to the month, if not quite to the DAY today), I'm not going away anytime soon.
6) Message boards : Number crunching : Moo Wrapper to DNet outage? (Message 7908)
Posted 8 Feb 2018 by QuintLeo
I'm seeing signs that Moo Wrapper and Distributed.Net are having communications issues again - ALL of us on the high end of the Moo Wrapper list are way down on block submitted the last 2 days on D.Net stats, but other non-Moo Wrapper folks are NOT.
7) Message boards : Number crunching : Nvidia OpeCL? (Message 7907)
Posted 8 Feb 2018 by QuintLeo
If you're running the newest Nvidia cards like the 1070 ti, Linux driver version 384.98 seems to work reliably.
I have no idea what Windows driver version works well with those cards as I've never inflicted Windows on any of the ones I have.

STILL waiting on Moo Wrapper to update to the CURRENT Dnet 521 client, it's ridiculous that it's STILL insists on using the old BUGGY 520 client.
8) Questions and Answers : Wrapper and Client : HOW TO CHOSE a especific application to work on ? im receiving 2 kinds.. and onde just crash my pc... i wish to chose only one.. please help ati_14 and opencl+ati_101 (Message 7875)
Posted 9 Jan 2018 by QuintLeo
The openCL one is for GPU.
The other one I THINK is for CPU.
WHICH ONE is crashing your PC?
9) Questions and Answers : Windows : Hello Admin, can you update the app already? (Message 7874)
Posted 9 Jan 2018 by QuintLeo
I'm pretty sure that the site admin IS the project admin for this particular project.
10) Message boards : Number crunching : Legacy Dual GPUs, BOINC assigned work to both but only one with load (Message 7873)
Posted 9 Jan 2018 by QuintLeo
I believe there is an "ignore intel" option among the GPU ignore commands?
That's an option in config.xml though not app_config.xml
It's wierd that the client would ONLY work on the Intel iGPU though - it should be using both the Intel AND the AMD GPUs in the system if you have allgpus set.
11) Message boards : Number crunching : Vega (Message 7872)
Posted 9 Jan 2018 by QuintLeo
Bumping memory up for Moo Wrapper work is a waste - the entire Dnet client AND data fit into cache memory on anything remotely recent in a GPU.
12) Message boards : Number crunching : How to throttle GPU? (Message 7871)
Posted 9 Jan 2018 by QuintLeo
GPU Driver install or upgrade on windows ALWAYS requires a reboot - often 2 or 3 of them - before the new driver starts working correctly if at all.
That's been the case back AT LEAST to Windows For Workgroups 3.10 (BEFORE 95).
13) Message boards : Status info : Latest ATI/nVidia requirements (Message 7870)
Posted 9 Jan 2018 by QuintLeo
Just had a machine lose 2 days of work because you STILL have not updated the client from the BUGGY 520 version to the current 521 version more than a YEAR after 521 was released to FIX ISSUES with 520.

The FIX is just a drop-in of the 521 client for the 520 client, why has this taken so LONG to fix?
14) Message boards : Number crunching : Vega (Message 7827)
Posted 4 Dec 2017 by QuintLeo
Have you optimised it for Dnet/Moo?

What I found on my 56 was that it wanted quite a bit of undervolt, along with the usual "drop the ram speed to the minimum" and a bit of set power limit up, to get optimal keyrate while keeping temps fairly low.
15) Questions and Answers : Windows : how to get 1.04 (opencl_nvidia_101) instead of 1.03 (cuda31) (Message 7816)
Posted 25 Nov 2017 by QuintLeo
The only way I've found to get a NVidia card to use OpenCL on a reliable basis with Moo is to download a copy of the 521 OpenCL client from the Dnet clients download page, rename the .exe file to match the 520 client name in the moo wrapper "projects/" directory, then copy the renamed 521 version client to that directory overwriting the 520 client that is already there.

This will only work as long as BOINC does not get rebooted - if it DOES get rebooted, you'll have to do the copy overwrite again.

I'm not sure how much of a difference the GTX 750 ti has in performance under CUDA vs under OpenCL - the only thing I can remember the numbers on for that comparison is the GTX 1080 ti, which on my Aorus went from around 6-6.5 GKeys/sec to a hair over 10 on the same settings.
16) Message boards : Number crunching : Nvidia OpeCL? (Message 7815)
Posted 25 Nov 2017 by QuintLeo
For a machine that doesn't game, THE driver version that combines best performance AND best reliability is 373.06 - this comes out of extensive testing of driver versions by the FAH community, but should be applicable here as well.
Unfortunately, if you use a GTX 1080 ti or more recent (like the newest Titan or the 1070 ti) you HAVE to use something more recent - I'd go with the 384.98 (November 2 update) version for LINUX, not sure on the WIndows side as my few remaining WIndows/NVida machines are all running older cards on 373.06

Newer on NVidia drivers are often NOT BETTER for compute usage, and a lot of the versions since 373.06 have been actively BROKEN for compute.

The GTX 1070 is an 8GB card - there is no option for anything else on ANY version of it.
Doesn't really matter though, as the underlying Dnet client only uses perhaps *A* megabyte if that much including data usage.

The only way I've found to date to RELIABLY get a GTX 10xx series card to use OpenCL under Moo is to do the "copy the 521 client in place of the 520 client that Moo uses" trick, which only works 'till BOINC gets rebooted - it's one of the reasons I only run AMD cards on MOO, it's not worth the hassle to get my NVidia farm (almost all 1070/1080/1080i/1070ti cards, though I do have a FEW 950/960 left-overs) to work with Moo as long as Moo continues to use a client that is outdated and where the CURRENT client fixes quite a few issues.
17) Message boards : Number crunching : Problems running wus on AMD R9 380. Suddenly Moo crashes card. (Message 7814)
Posted 25 Nov 2017 by QuintLeo
Oddly enough, I HAVE to undervolt on my Vega RX 56 to get the best keyrates - and lower temps.

Seems like the "default" GPU voltage on those things is set WAY high.

Not sure how long I'm going to leave the thing "lent" to my cryptocoin mining effort, as the only thing it's worth mining with is Monero and you HAVE to run Win10 and the blockchain driver to get decent hashrate out of it on that (the LINUX version of that driver flat out doesn't WORK with Vega, in fact AMD has had the FE out for MONTHS and it STILL doesn't work under LINUX due to their borked drivers situation on the LINUX side).

On the RC5-72/Dnet/Moo/BOINC side, it's about a 7.5ish GKey/sec card stock and can easily be tweeked to hit 9 reliably - that's a bit more than a PAIR of RX series cards or my old-but-reliable R9 cards, while the power consumption is a little less than a pair of my RX 470 cards.
It also works with 520 under OpenCL as MooWrapper provides, no need to "kludge" it like for a GTX 1080 ti to get it's good hashrate.
18) Message boards : Number crunching : Legacy Dual GPUs, BOINC assigned work to both but only one with load (Message 7790)
Posted 9 Nov 2017 by QuintLeo
What is the "max concurrent" line for?
I've never had that in any of my multi-GPU systems.
19) Questions and Answers : Windows : 2nd GPU issue (Message 7786)
Posted 8 Nov 2017 by QuintLeo
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.
20) Questions and Answers : Windows : Hello Admin, can you update the app already? (Message 7773)
Posted 3 Nov 2017 by QuintLeo
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?

Next 20

Copyright © 2011-2024 Moo! Wrapper Project