Topic: [XMR] JCE Miner Cryptonight/forks, now with GPU! - page 36. (Read 90833 times)
How's the warm up for heavy on 0.33b6? Did u manage to improve it?
i read your reports about hashrate stability, i'll focus on stabilize Heavy hashrate as the top priority
Hi. Miner not work with format "user wallet + paymentID.diff". Can you fix it? Please)
I'll do a test on OptimusBlue, they support this syntax
OMG JCE MAN!
Just tested your miner on two 7870 cards. and im getting what I got before with claymore and even better! 400 per card!! NICE!!!!!!!!!!!!!
Now I really need a GPU linux version and watchdog temp asap:D Then your miner will be on par or better than Claymore even!! NICE JOB! =)
Linux: very unlikely, because of lack of time. I dev alone and have all the CPU versions to update too. Cannot afford Linux GPU port from the Adrenalin.Just tested your miner on two 7870 cards. and im getting what I got before with claymore and even better! 400 per card!! NICE!!!!!!!!!!!!!
Now I really need a GPU linux version and watchdog temp asap:D Then your miner will be on par or better than Claymore even!! NICE JOB! =)
Temperature watchdog: added, now testing, for 0.33b6
syntax will be: --max-temp M with integer M>0, in °C
How does the autoswitch work? Using moneroocean.
When I download their fork of xmrig, it does a quick benchmark and saves my hashrates for each algo, then goes from there. How does JCE know which algo is most profitable on my hardware? Does it save hashrates over time?
I gave it a quick shot and it chose cnv8 which is less profitable on a dual core i5 than cryptolight.
When I download their fork of xmrig, it does a quick benchmark and saves my hashrates for each algo, then goes from there. How does JCE know which algo is most profitable on my hardware? Does it save hashrates over time?
I gave it a quick shot and it chose cnv8 which is less profitable on a dual core i5 than cryptolight.
It exists only for the CPU version for now. Then, it just connects and let MoneroOcean switch the algo on the fly. The miner itself takes no decision. MoneroOcean tend to mine mostly on CN-v8, at least when i tested in end of october. When mining such way, with --variation 16, to get more logs about what algo is mined.
example:
Code:
22:08:37 | Connected to pool. Now logging in...
22:08:37 | Algo-autoswitch Pool gets proposed:
22:08:37 | * Original Cryptonight
22:08:37 | * Original Cryptolight
22:08:37 | * Cryptonight V7 fork of April-2018
22:08:37 | * Cryptolight V7 fork of April-2018
22:08:37 | * Cryptonight-XTL fork of May-2018
22:08:37 | * Cryptonight-Alloy fork of May-2018
22:08:37 | * Cryptonight-MKT/B2N fork of May-2018
22:08:37 | * Cryptonight-Arto fork of May-2018
22:08:37 | * Cryptonight-Fast MSR fork of June-2018
22:08:37 | * Cryptolight-Red fork of July-2018
22:08:37 | * Cryptonight V8 fork of Oct-2018
22:08:38 | Successfuly logged as .......
22:08:38 | Auto-select algo switched to: Cryptonight V8 fork of Oct-2018
22:08:38 | Pool changes Difficulty to 100.
22:08:38 | CPU Thread 2 for Cryptonight/forks wakes-up.
22:08:38 | CPU Thread 1 for Cryptonight/forks wakes-up.
22:08:37 | Algo-autoswitch Pool gets proposed:
22:08:37 | * Original Cryptonight
22:08:37 | * Original Cryptolight
22:08:37 | * Cryptonight V7 fork of April-2018
22:08:37 | * Cryptolight V7 fork of April-2018
22:08:37 | * Cryptonight-XTL fork of May-2018
22:08:37 | * Cryptonight-Alloy fork of May-2018
22:08:37 | * Cryptonight-MKT/B2N fork of May-2018
22:08:37 | * Cryptonight-Arto fork of May-2018
22:08:37 | * Cryptonight-Fast MSR fork of June-2018
22:08:37 | * Cryptolight-Red fork of July-2018
22:08:37 | * Cryptonight V8 fork of Oct-2018
22:08:38 | Successfuly logged as .......
22:08:38 | Auto-select algo switched to: Cryptonight V8 fork of Oct-2018
22:08:38 | Pool changes Difficulty to 100.
22:08:38 | CPU Thread 2 for Cryptonight/forks wakes-up.
22:08:38 | CPU Thread 1 for Cryptonight/forks wakes-up.
Quote
Auto-select algo switched to: Cryptonight V8 fork of Oct-2018
Here that's MoneroOcean that chose the algo, among those listed above "gets proposed"
How does the autoswitch work? Using moneroocean.
When I download their fork of xmrig, it does a quick benchmark and saves my hashrates for each algo, then goes from there. How does JCE know which algo is most profitable on my hardware? Does it save hashrates over time?
I gave it a quick shot and it chose cnv8 which is less profitable on a dual core i5 than cryptolight.
When I download their fork of xmrig, it does a quick benchmark and saves my hashrates for each algo, then goes from there. How does JCE know which algo is most profitable on my hardware? Does it save hashrates over time?
I gave it a quick shot and it chose cnv8 which is less profitable on a dual core i5 than cryptolight.
OMG JCE MAN!
Just tested your miner on two 7870 cards. and im getting what I got before with claymore and even better! 400 per card!! NICE!!!!!!!!!!!!!
Now I really need a GPU linux version and watchdog temp asap:D Then your miner will be on par or better than Claymore even!! NICE JOB! =)
Just tested your miner on two 7870 cards. and im getting what I got before with claymore and even better! 400 per card!! NICE!!!!!!!!!!!!!
Now I really need a GPU linux version and watchdog temp asap:D Then your miner will be on par or better than Claymore even!! NICE JOB! =)
Thanks for all the info everything has been giving!
Latest version of JCE.
4 x Vega 56 Reference with V64 BIOS
1475 / 915 and 1100 /900
Getting 1650h/s per card
Current Config:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":896 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":896 },
Driver :24.20.13011.1009
Tried various configs, cannot get more than 1650h/s.
Any advice?
And is it normal for JCE not to show temp and fan speed?
Thanks
Latest version of JCE.
4 x Vega 56 Reference with V64 BIOS
1475 / 915 and 1100 /900
Getting 1650h/s per card
Current Config:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":896 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":896 },
Driver :24.20.13011.1009
Tried various configs, cannot get more than 1650h/s.
Any advice?
And is it normal for JCE not to show temp and fan speed?
Thanks
Is it on CN-v8?
Try:
or, alternative
TeamRed is a very good Miner that just came out, specialized into CN-v8 on Vega, so i'm not jealous if you find them to be faster. We all were impressed by their performances. Just keep in mind they have 2.5% fees, i've 0.9%.
Well configured, JCE should be almost on par with TeamRed, maybe 1% or 2% slower.
Try:
Code:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "index" : ..., "multi_hash":1920 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "index" : ..., "multi_hash":1920 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "index" : ..., "multi_hash":1920 },
or, alternative
Code:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : ..., "multi_hash":1936 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : ..., "multi_hash":1936 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : ..., "multi_hash":1936 },
TeamRed is a very good Miner that just came out, specialized into CN-v8 on Vega, so i'm not jealous if you find them to be faster. We all were impressed by their performances. Just keep in mind they have 2.5% fees, i've 0.9%.
Well configured, JCE should be almost on par with TeamRed, maybe 1% or 2% slower.
yes sorry v8
i try your configs and report thanks
Is it on CN-v8?
Try:
or, alternative
TeamRed is a very good Miner that just came out, specialized into CN-v8 on Vega, so i'm not jealous if you find them to be faster. We all were impressed by their performances. Just keep in mind they have 2.5% fees, i've 0.9%.
Well configured, JCE should be almost on par with TeamRed, maybe 1% or 2% slower.
Try:
Code:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "index" : ..., "multi_hash":1920 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "index" : ..., "multi_hash":1920 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "index" : ..., "multi_hash":1920 },
or, alternative
Code:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : ..., "multi_hash":1936 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : ..., "multi_hash":1936 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : ..., "multi_hash":1936 },
TeamRed is a very good Miner that just came out, specialized into CN-v8 on Vega, so i'm not jealous if you find them to be faster. We all were impressed by their performances. Just keep in mind they have 2.5% fees, i've 0.9%.
Well configured, JCE should be almost on par with TeamRed, maybe 1% or 2% slower.
what is gut conf for vega56/64 ?
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "index" : 0, "multi_hash":1792 },
{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "index" : 0, "multi_hash":1792 }
]
only 1720hs, teamred give 1980hs
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "index" : 0, "multi_hash":1792 },
{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "index" : 0, "multi_hash":1792 }
]
only 1720hs, teamred give 1980hs
hello!
Documentation:
https://github.com/jceminer/cn_gpu_miner#troubleshooting
Last question:
I'm about to release a minor update with more stable hashrates for Heavy (I hope...), no more autoconfig on Intel GPU (causes a lot of troubles) and smoother autoconfig on AMD ones. And a little optim for Monero v8.
Documentation:
https://github.com/jceminer/cn_gpu_miner#troubleshooting
Last question:
Quote
Q. I get error D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Intel GPUs are now enabled among AMD GPUs, ensure you're not applying a previous AMD configuration to an Intel GPU
Intel GPUs are now enabled among AMD GPUs, ensure you're not applying a previous AMD configuration to an Intel GPU
I'm about to release a minor update with more stable hashrates for Heavy (I hope...), no more autoconfig on Intel GPU (causes a lot of troubles) and smoother autoconfig on AMD ones. And a little optim for Monero v8.
Hello!
After updating 0.33h and higher, an error appears when starting the miner:
Abort was called at 318 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Help fix it. 6*Vega64, Win10, 18.6.1 drivers.
After updating 0.33h and higher, an error appears when starting the miner:
Abort was called at 318 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Help fix it. 6*Vega64, Win10, 18.6.1 drivers.
0.33 B5 is ways too unstable on my system, even after lowering the intensity.
0.33 B4 seems to work better.
My 3 GPU are RX570 4GB with undervolting and mem OC. I have a very stable and satisfying config with 0.32G.
Right now mining XTL.
HR: 2739H/s, power: 335W
Have you tried lower intensities?0.33 B4 seems to work better.
My 3 GPU are RX570 4GB with undervolting and mem OC. I have a very stable and satisfying config with 0.32G.
Right now mining XTL.
HR: 2739H/s, power: 335W
Code:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
],
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
],
I found 464 (and 448 for one card) to be the best. Anything above that and it'll start crashing. Hashrate per 570 is 857 h/s across all 7 cards of my rig (some are flaky so clocked a bit lower - range is basically 825-900).
0.33 B5 is ways too unstable on my system, even after lowering the intensity.
0.33 B4 seems to work better.
My 3 GPU are RX570 4GB with undervolting and mem OC. I have a very stable and satisfying config with 0.32G.
Right now mining XTL.
HR: 2739H/s, power: 335W
0.33 B4 seems to work better.
My 3 GPU are RX570 4GB with undervolting and mem OC. I have a very stable and satisfying config with 0.32G.
Right now mining XTL.
HR: 2739H/s, power: 335W
Code:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
],
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 672},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 928},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 912},
],
i read your reports about hashrate stability, i'll focus on stabilize Heavy hashrate as the top priority
Hi. Miner not work with format "user wallet + paymentID.diff". Can you fix it? Please)
Hashrate is unstable. I just restarted a few times until I got stable hashrate.
Now getting 1800hs on vega56 stable. 1470/899mv core 1098/870mv memory
Whole rig.
2x rx570 4gb and 4x vega56
8970hs 940watts at the wall.
Just waiting to confirm on the long run at pool hashrate.
Now getting 1800hs on vega56 stable. 1470/899mv core 1098/870mv memory
Whole rig.
2x rx570 4gb and 4x vega56
8970hs 940watts at the wall.
Just waiting to confirm on the long run at pool hashrate.
guys! i recently got a rx550, 2gb. Any idea if i can get more than 300h/s on cn-heavy? 
14:52:33 | Hashrate CPU Thread 0: 30.92 h/s - Total CPUs: 30.92 h/s
14:52:33 | Hashrate GPU Thread 1: 168.05 h/s
14:52:33 | Hashrate GPU Thread 2: 168.01 h/s - Total GPU 0: 336.05 h/s
14:52:33 | Hashrate GPU Thread 3: 853.76 h/s
14:52:33 | Hashrate GPU Thread 4: 854.35 h/s - Total GPU 1: 1708.10 h/s
14:52:33 | Hashrate GPU Thread 5: 863.24 h/s
14:52:33 | Hashrate GPU Thread 6: 867.02 h/s - Total GPU 2: 1730.25 h/s
14:52:33 | Hashrate GPU Thread 7: 828.42 h/s
14:52:33 | Hashrate GPU Thread 8: 829.00 h/s - Total GPU 3: 1657.42 h/s
14:52:33 | Hashrate GPU Thread 9: 850.04 h/s
14:52:33 | Hashrate GPU Thread 10: 851.09 h/s - Total GPU 4: 1701.12 h/s
14:52:33 | Total: 7163.84 h/s - Max: 7164.03 h/s
GPU 0 is Gigabyte RX550 2GB (elpida) mining on Haven and as a display
Here is my config :
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash":216 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash":216 },
However, there is one strange thing about my Vega 56 hashrate. 1 of any Vega (random) always drop to 16xx h/s (about 60 h/s) after each miner restart.
Here are my Vega 56 config :
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash":896 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash":896 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 3, "multi_hash":896 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 3, "multi_hash":896 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 4, "multi_hash":896 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 4, "multi_hash":896 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 5, "multi_hash":896 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 5, "multi_hash":896 },
Any ideas ??
PPT according to vegaminingguides.com but Core @870mV and memory @860mV
It first i’ve posted this on https://github.com/jceminer/cn_cpu_miner/issues/26 but here I might get the anser quicker:
Code:
is it possible somehow to specify which algorithms should be selected when using "Pool-managed Autoswitch" variany in JCE?
I have been previously mining on MoneroOcean with MM.js proxy miner, that've configured with manually gathered performance benchmarks, for example:
...
"algo_perf": {
"cn/xtl": 54.17,
"cn/2": 54.56,
"cn/msr": 111.15,
"cn-lite": 172.73,
"cn-heavy": 29.44,
"cn-heavy/tube": 22.53
},
With these, MoneroOcean is able to decide which coin would be most profitable to mine on my setup (in my case, it would be cn-lite algorithm, a.k.a Cryptolight V7 fork of April-2018)
Unfortunately when I've configured JCE miner with variant 16 (Pool-managed Autoswitch) - it's mining only with Cryptonight V8 fork of Oct-2018.
Is it possible to specify somehow particular algorithms performance, that would be than used by MoneroOcean to decide which coin is most profitable to mine?
I have been previously mining on MoneroOcean with MM.js proxy miner, that've configured with manually gathered performance benchmarks, for example:
...
"algo_perf": {
"cn/xtl": 54.17,
"cn/2": 54.56,
"cn/msr": 111.15,
"cn-lite": 172.73,
"cn-heavy": 29.44,
"cn-heavy/tube": 22.53
},
With these, MoneroOcean is able to decide which coin would be most profitable to mine on my setup (in my case, it would be cn-lite algorithm, a.k.a Cryptolight V7 fork of April-2018)
Unfortunately when I've configured JCE miner with variant 16 (Pool-managed Autoswitch) - it's mining only with Cryptonight V8 fork of Oct-2018.
Is it possible to specify somehow particular algorithms performance, that would be than used by MoneroOcean to decide which coin is most profitable to mine?
i read your reports about hashrate stability, i'll focus on stabilize Heavy hashrate as the top priority
Thank you for the confirmation. With previous versions, 033b4 in particular, how much can you get?
Hello,
I've done all test possible with one of my rx580 rigs (6 cards) - OC, multihash, multi windows, ... - the last version is not stable, it is impossible to get all 6 cards to max hashrate.
I've come back to older versions waiting for a stable version.
I've done all test possible with one of my rx580 rigs (6 cards) - OC, multihash, multi windows, ... - the last version is not stable, it is impossible to get all 6 cards to max hashrate.
I've come back to older versions waiting for a stable version.
Tested jce with different gpu. On old gpu like 370 works fine, on v8 can get more than 500 hs. On rx series 4 gb working good.
But i have a lot of problem with 8gb card.
Example, sapphire pulse rx580 8gb hynix memory, fresh windows install with 18.6.1 driver.
Tested with multiple bios mod, srebpolaris 3.5, pbe 3 or 1.6.7 i get very unstable hashrate max to 940 hs, this with 033b4.
With 033b5 can get > than 1000 hs but very very unstable hashrate.
On srbminer get 950 hs but stable without fluctuation.
1200 gpu 2100 or 2150 mem without memory error.
Other experiences with this gpu? Can you get stable 1000 hs or more on v8?
But i have a lot of problem with 8gb card.
Example, sapphire pulse rx580 8gb hynix memory, fresh windows install with 18.6.1 driver.
Tested with multiple bios mod, srebpolaris 3.5, pbe 3 or 1.6.7 i get very unstable hashrate max to 940 hs, this with 033b4.
With 033b5 can get > than 1000 hs but very very unstable hashrate.
On srbminer get 950 hs but stable without fluctuation.
1200 gpu 2100 or 2150 mem without memory error.
Other experiences with this gpu? Can you get stable 1000 hs or more on v8?
Jump to: