vmozara
Member
 Offline
Activity: 190
Merit: 59
|
 |
November 01, 2018, 07:55:50 PM |
|
I got that fault when my intensity was too high. Try to lower it just to see if it works, then tune
|
|
|
|
|
JCE-Miner (OP)
Member
Offline
Activity: 350
Merit: 22
|
|
November 01, 2018, 07:58:37 PM |
|
not fixed yet, the b3 version was to fix the driver 14 bug.
i just took a look at TeamRedMiner, and… wow they did a nice job. looks like the new Claymore grade miner.
i'll do more benches but if i'm too far behind in both consumption and speed, i'll give up the GPU version and focus back to CPU, where i provide the best miner. i may have beaten SRB OpenCL but they use ROCm GCN assembly, a domain i'm not that good.
somehow they did like i did for non-aes cpu, write ultra-optimized assembly that is far faster than anything else.
2.5% fees is high but they worth it.
|
|
|
|
|
pbfarmer
Member
Offline
Activity: 340
Merit: 29
|
|
November 01, 2018, 08:21:10 PM |
|
not fixed yet, the b3 version was to fix the driver 14 bug.
i just took a look at TeamRedMiner, and… wow they did a nice job. looks like the new Claymore grade miner.
i'll do more benches but if i'm too far behind in both consumption and speed, i'll give up the GPU version and focus back to CPU, where i provide the best miner. i may have beaten SRB OpenCL but they use ROCm GCN assembly, a domain i'm not that good.
somehow they did like i did for non-aes cpu, write ultra-optimized assembly that is far faster than anything else.
2.5% fees is high but they worth it.
Yeah - teamred is pretty impressive on cnv2. I benched against srb and your b2 version on a few vegas, and they came out well ahead (~ 5%) for similar power draw, even after that massive fee. Anything in b3 that would be worth benching? Still loving your miner for CPU and heavy & variants on GPU, but b2 was still lagging srb for cnv2, which is now itself lagging teamred :| One issue i do have w/ TR - cnv2 seems to cause occasional massive power spikes, and their miner seems to have made it even worse - so much so that their mean and median power draw has diverged significantly. Their reporting could be better too... |
|
|
|
|
_ap_
Newbie
Offline
Activity: 28
Merit: 0
|
|
November 01, 2018, 08:33:14 PM |
|
many thanks, it's working now!
what steps recommend increase the multi hash? 580 hashrate is very good (prev miner: 930H/s, jce now: 1030H/s), but the 570 a little bit slow (prev miner: 760H/s, jce now: 680H/s)
All, as I thought... Miner used settings for 8gb card on 4gb card... Optimal settings... For 8Gb try { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":944 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":944 }, for 4Gb: { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":472 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":472 }, If with 472 will be error try one of 472 lower to 464. Thanks. I will try.. |
|
|
|
|
JCE-Miner (OP)
Member
Offline
Activity: 350
Merit: 22
|
|
November 01, 2018, 09:05:43 PM |
|
I can recognize when a dev is good, and they are.
They are two people, which is a important point for time. Look how i messed up with the CNv8 deadline because i was away at the wrong time. May have had a buddy dev, it wouldn't have happended. Two people specialized on cn-v8 for RX/vega against me, alone, having to support CPU aes, and non-aes, 32 and 64 bits, and GPU... I cannot win.
I may specialize in older cards they don't support, or just give up all GPUs. But +5% is a huge gap, i don't think I can fill it up.
Still need to bench the real hashrate, after all Claymore 11 was also +5% on screen, but -5% on pool. But beating ROCm with OpenCL is hardly possible.
|
|
|
|
|
vmozara
Member
Offline
Activity: 190
Merit: 59
|
|
November 01, 2018, 10:28:37 PM |
|
You win gold metal for honesty and modesty.  TR miner seems to be really strong at new CN. I have big issues getting it running on every rig, but where it works, it works good and pool side hashrate seems to be correct as well. |
|
|
|
|
slaycho
Newbie
Offline
Activity: 8
Merit: 0
|
|
November 01, 2018, 11:41:56 PM |
|
Can someone help? My RX470 4GB cards cant start at all...When i start my miner at the very start my rig crash every time. I tried --auto mode and its the same. Change the setting of my cards and its still the same....THE ONLY rig that work have RX480 8GB cards ..... Using 18.5.1 and 1803win edition 60Gig virtual mem. Anyone with same problem like me?
your problem I guess is the same with _ap_ which is in auto mode 4GB GPU have 2 thread and multi_hash 864, so better use manual config 4GB GPU 1 thread multi_hash 944 or 2 thread but multi_hash 472. Tnx it worked but now my main GPU always crash.... Do you think if i set the integrated gpu from the cpu for main gpu gonna help? Thank you again! |
|
|
|
|
|
UnclWish
|
|
November 02, 2018, 06:11:52 AM |
|
guys! i recently got a rx550, 2gb. Any idea if i can get more than 300h/s on cn-heavy?  No, 2Gb too small amount to have normal speed on cn-heavy. You can increase speed only by use overclocking and editing memory straps in bios. |
|
|
|
|
fluxy12
Jr. Member
Offline
Activity: 145
Merit: 1
|
|
November 02, 2018, 06:42:00 AM |
|
Hello JCE i still use your miner in all my rigs because TR have not heavy algorithms and they are better than CNv8 ATM, on heavy your miner is far better than others ! (i got 1170h/S for 90W per rx 580).
Don't give away man they would launched heavy algos if they were already better than you.
|
|
|
|
|
JCE-Miner (OP)
Member
Offline
Activity: 350
Merit: 22
|
|
November 02, 2018, 07:12:59 AM |
|
thanks!
i don't give up instantly, and i may keep some niche like Tube and older gpus. but they're really good and will probably add the missing algos. but it doesn't mean they will be faster on Tube, where i'm pretty good. just they added a big +5% on a new algo, and if they are better on both power and hashrate, fees deduced, i'll lose reason to continue my code.
i'm preparing an optimized version for rx560 and rx550, if i get a +2% i may fill the gap, if i get a pitty +0.1% i may giveup. i've more tests to do.
@vmozara: ok i trust you their hashrate is correct, i won't re-bench my side. i know what perf i need to achieve to stay in the race.
|
|
|
|
|
|
UnclWish
|
|
November 02, 2018, 07:25:52 AM |
|
JCE, thanks for your hard work! Miner is great!
Is there some room for heavy algo optimizations? Especcially for 4Gb cards?
|
|
|
|
|
sxemini
Member
Offline
Activity: 1558
Merit: 69
|
|
November 02, 2018, 10:19:06 AM |
|
Someone has good settings for MoneroV8 for the RX550? I can´t get a stable hashrate. I have 6 similiar RX550 with same bios. Hashrate is very unstable and mostly 1 card is slower then all other, and this change all 5min. Monero V7 works stable, and with SRB it works stable too, but with srb the effective pool hashrate is 400h slower then the reported hashrate.
Memory is 2Mb? Try this parameters: { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":464 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":464 } Then try to increase both multi_hash parameters untill your card have enough memory or speed became lower even at start. I have RX550 4GB. I tried worksize 8,12,16 and Multihash i tried 400,416,432,448,464,480,496 in many configs. In every Config it jumps up and down. Driver is 18.6.1. With SRB i get stable hashrate at around 2850 hashes. I manage over 150 GPU´s, so i am not a noob ^^ Maybe it is a driver problem? On my other rigs with JCE Miner i have the beta blockchain driver installed and old pitcairn and tahiti cards, there it works perfect. |
|
|
|
|
sxemini
Member
Offline
Activity: 1558
Merit: 69
|
|
November 02, 2018, 10:27:14 AM |
|
Hey JCE, Issue still persists!: For Windows 64-bits
Analyzing Processors topology...
Intel(R) Celeron(R) CPU G3930 @ 2.90GHz
Assembly codename: generic_aes
SSE2 : Yes
SSE3 : Yes
SSE4 : Yes
AES : Yes
AVX : No
AVX2 : No
Found CPU 0, with:
L1 Cache: 32 KB
L2 Cache: 256 KB
L3 Cache: 2048 KB, shared with CPU 1
Found CPU 1, with:
L1 Cache: 32 KB
L2 Cache: 256 KB
L3 Cache: 2048 KB, shared with CPU 0
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: Intel
Processor: Intel(R) HD Graphics 610
Device: ff:ff
Compute-Units: 12
Cache Memory: 256 KB
Local Memory: 64 KB
Global Memory: 1592 MB
Addressing: 64-bits
Found GPU 1, with:
Vendor: AMD
Processor: Ellesmere
Device: 06:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
Found GPU 2, with:
Vendor: AMD
Processor: gfx900
Device: 09:00
Compute-Units: 64
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8176 MB
Addressing: 64-bits
Found GPU 3, with:
Vendor: AMD
Processor: gfx900
Device: 03:00
Compute-Units: 64
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8176 MB
Addressing: 64-bits
Preparing 7 Mining Threads...
+-- Thread 0 config ------------------------+
| Run on CPU: 0 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+-------------------------------------------+
+-- Thread 1 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 2 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 3 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 4 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 5 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 1120 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 6 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 1120 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
Cryptonight Variation: Cryptonight V8 fork of Oct-2018
Low intensity.
Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000000008400000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 0 of NUMA node 0 at: 0000000008600000
Starting GPU Thread 1, on GPU 1
Created OpenCL Context for GPU 1 at 0000000007d644b0
Created OpenCL Thread 1 Command-Queue for GPU 1 at 0000000007d64610
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3968MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
Starting GPU Thread 2, on GPU 1
Created OpenCL Thread 2 Command-Queue for GPU 1 at 000000000d18a620
Scratchpad Allocation success for OpenCL Thread 2
Allocating big 3968MB scratchpad for OpenCL Thread 2...
Compiling kernels of OpenCL Thread 2...
Kernels of OpenCL Thread 2 compiled.
Starting GPU Thread 3, on GPU 2
Created OpenCL Context for GPU 2 at 0000000007f1ff40
Created OpenCL Thread 3 Command-Queue for GPU 2 at 00000000118530b0
Scratchpad Allocation success for OpenCL Thread 3
Allocating big 3968MB scratchpad for OpenCL Thread 3...
Compiling kernels of OpenCL Thread 3...
Kernels of OpenCL Thread 3 compiled.
Starting GPU Thread 4, on GPU 2
Created OpenCL Thread 4 Command-Queue for GPU 2 at 0000000011852b70
Scratchpad Allocation success for OpenCL Thread 4
Allocating big 3968MB scratchpad for OpenCL Thread 4...
Compiling kernels of OpenCL Thread 4...
Kernels of OpenCL Thread 4 compiled.
Starting GPU Thread 5, on GPU 0
Created OpenCL Context for GPU 0 at 000000001160b0b0
Created OpenCL Thread 5 Command-Queue for GPU 0 at 0000000011598020
Scratchpad Allocation success for OpenCL Thread 5
Allocating big 2240MB scratchpad for OpenCL Thread 5...
Compiling kernels of OpenCL Thread 5...
Kernels of OpenCL Thread 5 compiled.
Starting GPU Thread 6, on GPU 0
Created OpenCL Thread 6 Command-Queue for GPU 0 at 0000000011598190
Scratchpad Allocation success for OpenCL Thread 6
Allocating big 2240MB scratchpad for OpenCL Thread 6...
Compiling kernels of OpenCL Thread 6...
Kernels of OpenCL Thread 6 compiled.
Keep-Alive enabled
Devfee for CPU is 1.5%
Devfee for GPU is 0.9%
21:01:42 | MoneroOcean Mining session starts!
During mining time, press:
h display hashrate for each mining thread.
r display full report.
p pause all.
u pause CPUs.
0-F pause GPU 0-15.
t GPU temperature and fan speed.
q quit.
21:01:42 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
21:01:42 | during this time, the hashrate may be unstable and inconsistent.
21:01:42 | Let the miner warm-up if you're tuning for performance.
21:01:43 | Connecting to mining pool gulf.moneroocean.stream:10064 ...
21:01:43 | Connected to pool. Now logging in...
21:01:44 | Successfuly logged as //PRIVATE INFO//
21:01:44 | Pool changes Difficulty to 64000.
Abort was called at 318 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Press any key to continue . . . You run double thread with 1120 Multihash on the Intel IGPU (GPU 0)? It is not a Miner issue, it is config issue. |
|
|
|
|
Uaciuganadu
Newbie
Offline
Activity: 39
Merit: 0
|
|
November 02, 2018, 10:41:18 AM |
|
Hey JCE, Issue still persists!: For Windows 64-bits
Analyzing Processors topology...
Intel(R) Celeron(R) CPU G3930 @ 2.90GHz
Assembly codename: generic_aes
SSE2 : Yes
SSE3 : Yes
SSE4 : Yes
AES : Yes
AVX : No
AVX2 : No
Found CPU 0, with:
L1 Cache: 32 KB
L2 Cache: 256 KB
L3 Cache: 2048 KB, shared with CPU 1
Found CPU 1, with:
L1 Cache: 32 KB
L2 Cache: 256 KB
L3 Cache: 2048 KB, shared with CPU 0
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: Intel
Processor: Intel(R) HD Graphics 610
Device: ff:ff
Compute-Units: 12
Cache Memory: 256 KB
Local Memory: 64 KB
Global Memory: 1592 MB
Addressing: 64-bits
Found GPU 1, with:
Vendor: AMD
Processor: Ellesmere
Device: 06:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
Found GPU 2, with:
Vendor: AMD
Processor: gfx900
Device: 09:00
Compute-Units: 64
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8176 MB
Addressing: 64-bits
Found GPU 3, with:
Vendor: AMD
Processor: gfx900
Device: 03:00
Compute-Units: 64
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8176 MB
Addressing: 64-bits
Preparing 7 Mining Threads...
+-- Thread 0 config ------------------------+
| Run on CPU: 0 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+-------------------------------------------+
+-- Thread 1 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 2 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 3 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 4 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 5 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 1120 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 6 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 1120 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
Cryptonight Variation: Cryptonight V8 fork of Oct-2018
Low intensity.
Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000000008400000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 0 of NUMA node 0 at: 0000000008600000
Starting GPU Thread 1, on GPU 1
Created OpenCL Context for GPU 1 at 0000000007d644b0
Created OpenCL Thread 1 Command-Queue for GPU 1 at 0000000007d64610
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3968MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
Starting GPU Thread 2, on GPU 1
Created OpenCL Thread 2 Command-Queue for GPU 1 at 000000000d18a620
Scratchpad Allocation success for OpenCL Thread 2
Allocating big 3968MB scratchpad for OpenCL Thread 2...
Compiling kernels of OpenCL Thread 2...
Kernels of OpenCL Thread 2 compiled.
Starting GPU Thread 3, on GPU 2
Created OpenCL Context for GPU 2 at 0000000007f1ff40
Created OpenCL Thread 3 Command-Queue for GPU 2 at 00000000118530b0
Scratchpad Allocation success for OpenCL Thread 3
Allocating big 3968MB scratchpad for OpenCL Thread 3...
Compiling kernels of OpenCL Thread 3...
Kernels of OpenCL Thread 3 compiled.
Starting GPU Thread 4, on GPU 2
Created OpenCL Thread 4 Command-Queue for GPU 2 at 0000000011852b70
Scratchpad Allocation success for OpenCL Thread 4
Allocating big 3968MB scratchpad for OpenCL Thread 4...
Compiling kernels of OpenCL Thread 4...
Kernels of OpenCL Thread 4 compiled.
Starting GPU Thread 5, on GPU 0
Created OpenCL Context for GPU 0 at 000000001160b0b0
Created OpenCL Thread 5 Command-Queue for GPU 0 at 0000000011598020
Scratchpad Allocation success for OpenCL Thread 5
Allocating big 2240MB scratchpad for OpenCL Thread 5...
Compiling kernels of OpenCL Thread 5...
Kernels of OpenCL Thread 5 compiled.
Starting GPU Thread 6, on GPU 0
Created OpenCL Thread 6 Command-Queue for GPU 0 at 0000000011598190
Scratchpad Allocation success for OpenCL Thread 6
Allocating big 2240MB scratchpad for OpenCL Thread 6...
Compiling kernels of OpenCL Thread 6...
Kernels of OpenCL Thread 6 compiled.
Keep-Alive enabled
Devfee for CPU is 1.5%
Devfee for GPU is 0.9%
21:01:42 | MoneroOcean Mining session starts!
During mining time, press:
h display hashrate for each mining thread.
r display full report.
p pause all.
u pause CPUs.
0-F pause GPU 0-15.
t GPU temperature and fan speed.
q quit.
21:01:42 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
21:01:42 | during this time, the hashrate may be unstable and inconsistent.
21:01:42 | Let the miner warm-up if you're tuning for performance.
21:01:43 | Connecting to mining pool gulf.moneroocean.stream:10064 ...
21:01:43 | Connected to pool. Now logging in...
21:01:44 | Successfuly logged as //PRIVATE INFO//
21:01:44 | Pool changes Difficulty to 64000.
Abort was called at 318 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Press any key to continue . . . You run double thread with 1120 Multihash on the Intel IGPU (GPU 0)? It is not a Miner issue, it is config issue. You are absolutely right, i did not notice the re-order and that iGPU was added. Thank you. |
|
|
|
|
mrwhitti
Newbie
Offline
Activity: 4
Merit: 0
|
|
November 02, 2018, 01:12:17 PM |
|
I can recognize when a dev is good, and they are.
They are two people, which is a important point for time. Look how i messed up with the CNv8 deadline because i was away at the wrong time. May have had a buddy dev, it wouldn't have happended. Two people specialized on cn-v8 for RX/vega against me, alone, having to support CPU aes, and non-aes, 32 and 64 bits, and GPU... I cannot win.
I may specialize in older cards they don't support, or just give up all GPUs. But +5% is a huge gap, i don't think I can fill it up.
Still need to bench the real hashrate, after all Claymore 11 was also +5% on screen, but -5% on pool. But beating ROCm with OpenCL is hardly possible.
I agree with you JCE .. the cpu miner is what put you on the map & even after the v8 fork i still use it as it give me the best results on my CPU miners even after a h/r reduction & extra power draw. The v8 fork seems to have favoured the RX & VEGA GPU's as most are now getting v7 hash rates and in some cases even more with the various miners, tweaks & optimizations. I don't see the point in spending time to give maybey the same or +/- 1%-3% hash rate in an already saturated GPU miner field. Everyone is chasing the RX & VEGAS and completely ignoring the lucrative older CPU's which in some cased have taken a up to 25% drop in hash rate with intel ,Xeons,AMD & opterons both 32 & 64 bit which i have experienced myself as i mine with all of them. Many miners have gone offline as it's no longer profitable. FYI: i mine with RX 570's also and pre-fork claymore's miner was tops for me in hash rate/power draw & stability but on v8 i now use xmr-stak which when run dual thread is giving me a higher h/r than i was getting on the claymore v7. Power draw is slightly up but its otherwise rock solid & stable so i personally would'nt bother to switch miner to get a 1% - 3% increase in hash rate. I would hope you will find time to see if miner optimization can reduce the loss suffered by older the CPU's as in truth it is what i want to see now as there are already plenty of GPU miners to choose from. |
|
|
|
|
|
kissmarx
|
|
November 02, 2018, 01:56:28 PM |
|
Thanks JCE Miner. It's great to mine cryptonights using JCE. It is just the best miner that I have tried. It is very easy to use that even the newbie miners will agree with me.
Keep up the good work man.
|
|
|
|
|
sky2018miner
Newbie
Offline
Activity: 33
Merit: 0
|
|
November 02, 2018, 02:29:50 PM |
|
Hello, I am writing here for the first time
I have r7 370 2gb video cards in my farms
used to use srb miner, but lately support for old cards in it began to limp, when switching to v8, the hashrate dropped significantly, calculation errors appeared, wrote no changes to the srb miner topic
please do not drop support for old maps on your miner i have better results
r7 370 2gb - monero v7 srb 1.6.9 --495h / s
--monero v8 srb 1.6.9 --- 366h / s
jce 033b2 --- 422h / s
thank you very much for the miner for old video cards
the rest concentrated their attention on rx / vega cards where big competition forgetting about other generations
you will be able to occupy your niche in the market of miners, about which others have forgotten
|
|
|
|
|
Mike Leone
Newbie
Offline
Activity: 8
Merit: 0
|
|
November 02, 2018, 05:54:51 PM |
|
"Failed to allocate shared Large Page, using normal memory (slower). Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower)." That's a message about the CPU mining, because --auto also configures the CPU. To stay on GPU only, add parameter --no-cpuI tried and with the --no-cpu in auto mode and with the command -c config.txt Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10 " |
|
|
|
|
monote
Newbie
Offline
Activity: 26
Merit: 1
|
|
November 02, 2018, 06:32:30 PM |
|
guys! i recently got a rx550, 2gb. Any idea if i can get more than 300h/s on cn-heavy? No, 2Gb too small amount to have normal speed on cn-heavy. You can increase speed only by use overclocking and editing memory straps in bios. Yeah! I know, i have the bios modded and tried some different configurations of OC without luck... Maybe someone had good ones  Thanks man! |
|
|
|
|
matheus176
Newbie
Offline
Activity: 52
Merit: 0
|
|
November 03, 2018, 06:18:04 AM |
|
Hello i'm new into mining and i have one xeon skylake 12 cores, 24 threads, 56mb L3 cache and one xeon 10 cores, 20 threads with 56mb L3 cache too, in default settings i was able to get 1700h/s using cryptonight lite, is there any way to optimize my results? I was Reading about the multi hash but i don't know which config to use, and how much is the value for hugepages?
|
|
|
|
|
|
