[JCE]Fast & stable CN/v8/Heavy/Tube/XHV miner, CPU+GPU, Vega56 1800+ RX580 1200+

[grendel25]

question:  I'm using 2x opteron 6376 and get around 475 h/s using 16 of 32 available cores which seems to consume about 57% of CPU resources.  Could i tune this up to get better performance and also use the other 16 cores?  Thank you for any comments or suggestions.

What coin/algo?

The Opteron 6376 is basically two AMD FX Piledriver dies on one package. An FX 8300 hashes around 1000 H/s Cryptonight-Lite or 340 H/s with CN v7.

Your system with two Opteron 6376 (say four FX dies), but lower frequency, should be around FX-8300-hashrate * 4 * 2.3 / 3.3. So CN v7 hashrate should be VAGUELY 900 H/s for the whole system with optimized settings But that depends on what coin/algo you want to mine

Coin/Algo:  Alloy  /  cryptonight-alloy 

How would I determine optimized settings?  I guess I should see what I get on CN v7 to see if it's close to that 900 number.  any suggestions of coins to try?  Sumo?

I didn't know that about AMD FX Piledriver dies.  Your response is very informative.  Thank you for that.

[heavyarms1912]

does the gpu miner compile fresh kernel every run?  It seems to be lot slower with multi GPU rigs.
EDIT:  Just read the posts above.

[Bry Guy]

does the gpu miner compile fresh kernel every run?  It seems to be lot slower with multi GPU rigs.
EDIT:  Just read the posts above.

Yes, every run is freshly compiled and tied to that individual card for security purposes. JCE is aware that those of us with bigger multi-card rigs would love to see the total time spent at startup reduced and has commented that he will continue to look for ways to improve upon this startup time without compromising security.
EDIT:  Just saw your EDIT after I posted!   

[JCE-Miner]

Version 0.31a CPU Windows online

Code:

Backported GPU netcode
Bittube-v4 (with better perf than any other cpu miner)
Now max is 256 cpu/gpu threads
new coin PrivatePay
case insensitive commands (pressing h or H for hashrate will both work now)
Sumokoin back to CN-classic

[UnclWish]

Even with --no-gpu option gpu miner doing something with OpenCL GPU at start. If GPU's mines on other miner and run your miner with --no-gpu option, it short freeze - even mouse hangs - and than all works fine. On other miner speed on GPU's drops on this moment.
On first GPU prototyps --no-gpu option disables that. On latest - no.

[Bazzaar]

I know my heavy is bad, i need to optimize it. I even tell it explicitely in my doc.

Have you seen the Heavy algo draft optimisations on Github?

Baz

ps. 6000 h/s with 4x vegas on Bittube   

[Lonnegan64]

Coin/Algo:  Alloy  /  cryptonight-alloy  

How would I determine optimized settings?  I guess I should see what I get on CN v7 to see if it's close to that 900 number.  any suggestions of coins to try?  Sumo?

Oh. Alloy is a harder variant of CN Heavy. You shouldn't mine CN-Heavy or CN-Alloy with CPUs, since their drop of hashrate in comparison to CN ist enormous, whereas GPUs aren't affected in the same way. CN-Heavy and CN-Alloy are tailormade for GPUs.   Consider to mine a CN-Lite coin with your CPUs. You may reach around 2700 H/s with CN-Lite (Aeon, Turtlecoin) or about 1300 H/s with CN-Fast (Masari).   If you want to mine CNv7, why not Monero? Sumo is back to ASIC friendly original CN. It's absurd to mine an ASIC coin with CPUs.  

I didn't know that about AMD FX Piledriver dies.  Your response is very informative.  Thank you for that.

No problem

[grendel25]

Coin/Algo:  Alloy  /  cryptonight-alloy  

How would I determine optimized settings?  I guess I should see what I get on CN v7 to see if it's close to that 900 number.  any suggestions of coins to try?  Sumo?

Oh. Alloy is a harder variant of CN Heavy. You shouldn't mine CN-Heavy or CN-Alloy with CPUs, since their drop of hashrate in comparison to CN ist enormous, whereas GPUs aren't affected in the same way. CN-Heavy and CN-Alloy are tailormade for GPUs.   Consider to mine a CN-Lite coin with your CPUs. You may reach around 2700 H/s with CN-Lite (Aeon, Turtlecoin) or about 1300 H/s with CN-Fast (Masari).   If you want to mine CNv7, why not Monero? Sumo is back to ASIC friendly original CN. It's absurd to mine an ASIC coin with CPUs.  

I didn't know that about AMD FX Piledriver dies.  Your response is very informative.  Thank you for that.

No problem

ahhh, that's why I see all the negative comments on Sumo coin.  So much has changed with the cryptonight algorithm since the days when I mined with a few lowly AMD cards.  It is really interesting about all the variants.

Good to know about alloy coin.  It makes me want to throw some GPUs at it for a bit. 

Thanks for the CN-Lite and CN-Fast comments... just to be clear, for CPU mining, I want to look for CN-Lite --and-- CN-Fast algorithms?

[wgestickley]

Hi Guys,

Are there some estimated Hashrates for CN_Heavy?

I am interested in:
RX570, 4 GB
RX580, 8 GB

I am actuallly uses SRB Miner

Thank you

[Lonnegan64]

just to be clear, for CPU mining, I want to look for CN-Lite --and-- CN-Fast algorithms?

I'd go for CN-Lite, AeonCoin for example. There the CPUs' advantage over GPUs is max. With a scratchpad size of 1 MB per thread you can start 32 threads on your 2 socket system and the data still fits into the L2 cache of your Opterons 6376. When you activate double-hash, you can still run 32 threads, filling the L2 and L3 victim cache for the last extra percent of performance. "Bulldozer was without doubt an unmitigated failure" (Andrew Feldman, Corporate Vice President and General Manager of the Server Business Unit, AMD), but at mining CN, it is a beast!      

[Lonnegan64]

FYI: Electroneum is back to ASIC-friedly CN original, too! 
https://www.facebook.com/electroneum/posts/2030562537205714

[UnclWish]

Hi Guys,

Are there some estimated Hashrates for CN_Heavy?

I am interested in:
RX570, 4 GB
RX580, 8 GB

I am actuallly uses SRB Miner

Thank you

Heavy is not good optimized yet. But on 570/4 speed will be about 750-800, 580/8 - about 1000 h/s.

[Lonnegan64]

Heavy is not good optimized yet. But on 570/4 speed will be about 750-800, 580/8 - about 1000 h/s.

You should add "with mod bios and optimized clock/power/ram settings". @Stock the performance is significantly lower!  

[Bry Guy]

Hi JCE,

When using your GPU miner, can you advise as to whether or not you are currently verifying the GPU result by cross checking with CPU that is is valid before submitting to the pool? Some other miners perform this check and will avoid submitting if there is a discrepancy, merely noting it as a 'Compute Error'. If you aren't, would you consider adding the functionality, even if only via a config or switch? If it slows down performance, it can still be beneficial when testing more aggressive clocks and multi_hash/intensity settings to have this check before submitting when trying to find the performance vs stability sweet spot and not wanting to get banned by the pool for invalid shares.

I received this error in JCE while testing the reasonable limit of each GPU so it got me wondering about this. My static difficulty is definitely appropriate as it's not even 25x my hashrate. I am sure that lowering my clocks will reduce or eliminate this issue, but I thought I'd include this result for informational purposes.

Code:

21:40:57 | Rejected by the pool.
21:40:57 | Message from the pool: Low difficulty share
21:41:45 | GPU 7 Thread 14 Lane 1526 finds a Share, value 400015
21:41:45 | Rejected by the pool.
21:41:45 | Connection failed: The pool kicked you out as Unauthenticated, its Difficulty 400015 is probably too high for your computing power. If the pool allows fixed Difficulty, fix it to a lower value.
21:41:45 | Connection interrupted, waiting 5s then retry, attempt #1
21:41:45 | Connection failed: Socket receive error: A blocking operation was interrupted by a call to WSACancelBlockingCall.
21:41:45 | Connection interrupted, waiting 5s then retry, attempt #2

Thank you for considering this. As things stand now only having the ability to specify one pool, it can result in complete downtime if invalid shares are submitted that are outside the proper difficulty level and the pool issues a ban.

[JCE-Miner]

Good idea, i'll add parameter --doublecheck to make CPU re-check the share, like Claymore 10.

i ordered a A8 APU on socket FM2 to make JCE compatible with APUs

[whotheff]

Good idea, i'll add parameter --doublecheck to make CPU re-check the share, like Claymore 10.

i ordered a A8 APU on socket FM2 to make JCE compatible with APUs

Thanks! You're the most hard working dev around here

[JCE-Miner]

I'm the most late, a lot of simple features are missing like temperature monitoring or autoconfig.

Have you seen the Heavy algo draft optimisations on Github?

if you're talking about this
https://github.com/imperdin/xmr-stak


well, first it applies only to xmrstak, i use my own code, based on jce cpu 32 Bits
and... it's mostly a bunch of changes that fix some goofs of the Wolf0 code, add some new ones, leave most of them in place. Nothing interresting. and since jce is close source, it would be illegal to take his code.

[Bazzaar]

I'm the most late, a lot of simple features are missing like temperature monitoring or autoconfig.

Have you seen the Heavy algo draft optimisations on Github?

if you're talking about this
https://github.com/imperdin/xmr-stak


well, first it applies only to xmrstak, i use my own code, based on jce cpu 32 Bits
and... it's mostly a bunch of changes that fix some goofs of the Wolf0 code, add some new ones, leave most of them in place. Nothing interresting. and since jce is close source, it would be illegal to take his code.

Ok, just wondered if it gave any clues where and how to get heavy more efficient.
Interesting that Doc made some improvements to SRB based on it, just saying.

[JCE-Miner]

really?
i read he said he already had a better code. i really see no good ideas in the changes, just some trivial fixes.
alas, my code is different and yes i've some ideas to improve it

[Beruang123]

Hi,

I have 2 mining rigs :
1st rig  = 4 RX 580 8 GB (MSI) and 2 RX Vega 56 (Power Color Red Devil)
2nd rig = 5 RX Vega 56 (Power Color Red Devil)

Both installed win 10 1709, AMD driver 18.5.1, using Hard disk & mining normal_v7, why in rig 1 (2 Vegas), I can set my Vega 56 with Mem P3 Clock to 920, but in Rig 2(5 Vegas), the max Mem P3 Clock I can only set is 895 without any error with Overdriventool??

Any ideas why this is happening??

Any help appreciated.

Thanks