Pages:
Author

Topic: [XMR] JCE Miner Cryptonight/forks, now with GPU! - page 26. (Read 90841 times)

newbie
Activity: 14
Merit: 0

Online is the 0.33b-y

* A lot less tested than a regular version, i hope there's no bugs out there
* Fees lowered back to 0.9% on all algos, as I'm no longer 20% faster than the reference code
* More hybrid, so should eat a bit more CPU
* Bad shares on Heavy fixed, at least i had zero during my 5-hour test session
* Light optim ~2% for HD7000 is backported to HD6000
* It was more stable on my rig, but i'm doubting of such observations Cry

That's the standalone .exe on Github, as for the previous b-x

I'm become crazy , i've 3 PC and ALL Crash, with 14.4 driver and 6950HD, i've allready post my config.
Could u help me ? i'm very glad to fee you my hash Smiley

I must use this 14.4 driver with your miner ?  i'm the only one who have problem with 6950. Huh
sr. member
Activity: 1484
Merit: 253
I think that 1st what need to do - is stabilizing heavy algo speed, 2nd - lowering power consumption for v8.
newbie
Activity: 4
Merit: 0
Hello JCE-Miner, can you please look into temperature/fan monitoring? It does not work for me at all. Temp and fan are always zero...
I'm using 18.6.1 driver version. Windows 10 1709 and 1803.
Miner version 0.33b6 (tried previous versions - same result).
Cards are different - mix of RX470/RX480/RX570/RX580 - Asus and Powercolor.
This is reproduced on all my rigs with different hardware and even platform (intel and amd).
member
Activity: 340
Merit: 29
@JCE-Miner - this brings up a feature ask...  Can we get a configurable watchdog delay?  The hour-long warmups aren't terribly bothersome (to me) as long as the miner is stable, but the 5-min watchdog is useless for these scenarios.
member
Activity: 340
Merit: 29
thanks all for your feedbacks.

i expected a speed regression on big cards, the b-x/y is rather for the old cards, but is the varying hashrate fixed in such case ?

there's nothing i can do about your browser or antivirus blocking the download, you have to add exceptions or disable security temporarily. jce contains no malicious code, it's just a miner.

there should be a little boost for Hawaii but didn't have time to decently bench.


i take note of the display bug in the report, i've also to make the reconnect to reset the hash counter


It's looking to me like 33 in general is a regression for heavy on 8g polaris.   I am able to get to ~1175h/s on 32q after 15min or so, and it pretty much sticks there.  On 33b-y, with same exact settings (both miner config and gpu) I can only get to 1025-1050, though it does get to stable faster it seems.  In a 12 hr test, it did touch 1165 for a single reporting cycle (hours into the run,) but immediately returned to 1035.  I am now running 33b5, and while it's only been up ~30min, it does not appear to be any different from 33b-y.

EDIT: Looks like i was wrong - about 1.25 hours in on my 33b5 test, h/r ramped up to 1250.  Will let it continue running to test stability.
sr. member
Activity: 1484
Merit: 253
On 588 cards speed on b-y version is a bit lower and a little more stable, but still start to fluctuate after some time... Bad shares became rare...
member
Activity: 350
Merit: 22
thanks all for your feedbacks.

i expected a speed regression on big cards, the b-x/y is rather for the old cards, but is the varying hashrate fixed in such case ?

there's nothing i can do about your browser or antivirus blocking the download, you have to add exceptions or disable security temporarily. jce contains no malicious code, it's just a miner.

there should be a little boost for Hawaii but didn't have time to decently bench.


i take note of the display bug in the report, i've also to make the reconnect to reset the hash counter
newbie
Activity: 417
Merit: 0
xmrig is no longer a clone of Wolf0 miner, they really provide their own code with own optimizations.
Including some i found 6 months ago, but not all, so i don't think they hacked my miner, just they knew where to look for performance, as TeamRed hinted me, and i hinted SRB. Experienced devs facing the same problem find the same solution, normal.

Online is the 0.33b-y

* A lot less tested than a regular version, i hope there's no bugs out there
* Fees lowered back to 0.9% on all algos, as I'm no longer 20% faster than the reference code
* More hybrid, so should eat a bit more CPU
* Bad shares on Heavy fixed, at least i had zero during my 5-hour test session
* Light optim ~2% for HD7000 is backported to HD6000
* It was more stable on my rig, but i'm doubting of such observations Cry

That's the standalone .exe on Github, as for the previous b-x

This version block my 6*vega 56 nitro rig  after 1 min  in ARTOcashe and XTL
Tube have ony 9000HR- last version have 11600HR.
Setup is identical.
full member
Activity: 729
Merit: 114
xmrig is no longer a clone of Wolf0 miner, they really provide their own code with own optimizations.
Including some i found 6 months ago, but not all, so i don't think they hacked my miner, just they knew where to look for performance, as TeamRed hinted me, and i hinted SRB. Experienced devs facing the same problem find the same solution, normal.

Online is the 0.33b-y

* A lot less tested than a regular version, i hope there's no bugs out there
* Fees lowered back to 0.9% on all algos, as I'm no longer 20% faster than the reference code
* More hybrid, so should eat a bit more CPU
* Bad shares on Heavy fixed, at least i had zero during my 5-hour test session
* Light optim ~2% for HD7000 is backported to HD6000
* It was more stable on my rig, but i'm doubting of such observations Cry

That's the standalone .exe on Github, as for the previous b-x

I really appreciate your straightforwardness.

p.s. Seems like detection of iGPU is back Cheesy
member
Activity: 1558
Merit: 69
Hallo JCE ich versuche 2 Tage den JCE Miner von Github zum downloaden. Leider blockiert mir Google Chrom den download. was kann ich tun um diesen Miner zu bekommen ( Sicherheitseinstellung hab ich geändert). Anderen Browser?

Du siehst aber schon das wir hier in einen englischen Forum sind und du englisch schreiben musst oder geh in den deutschen Abteil.
Wenn du aber schon probleme hast einfach in Chrome auf Datei behalten zu drücken nach dem download (Downloadtab öffnen nach Download), dann wirds mit dem ganzen rest hier schwierig.
newbie
Activity: 30
Merit: 0
Hallo JCE ich versuche 2 Tage den JCE Miner von Github zum downloaden. Leider blockiert mir Google Chrom den download. was kann ich tun um diesen Miner zu bekommen ( Sicherheitseinstellung hab ich geändert). Anderen Browser?
newbie
Activity: 31
Merit: 0
xmrig is no longer a clone of Wolf0 miner, they really provide their own code with own optimizations.
Including some i found 6 months ago, but not all, so i don't think they hacked my miner, just they knew where to look for performance, as TeamRed hinted me, and i hinted SRB. Experienced devs facing the same problem find the same solution, normal.

Online is the 0.33b-y

* A lot less tested than a regular version, i hope there's no bugs out there
* Fees lowered back to 0.9% on all algos, as I'm no longer 20% faster than the reference code
* More hybrid, so should eat a bit more CPU
* Bad shares on Heavy fixed, at least i had zero during my 5-hour test session
* Light optim ~2% for HD7000 is backported to HD6000
* It was more stable on my rig, but i'm doubting of such observations Cry

That's the standalone .exe on Github, as for the previous b-x

Is there any improvement for R9 390?
newbie
Activity: 11
Merit: 0
Wrong comparition - different versions, drivers and even memory freq...
even if the comparison is positive, i've to agree it's wrong until the only change is the miner version.
please tell what config you used and what did you mine.

The frequency was the same at the beginning but I lowered the timing later and there was a decrease in the hasrate. And the drivers always update to the newest, here I just downgraded after problems on 18.11.2 with another program.

Monero v8 -I've used this conf since you released gpu v8. I tested different configurations and this is optimal for my RX 550 from Gigabyte (Hynix Memory), and Bios mod SRBPolaris.
Quote
"gpu_threads_conf" :
[
     { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":432 },
     { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 0, "multi_hash":432 },
     { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 2, "multi_hash":432 },
     { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 2, "multi_hash":432 },
     { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 3, "multi_hash":432 },
     { "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 3, "multi_hash":432 },
]

And especially now I came back to 18.11.1, and higher frequency 2050MHz


Quote
Quote
Quote from: polsska on November 18, 2018, 08:12:28 AM
b-x
3x RX 550 2GB (1315MHz core, 2050MHz mem, drivers 18.11.1, Win 10 1809)


Quote
09:08:36 | Hashrate GPU Thread 0: 258.57 h/s
09:08:36 | Hashrate GPU Thread 1: 256.64 h/s - Total GPU 0: 515.21 h/s
09:08:36 | Hashrate GPU Thread 2: 253.11 h/s
09:08:36 | Hashrate GPU Thread 3: 258.37 h/s - Total GPU 2: 511.47 h/s
09:08:36 | Hashrate GPU Thread 4: 248.62 h/s
09:08:36 | Hashrate GPU Thread 5: 255.99 h/s - Total GPU 3: 504.61 h/s
09:08:36 | Total: 1531.28 h/s - Max: 1531.28 h/s


b-y
3x RX 550 2GB (1315MHz core, 2050MHz mem, drivers 18.11.1, Win 10 1809)
Quote
09:46:11 | Hashrate GPU Thread 0: 258.32 h/s
09:46:11 | Hashrate GPU Thread 1: 260.64 h/s - Total GPU 0: 518.95 h/s
09:46:11 | Hashrate GPU Thread 2: 259.60 h/s
09:46:11 | Hashrate GPU Thread 3: 260.64 h/s - Total GPU 2: 520.24 h/s
09:46:11 | Hashrate GPU Thread 4: 260.80 h/s
09:46:11 | Hashrate GPU Thread 5: 259.55 h/s - Total GPU 3: 520.34 h/s
09:46:11 | Total: 1559.52 h/s - Max: 1559.52 h/s

09:57:46 | Hashrate GPU Thread 0: 259.45 h/s
09:57:46 | Hashrate GPU Thread 1: 258.01 h/s - Total GPU 0: 517.46 h/s
09:57:46 | Hashrate GPU Thread 2: 260.69 h/s
09:57:46 | Hashrate GPU Thread 3: 254.39 h/s - Total GPU 2: 515.08 h/s
09:57:46 | Hashrate GPU Thread 4: 258.73 h/s
09:57:46 | Hashrate GPU Thread 5: 258.68 h/s - Total GPU 3: 517.40 h/s
09:57:46 | Total: 1549.92 h/s - Max: 1559.52 h/s

10:04:09 | Hashrate GPU Thread 0: 257.45 h/s
10:04:09 | Hashrate GPU Thread 1: 256.34 h/s - Total GPU 0: 513.79 h/s
10:04:09 | Hashrate GPU Thread 2: 248.79 h/s
10:04:09 | Hashrate GPU Thread 3: 256.59 h/s - Total GPU 2: 505.38 h/s
10:04:09 | Hashrate GPU Thread 4: 256.69 h/s
10:04:09 | Hashrate GPU Thread 5: 260.64 h/s - Total GPU 3: 517.33 h/s
10:04:09 | Total: 1536.48 h/s - Max: 1559.52 h/s
10:04:44 | Hashrate GPU Thread 0: 256.04 h/s
10:04:44 | Hashrate GPU Thread 1: 258.11 h/s - Total GPU 0: 514.15 h/s
10:04:44 | Hashrate GPU Thread 2: 267.64 h/s
10:04:44 | Hashrate GPU Thread 3: 251.98 h/s - Total GPU 2: 519.62 h/s
10:04:44 | Hashrate GPU Thread 4: 259.35 h/s
10:04:44 | Hashrate GPU Thread 5: 259.19 h/s - Total GPU 3: 518.53 h/s
10:04:44 | Total: 1552.29 h/s - Max: 1559.52 h/s

And so on the version of b-x about 1530 h/s it was the maxiumum I achieved.
on x-y there is even 30 h/s more on 3 cards, though it is waving but in this range (1530-1560).
But now i back to 18.9.3.









member
Activity: 350
Merit: 22
yes this is this one, a .exe alone since it's an experimental version.
it's backward compatible with previous 0.33
jr. member
Activity: 145
Merit: 1
xmrig is no longer a clone of Wolf0 miner, they really provide their own code with own optimizations.
Including some i found 6 months ago, but not all, so i don't think they hacked my miner, just they knew where to look for performance, as TeamRed hinted me, and i hinted SRB. Experienced devs facing the same problem find the same solution, normal.

Online is the 0.33b-y

* A lot less tested than a regular version, i hope there's no bugs out there
* Fees lowered back to 0.9% on all algos, as I'm no longer 20% faster than the reference code
* More hybrid, so should eat a bit more CPU
* Bad shares on Heavy fixed, at least i had zero during my 5-hour test session
* Light optim ~2% for HD7000 is backported to HD6000
* It was more stable on my rig, but i'm doubting of such observations Cry

That's the standalone .exe on Github, as for the previous b-x
Hello,

Where is the version please ? https://github.com/jceminer/cn_gpu_miner/blob/master/jce_cn_gpu_miner64.exe  ?
member
Activity: 350
Merit: 22
b-x
3x RX 550 2GB (1315MHz core, 2050MHz mem, drivers 18.11.1, Win 10 1809)

Quote
09:08:36 | Hashrate GPU Thread 0: 258.57 h/s
09:08:36 | Hashrate GPU Thread 1: 256.64 h/s - Total GPU 0: 515.21 h/s
09:08:36 | Hashrate GPU Thread 2: 253.11 h/s
09:08:36 | Hashrate GPU Thread 3: 258.37 h/s - Total GPU 2: 511.47 h/s
09:08:36 | Hashrate GPU Thread 4: 248.62 h/s
09:08:36 | Hashrate GPU Thread 5: 255.99 h/s - Total GPU 3: 504.61 h/s
09:08:36 | Total: 1531.28 h/s - Max: 1531.28 h/s


b-y
3x RX 550 2GB (1315MHz core, 2000MHz mem, drivers 18.9.3, Win 10 1809)

Quote
23:42:49 | Hashrate GPU Thread 0: 263.48 h/s
23:42:49 | Hashrate GPU Thread 1: 257.81 h/s - Total GPU 0: 521.28 h/s
23:42:49 | Hashrate GPU Thread 2: 262.63 h/s
23:42:49 | Hashrate GPU Thread 3: 262.63 h/s - Total GPU 2: 525.26 h/s
23:42:49 | Hashrate GPU Thread 4: 260.17 h/s
23:42:49 | Hashrate GPU Thread 5: 256.24 h/s - Total GPU 3: 516.41 h/s
23:42:49 | Total: 1562.94 h/s - Max: 1568.77 h/s
Wrong comparition - different versions, drivers and even memory freq...
even if the comparison is positive, i've to agree it's wrong until the only change is the miner version.
please tell what config you used and what did you mine.


config file: please take a look at the doc in the github page:
https://github.com/jceminer/cn_gpu_miner

there are some example. the key for test is to set a very low value for multi_hash like 64 to check it starts. if yes, increase it until you find the best value, by steps of 16.
for a 4G card this should be around 800 on two threads, a bit more for 8G
if you mine Heavy or similar, the values should be halved (~400 for a 4G)
newbie
Activity: 3
Merit: 0
Hi! JCE-Miner
I have RX550/4G and 470/8G run Haven very good. But rx470/4G and RX570/4G is not run, how config in file" config.txt"?
sr. member
Activity: 1484
Merit: 253
b-x
3x RX 550 2GB (1315MHz core, 2050MHz mem, drivers 18.11.1, Win 10 1809)

Quote
09:08:36 | Hashrate GPU Thread 0: 258.57 h/s
09:08:36 | Hashrate GPU Thread 1: 256.64 h/s - Total GPU 0: 515.21 h/s
09:08:36 | Hashrate GPU Thread 2: 253.11 h/s
09:08:36 | Hashrate GPU Thread 3: 258.37 h/s - Total GPU 2: 511.47 h/s
09:08:36 | Hashrate GPU Thread 4: 248.62 h/s
09:08:36 | Hashrate GPU Thread 5: 255.99 h/s - Total GPU 3: 504.61 h/s
09:08:36 | Total: 1531.28 h/s - Max: 1531.28 h/s


b-y
3x RX 550 2GB (1315MHz core, 2000MHz mem, drivers 18.9.3, Win 10 1809)

Quote
23:42:49 | Hashrate GPU Thread 0: 263.48 h/s
23:42:49 | Hashrate GPU Thread 1: 257.81 h/s - Total GPU 0: 521.28 h/s
23:42:49 | Hashrate GPU Thread 2: 262.63 h/s
23:42:49 | Hashrate GPU Thread 3: 262.63 h/s - Total GPU 2: 525.26 h/s
23:42:49 | Hashrate GPU Thread 4: 260.17 h/s
23:42:49 | Hashrate GPU Thread 5: 256.24 h/s - Total GPU 3: 516.41 h/s
23:42:49 | Total: 1562.94 h/s - Max: 1568.77 h/s
Wrong comparition - different versions, drivers and even memory freq...
newbie
Activity: 11
Merit: 0
b-x
3x RX 550 2GB (1315MHz core, 2050MHz mem, drivers 18.11.1, Win 10 1809)

Quote
09:08:36 | Hashrate GPU Thread 0: 258.57 h/s
09:08:36 | Hashrate GPU Thread 1: 256.64 h/s - Total GPU 0: 515.21 h/s
09:08:36 | Hashrate GPU Thread 2: 253.11 h/s
09:08:36 | Hashrate GPU Thread 3: 258.37 h/s - Total GPU 2: 511.47 h/s
09:08:36 | Hashrate GPU Thread 4: 248.62 h/s
09:08:36 | Hashrate GPU Thread 5: 255.99 h/s - Total GPU 3: 504.61 h/s
09:08:36 | Total: 1531.28 h/s - Max: 1531.28 h/s


b-y
3x RX 550 2GB (1315MHz core, 2000MHz mem, drivers 18.9.3, Win 10 1809)

Quote
23:42:49 | Hashrate GPU Thread 0: 263.48 h/s
23:42:49 | Hashrate GPU Thread 1: 257.81 h/s - Total GPU 0: 521.28 h/s
23:42:49 | Hashrate GPU Thread 2: 262.63 h/s
23:42:49 | Hashrate GPU Thread 3: 262.63 h/s - Total GPU 2: 525.26 h/s
23:42:49 | Hashrate GPU Thread 4: 260.17 h/s
23:42:49 | Hashrate GPU Thread 5: 256.24 h/s - Total GPU 3: 516.41 h/s
23:42:49 | Total: 1562.94 h/s - Max: 1568.77 h/s
member
Activity: 350
Merit: 22
xmrig is no longer a clone of Wolf0 miner, they really provide their own code with own optimizations.
Including some i found 6 months ago, but not all, so i don't think they hacked my miner, just they knew where to look for performance, as TeamRed hinted me, and i hinted SRB. Experienced devs facing the same problem find the same solution, normal.

Online is the 0.33b-y

* A lot less tested than a regular version, i hope there's no bugs out there
* Fees lowered back to 0.9% on all algos, as I'm no longer 20% faster than the reference code
* More hybrid, so should eat a bit more CPU
* Bad shares on Heavy fixed, at least i had zero during my 5-hour test session
* Light optim ~2% for HD7000 is backported to HD6000
* It was more stable on my rig, but i'm doubting of such observations Cry

That's the standalone .exe on Github, as for the previous b-x
Pages:
Jump to: