How to lower intensity for lyra2rev3? I get 52 MH/s on RX 580 8Gb. But power consumption is too high. About 140-150W. It's need intensity option to lower power cons.
Hi! You need to control power draw (and perf) using your clocks, it's just the correct way to do it. Intensity is such a bogus idea for AMD cards for compute algos that doesn't allocate much mem. You're asking for a way to lower the global size of the scheduled jobs to the point where the card runs much less efficiently because of scheduling overhead and execution micro-variance having a larger effect on the overall hashrate. However, that also increases PCIe chatter and host-side load (that is tiny though). Hence, the proper approach is to tweak clocks and voltages until you end up with a power draw profile you're comfortable with. For CN, we provide ways of tweaking "intensity", but that's a very different ballgame. I allready lower clocks and voltages, but on 1 of my RX 580 GPU's is monitor connected and to work it normal I forced to set core voltage higher about 50 mV. Lower than 0.975V leads to BSOD with thread stuck... And on this voltage card consumes about 135-150W on lyra2rev3... |
|
|
|
Sorry Unclwish I won't delay the release to investigate your bug since the Turtle fork is somewhat an emergency issue.
Ok-ok. I'll wait. Note that cards are both RX 580 8Gb. Now I forced to set 2nd GPU 1 thread and 16 multi_hash to start mining at 1st GPU and 2nd GPU almost free, but even 1x16 gives some load on 2nd GPU... |
|
|
|
Can you recommend pool and coin for Lyra2rev3? I want to try!  You can try nicehash with btc wallet. |
|
|
|
|
Miner needs nicehash compatibility!
|
|
|
|
|
How to lower intensity for lyra2rev3? I get 52 MH/s on RX 580 8Gb. But power consumption is too high. About 140-150W. It's need intensity option to lower power cons.
|
|
|
|
|
Why on nicehash shares often rejected with invalid nonce error?
|
|
|
|
|
Please, add support for nicehash.
|
|
|
|
Can't launch miner to use only 1st GPU. For both of GPU's all works fine. When I remove from config.txt all strings with GPU 1 lefting only GPU 0, miner starts and after connecting to pool closes. In events error with attrib.exe In log: Starting GPU Thread 0, on GPU 0
Created OpenCL Context for GPU 0 at 0000022fca316a00
Created OpenCL Thread 0 Command-Queue for GPU 0 at 0000022fca0f7830
Scratchpad Allocation success for OpenCL Thread 0
Allocating big 3968MB scratchpad for OpenCL Thread 0...
Compiling kernels of OpenCL Thread 0...
Kernels of OpenCL Thread 0 compiled.
Allocated shared Large Page at: 000002308de00000
Allocated 8MB Cached Large Page Scratchpad Buffer at: 000002308e000000
17:48:18 | Nicehash Mining session starts!
17:48:18 | GPU Compute allocation starts at 80% and reaches 100% after ~1min,
17:48:18 | during this time, the hashrate may be unstable and inconsistent.
17:48:18 | Let the miner warm-up if you're tuning for performance.
17:48:19 | Connecting to mining pool cryptonightheavy.eu.nicehash.com:3364 ...
17:48:19 | Connected to pool. Now logging in...
17:48:19 | Successfuly logged as xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.JCE1stGPU
17:48:19 | Pool changes Difficulty to 50000.
|
|
|
|
2019.01.16:19:39:00.717: main Phoenix Miner 4.0b Windows/msvc - Release build
2019.01.16:19:39:00.717: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001
2019.01.16:19:39:00.717: main No CUDA driver found
2019.01.16:19:39:06.406: main Unknown OpenCL driver version! Hashrate and stale shares may suffer
2019.01.16:19:39:06.406: main OpenCL platform: OpenCL 2.1 AMD-APP (2766.5)
2019.01.16:19:39:06.406: main Available GPUs for mining:
how do i fix this problem?
You have upgraded your driver to version that is not yet supported by PhoenixMiner (see the line Unknown OpenCL driver version! Hashrate and stale shares may suffer in the log, it will be printed as yellow warning on your screen when the miner starts). It is not a good idea to update to drivers that are newer than the release of PhoenixMiner you are using because this means we weren't able to test this release of PhoenixMiner with these drivers and they probably won't work well (or at all). To fix the problem either upgrade to PhoenixMiner 4.1c, which supports AMD drivers up to and including 19.1.1. Sadly 4.1c does not support 19.1.1, as it gives the Unknown OpenCL version error and suffers a hashrate loss because of it. -clkernel 3 mode does not even work with it. ( clSetKernelArg (-49) ) I have 19.1.1 installed and latest version of miner works normal. RX 580 8 Gb Windows 10. |
|
|
|
P4 32 bits crash on Linux: I'll redo a test on my Core2 duo, the oldest CPU i have, but not sure at all i can reproduce the bug  Sad it would have shined since old cpu mining is my niche expertise, but maybe you use some old Linux distrib or something. It's a lot harder to support linux well because of the large variety of distribs. And i'm also more a Windows person. Large pages, see the doc here, it needs to be manually enabled, but that's the exact same as for any other miner, so if you find a guide for xmrstak/xmrig/whatever, it will work the same. https://github.com/jceminer/cn_cpu_miner#large-pagesJCE miner can't enable large pages if they disabled? Maybe you add this option in miner to auto-enable them like Claymore? |
|
|
|
Processor AMD Ryzen3 2200G Why? Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000018bfe000000
Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower). This can accure if you system have small amount of RAM or running too long from boot. Try to reboot and launch again. |
|
|
|
That answers exacly none of the questions i asked.
You can't recieve better speed on heavy algo than double threads with 944 multi_hash. Any other value will slower speed. And you can't reduce pagefile size. It's neccesary to have enough page file size to miner work normal. His size must be equal to size of videomemory used during miming. 2x944 multi_hash is almost 8Gb (about 7,5-7,7Gb) of videomemory during heavy algo mining. |
|
|
|
I'm trying out one cnHeavy coin.
I have 12 GPUS in the windows10 rig and I have set up 88GB swap file, now my SSD in rig is almost full, but still, my last to GPUs run in single thread, i left it at 944 intensity.
Is there a way to get better performance with different multi_hash setting then 944, or even better reduce page file/swap/virtual memory usage?
You can place your pagefile into different drives. 1st part about 8-16Gb of it you must place on system drive to improove speed. Other parts you can place into any other drive via pagefile settings. |
|
|
|
delay: that's an option that already exists in xmrstak, with a default of 40%. in jce this is automated, and yes it's related to the warmup. i won't add it as manual param, i'm confident with my automated values.
Right! Automated delay is better than manual tuning... |
|
|
|
|
Hi JCE! Doc releases new version of his miner and added thread_delay option. It can be changed manually for each GPU. Is this is what your miner does during warm-up? It try to find best thread delay? Delay between starting mining on 2 or more threads on one GPU?
|
|
|
|
i tried the gpu version on my laptop (win7 64 bit) but the attrib.exe always crashed on start. then i tried the cpu version, but the result are same. this is the win's log: Problem signature:
Problem event name: APPCRASH
Application Name: attrib.exe
Application Version: 6.1.7600.16385
Application Time Stamp: 4a5bc262
Error Module Name: ntdll.dll
Error Module Version: 6.1.7601.24024
Error Module Time Stamp: 5a58e571
Exception code: c0000026
Exception - offset: 00000000000c8a08
Operating System Version: 6.1.7601.2.1.0.256.1
Locale identifier: 1038
More information 1: 18d9
More information 2: 18d92874322adbc162708e4fec1a6d55
More information 3: 81d9
More information 4: 81d9b1ae568ccfbf94a4305bb26177ca
GPU version of miner works only on Windows 8.1+ |
|
|
|
|
JCE, didn't you thought about making ethereum miner? About a week it's more profitable than any cn algo on 470/480/570/580 cards...
|
|
|
|
|
Happy New 2019 Year All miners!
|
|
|
|
|
JCE, what plans you have now? On GPU part... Any enchancements for speed, or energy saving?
|
|
|
|
@Unclwish: try those: "cpu_threads_conf" :
[
{ "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true },
]
"cpu_threads_conf" :
[
{ "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : false },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : false },
]
But on a small AES intel CPU, i'm not that faster, when i am. Except on Bittube. It's possible i don't even compensate for the 1.5% fees, assuming you compiled xmrig with no fees. 1st variant - 57 h/s 2nd - 54 h/s My variant "cpu_threads_conf" :
[
{ "cpu_architecture" : "auto", "affine_to_cpu" : false, "use_cache" : true, "multi_hash" : 5 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : false, "use_cache" : true, "multi_hash" : 5 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : false, "use_cache" : true, "multi_hash" : 5 },
]
This variant gives 64 h/s and CPU load only 75% for comfort doing my work)))) On XMRig tha same config gives 72-75 h/s (and you're right about fee))) Overloading L3 cache by multi_hash gives additional speed... |
|
|
|
|
Show Posts
