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

[UnclWish]

any have a config? for mining only 1 / 2 /3 gpu
i am try -d command not run

Use config file in wich describe only your 3 gpu's. Like this:

"gpu_threads_conf" :
[
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":832 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":832 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":832 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":832 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 2, "multi_hash":832 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 2, "multi_hash":832 },
]

[1714633834]

1714633834

[1714633834]

1714633834

[heavyarms1912]

On 8Gb cards 944 isn't best multi_hash. Try to use 1836.

I had the settings swapped in my post for 4gb and 8gb cards.  1836 for CN-Heavy/Saber dual threads.  Will that even work?

Of course not. I thought you wrote about v7 algo. On heavy algo max is 944 for 8Gb. On higher values speed is drops due to lack of vmemory.
For heavy algo on 8Gb best multihash is 832 (and maybe 864) and dual threads.

Yea those numbers are for CN-Saber which is a bit heavier algo than CN-Heavy too.  Those are 944,1 thread on 4g cards and 832,2 threads on 8gb cards.

[vmozara]

Hi everybody,

now already some more time has passed with testing JCE miner and all I can say this is hands down the best and most reliable miner at least for CN7 and Vega cards.

All my machines had uptime of 200+ hours before  shut down yesterday to change the pool. There was 0 cards with hash drop, and I got 10 total invalid shares (GPU issue, nothing with miner)

I am still on 031C version because I am far away from home so I didn´t bother with remote changing

JCE, i guess now there is already many users and miners testing your miner with all kinds of suggestions, questions etc, don´t get overwhelmed and give up, just keep developing, i hope you receive now decent money from the miner fees to support yourself/family

In the beginning I was suggesting features like watchdog but considering I had 0 issues I don´t even know if this is necessary

There is few things I would like to see if possible to implement:
1. GPU displaying its BUS Id
2. Invalid shares statistic in Results, for example instead of Valid shares found 865, just write valid shares 865/888
3. Statistic of invalid shares in Results, for example if there is 15 invalid shares, to list how many was GPU fault and network fault.

Maybe you already did this in the later versions but I did not upgrade yet

I hope you will make soon enough money to get yourself a Vega card for testing

[JCE-Miner]

Thanks

It's true i log very few overall info, and nothing about bad shares (well, they are displayed at the moment they are found, but not accumulated, so you don't know how many bad share you had). The yellow log may have one extra line for bad shares.

Online is the very experimental 0.32

It uses a completely new OpenCL generator that is blazing fast (the generator, not the mining code) : compile now takes about one second but it's very possible it adds regressions, since everything is new. I tried to keed all perfs at max (even on RX550) but i cannot be sure. It was stable on my rig, but i haven't a lot of time to test.

It also introduces the -g parameter to filter the GPUs to mine on. Example: -g 0,2 means: don't mine on a GPU other than 0 or 2.
The auto-config should be a little better.

[Josefonaut]

Cheers for the awesome cpu miner   

[ZCXND]

I give 30min 0.32 on vega i get ~10h/s(2145h/s cryptonight v7) more compare to 0.31f but 8 Rejected Shares (24%) : Low Dificulty 
on rx550/460 it runs ~5 h/s slower (cryptonight v7)
driver 18.5.1

[vmozara]

0.32 vs 0.31c

7x Vega 56 rig on celeron 3855U (very slow cpu) with adrenalin 18.6.1. drivers

14210h/s compared to 14380 on 0.31c
in the beginning (first few minutes) got 5-6 invalid shares but after that no bad shares
super fast compiling, miner started in like 30 seconds

i will keep it running for hashrate to stabilize and report after few hours
 

[JuanHungLo]

Thanks

It's true i log very few overall info, and nothing about bad shares (well, they are displayed at the moment they are found, but not accumulated, so you don't know how many bad share you had). The yellow log may have one extra line for bad shares.

Online is the very experimental 0.32

It uses a completely new OpenCL generator that is blazing fast (the generator, not the mining code) : compile now takes about one second but it's very possible it adds regressions, since everything is new. I tried to keed all perfs at max (even on RX550) but i cannot be sure. It was stable on my rig, but i haven't a lot of time to test.

It also introduces the -g parameter to filter the GPUs to mine on. Example: -g 0,2 means: don't mine on a GPU other than 0 or 2.
The auto-config should be a little better.

Unfortunately, it still won't work for my win 7-64, blockchain drivers, RX 470-8GB with integrated graphics on MB.  Now the output says:

...Detecting OpenCL-capable GPUs...
Calling clGetPlatformIDs
Returned CL_UNKNOWN_ERROR -1001
Found 0 OpenCL PlatformIDs

�êË

[JCE-Miner]

i'm turning one rig to win7 + betablockchain, but i've very little time to test everything.
I could reproduce the bad share bug, now fixing.

[vmozara]

Great, thanks! Fast compiling is really amazing, the rig that was starting 15 minutes before, now starts in seconds, this is really useful for testing and troubleshooting

[UnclWish]

Tested new 32 version. Works fine. Especcially fast compiling - it's amazing! Thanx for it!

But I noticed that settings for GPU's now optimal some other than before. Maybe it's due to 18.7.1 driver.
Now best m.hash for heavy algo is 944, not 832 or 864...
For normal V7 close to twice m.hash from heavy.

And i noticed that speed now not so stable on heavy algo. It jumps +50-100 h/s up and down even after 10 minutes of mining...

[heavyarms1912]

@JCE-Miner

is the net effective hashrate the cumulative of 46 hours of mining?

13:53:32 | Total: 7277.79 h/s - Max: 7289.39 h/s
13:53:34 | GPU 3 Thread 3 Lane 688 finds a Share, value 100001
13:53:34 | Accepted by the pool.
13:53:36 | Pool mining.bit.tube:13333
13:53:36 | Currency BitTube (TUBE)
13:53:36 | Current pool Difficulty 100001
13:53:36 | Valid Shares found 11877
13:53:36 | Total hashes 1186051850
13:53:36 | Miner uptime 46:18:46
13:53:36 | Effective net hashrate 7113.78 h/s

[JCE-Miner]

this is the total amount of shares found, divided by the uptime.
Said differently, the full average of effective speed (taking into account shares really found, ignoring fees and rejected stale shares).

It should be the same as reported by your pool, minus ~1% since some shares are reported good because of ping but are dropped at last instant by the pool. Most pool do that, the notable exception is Nicehash who explicitely refuse any stale share, even cause by ping delay. Hence why you get more reject on Nicehash.

Optimal settings of 0.32+ may be different from previous versions since the code is all new.

Version 0.32a online

Same as 0.32, but bad shares are fixed.
0.32 is removed from github.

[vmozara]

In fact, JCe-miner is the first closed source miner that reports spot-on hashrate as the pool does.

Srbminer and cast-xmr report way more than pool. XMR-stak reports accurate, but the JCE is much faster

[vmozara]

I started 032a on one of my rigs. 032 had many invalids at start, 032a has a good start without invalids

[frozen80]

@JCE-Miner

Is it possible that the config generated by the --auto option can also be written in a text file or at least showed in the output?
I have good results for the Vega on the auto config and it would be nice to know the parameters of the config just in case i want to use the -c option later on.

Tnx dev.
Keep up the good work!

Lol ... It is already in the output ... i didn't notice.

[UnclWish]

JCE, I think you must change string when kernels compiles. It still writes "...it will be long..." Now it quick )))

[heavyarms1912]

In fact, JCe-miner is the first closed source miner that reports spot-on hashrate as the pool does.

Srbminer and cast-xmr report way more than pool. XMR-stak reports accurate, but the JCE is much faster

not really. it depends.  I have been using other miner and in fact, I get higher avg hashrate than the miner reports at the pool side.  Right now JCE gives me higher at least on Tube.

[vmozara]

I don´t really want to go through that discussion again. I don´t care what is shown on the screen. If one miner, over the span of 10 days, gives 10 billion hashes and another gives 9 billion hashes, but both shows 12KH/s, then these miners are not the same speed. One is real (JCE, XMR-Stak) and another is fuckin´ liar and cheater.

Cheers

[UnclWish]

JCE, please, add in report speed statistics for periods of time. An half hour, hour, etc...
And it's need minrigspeed option to restart miner if speed lower than pointed in option for 5 min or time pointed in 2nd option minrigspeedperiod.

P.S. Looks like at start and during several minutes in heavy algo speed every time differs...