Topic: [XMR] JCE Miner Cryptonight/forks, now with GPU! - page 18. (Read 90791 times)
JCE, please note that a fork is coming for turtlecoin: https://blog.turtlecoin.lol/archives/proof-of-work-algorithm-change/
Around 3570H/s max
Usually 3535-3540H/s
Usually 3535-3540H/s
i was asking about the instant blue hashrate provided by the miner itself.
The pool looks only for 15mns, 2Hs, 24Hs HR. In 15 mns, it can be less than 2KH/s or more than 4,5KH/s. Difficulty around 110K.
I just switched to another algo (Haven).
I just switched to another algo (Haven).
this is very consistent, but what say the instant hashrate? it should be 102% of the effective, depending on your pool aggresivity
on the b9 it was rather 103+% which is bad, but i found why. the b10 provides a lower hashrate on RX but a more consistant effective.
on the b9 it was rather 103+% which is bad, but i found why. the b10 provides a lower hashrate on RX but a more consistant effective.
Update for bittube.
Miner uptime 73:06:04 (73 hours)
Effective net hashrate 3457.39 h/s
Devices results - Shares Accepted/Ignored/Rejected - Net Hashrate
GPU 0 - 1923/1/0 - 871.81 h/s
GPU 1 - 1823/0/0 - 827.56 h/s
GPU 2 - 1878/0/0 - 854.14 h/s
GPU 3 - 1988/0/0 - 903.85 h/s
Pool says 3,45KH/s for the last 24hs.
Miner uptime 73:06:04 (73 hours)
Effective net hashrate 3457.39 h/s
Devices results - Shares Accepted/Ignored/Rejected - Net Hashrate
GPU 0 - 1923/1/0 - 871.81 h/s
GPU 1 - 1823/0/0 - 827.56 h/s
GPU 2 - 1878/0/0 - 854.14 h/s
GPU 3 - 1988/0/0 - 903.85 h/s
Pool says 3,45KH/s for the last 24hs.
I took time to test and bench, and while i could have restored the perfs of the b9, no way to get extra effective hash rate. i could fix the false positive that caused the effective to be 3% lower than theorical (instead of the normal 0.9% fee + 1% stale) but at the cost of 1% instant performance, which lead to the same final efficiency. i may find new ways to improve later, but so far on rx it's very possible srb took the current lead. i didn't try on vega.
i should release a b11 that restore the rx speed but since the b9 is still online, no urge. next version will be the cpu 0.33h
i suspend Heavy dev for now, i want to take time to apply my power optims for v8. i won't beat TeamRed but it should provide better efficiency overall.
i should release a b11 that restore the rx speed but since the b9 is still online, no urge. next version will be the cpu 0.33h
i suspend Heavy dev for now, i want to take time to apply my power optims for v8. i won't beat TeamRed but it should provide better efficiency overall.
Maybe not yet, i let it run the whole day, and while the new v8 is fine, i still got some bad shares on Heavy, looks like i need an extra fix. i advise you skip your tests for now, unless you target v8.
edit: i noted all the results after a full day of mining, and all new features are good but heavy on modern cards, probably a back regression due to the hd7000 perf restore. i got good results after 1h of mining but the 24h average is 1% lower, i need to fix that.
on hd7000 the b10 is 2% better than b9 and on Zen i got the 0.6% extra perf too. same for v8 on rx about 0.4%
if you're only targetting heavy on RX, skip b10 for now.
Yes, ok. Waiting next version with modern cards heavy fix. Thank you for your hard work! edit: i noted all the results after a full day of mining, and all new features are good but heavy on modern cards, probably a back regression due to the hd7000 perf restore. i got good results after 1h of mining but the 24h average is 1% lower, i need to fix that.
on hd7000 the b10 is 2% better than b9 and on Zen i got the 0.6% extra perf too. same for v8 on rx about 0.4%
if you're only targetting heavy on RX, skip b10 for now.
Maybe not yet, i let it run the whole day, and while the new v8 is fine, i still got some bad shares on Heavy, looks like i need an extra fix. i advise you skip your tests for now, unless you target v8.
edit: i noted all the results after a full day of mining, and all new features are good but heavy on modern cards, probably a back regression due to the hd7000 perf restore. i got good results after 1h of mining but the 24h average is 1% lower, i need to fix that.
on hd7000 the b10 is 2% better than b9 and on Zen i got the 0.6% extra perf too. same for v8 on rx about 0.4%
if you're only targetting heavy on RX, skip b10 for now.
edit: i noted all the results after a full day of mining, and all new features are good but heavy on modern cards, probably a back regression due to the hd7000 perf restore. i got good results after 1h of mining but the 24h average is 1% lower, i need to fix that.
on hd7000 the b10 is 2% better than b9 and on Zen i got the 0.6% extra perf too. same for v8 on rx about 0.4%
if you're only targetting heavy on RX, skip b10 for now.
Online is the 0.33b10 GPU
A subtle new feature is that the double-check now uses the Large Pages if possible, like the CPU miner. This is why you may see messages about large page allocated or freed even if you use the GPUs only. If large pages are not configured, no change.
The tests I did on old GPUs was Stellite and v8 and Heavy on HD7950 and HD7850. Didn't try on HD6000 yet.
This is a rare case where the CPU part of the GPU version is faster than the pure CPU one.
Of course i will backport it to a CPU release soon (will be the 0.33h)
Ok, let's test it...Quote
Fixed bad shares
As a consequence, the effective hashrate is closer to the instant one
Little optim for v8 on Zen CPU and RX GPU
Restored most of the perfs on HD7000
Warning when a non-AMD gpu is enabled
As a consequence, the effective hashrate is closer to the instant one
Little optim for v8 on Zen CPU and RX GPU
Restored most of the perfs on HD7000
Warning when a non-AMD gpu is enabled
A subtle new feature is that the double-check now uses the Large Pages if possible, like the CPU miner. This is why you may see messages about large page allocated or freed even if you use the GPUs only. If large pages are not configured, no change.
The tests I did on old GPUs was Stellite and v8 and Heavy on HD7950 and HD7850. Didn't try on HD6000 yet.
This is a rare case where the CPU part of the GPU version is faster than the pure CPU one.
Of course i will backport it to a CPU release soon (will be the 0.33h)
1st observations - speed on heavy became lower than on B9 about 10-15 h/s. And now it lower than on SRB...
Online is the 0.33b10 GPU
A subtle new feature is that the double-check now uses the Large Pages if possible, like the CPU miner. This is why you may see messages about large page allocated or freed even if you use the GPUs only. If large pages are not configured, no change.
The tests I did on old GPUs was Stellite and v8 and Heavy on HD7950 and HD7850. Didn't try on HD6000 yet.
This is a rare case where the CPU part of the GPU version is faster than the pure CPU one.
Of course i will backport it to a CPU release soon (will be the 0.33h)
Quote
Fixed bad shares
As a consequence, the effective hashrate is closer to the instant one
Little optim for v8 on Zen CPU and RX GPU
Restored most of the perfs on HD7000
Warning when a non-AMD gpu is enabled
As a consequence, the effective hashrate is closer to the instant one
Little optim for v8 on Zen CPU and RX GPU
Restored most of the perfs on HD7000
Warning when a non-AMD gpu is enabled
A subtle new feature is that the double-check now uses the Large Pages if possible, like the CPU miner. This is why you may see messages about large page allocated or freed even if you use the GPUs only. If large pages are not configured, no change.
The tests I did on old GPUs was Stellite and v8 and Heavy on HD7950 and HD7850. Didn't try on HD6000 yet.
This is a rare case where the CPU part of the GPU version is faster than the pure CPU one.
Of course i will backport it to a CPU release soon (will be the 0.33h)
I'm disconnect my R9 270X 4Gb from rig. No profit from it. Electrisity cost too high. My 270X gives 480 h/s on heavy about 100-110 Watt, 535 h/s on v8 about 125-130Watt. No profit.
What may happen is that i release a v8 that is faster than TeamRed with decent power consumption, ending to a good efficiency.
If you target low power before all, really, use TeamRed, it's just perfect for that, if you have a RX+. On older cards, so far i'm quite the last dev to maintain support for them.
TeamRed and Cast never supported.
SRB gave up old cards
Claymore dev is stopped.
remains the open source miners but on old cards i'm clearly faster, even fees deduced. Note that i need to fix some recent speed regressions i did due to how i rushed the b9.
Arguments for stopping and not restarting the miner:
1. When a GPU crashes, restarting the miner almost never wake it up, it often just crash the whole PC
2. If it was caused by an hardware failure (PSU, fan...) it's a lot safier, and i always give priority to safety.
3. The b9+ has such a stable hashrate that the watchdog is a lot less needed
4. Nothing prevents you to reboot it with a 3-lines batch:
autorestart.bat
where start.bat is the normal batch you use to start JCE, the one from the package (recommended, just edit the wallet/pool examples) or a custom one.
I know some other dev like Claymore allowed hardware tweaks (voltage...) and auto-restart by default, but i explicitely refuse that, for safety. Safety first.
If you target low power before all, really, use TeamRed, it's just perfect for that, if you have a RX+. On older cards, so far i'm quite the last dev to maintain support for them.
TeamRed and Cast never supported.
SRB gave up old cards
Claymore dev is stopped.
remains the open source miners but on old cards i'm clearly faster, even fees deduced. Note that i need to fix some recent speed regressions i did due to how i rushed the b9.
Quote
Why
Am about to try this miner and was reading the parameter file.
There is a --watchdog that stops the miner is there is not activity or H/R under a threshold. After the miner shut down does it start over again on its own, something like a reboot, or do I need to manually start it again ?
Am about to try this miner and was reading the parameter file.
There is a --watchdog that stops the miner is there is not activity or H/R under a threshold. After the miner shut down does it start over again on its own, something like a reboot, or do I need to manually start it again ?
Arguments for stopping and not restarting the miner:
1. When a GPU crashes, restarting the miner almost never wake it up, it often just crash the whole PC
2. If it was caused by an hardware failure (PSU, fan...) it's a lot safier, and i always give priority to safety.
3. The b9+ has such a stable hashrate that the watchdog is a lot less needed
4. Nothing prevents you to reboot it with a 3-lines batch:
autorestart.bat
Code:
:Begin
call start.bat
goto :Begin
where start.bat is the normal batch you use to start JCE, the one from the package (recommended, just edit the wallet/pool examples) or a custom one.
I know some other dev like Claymore allowed hardware tweaks (voltage...) and auto-restart by default, but i explicitely refuse that, for safety. Safety first.
Thanks, in fact it is strange that the pool reports a higher number, my effective net is supposed to be equal to the pool report. It's as strange to see it above than below. It already deduces bad shares, stale and fees.
I'm preparing a version with a better pool-side effective hashrate compared to the instant blue one (even if it looks like it is already >100%
) and with some boost for v8 on the CPU part too, for Zen, measured +0.6%
I fixed the remaining bad shares on Heavy that dates back from the b-x versions.
There will be boost on v8 for RX too.
I'm preparing a version with a better pool-side effective hashrate compared to the instant blue one (even if it looks like it is already >100%
) and with some boost for v8 on the CPU part too, for Zen, measured +0.6%I fixed the remaining bad shares on Heavy that dates back from the b-x versions.
There will be boost on v8 for RX too.
I'd prefer a lower power usage. I won't mine V8 because it's too costly to mine.
Thanks, in fact it is strange that the pool reports a higher number, my effective net is supposed to be equal to the pool report. It's as strange to see it above than below. It already deduces bad shares, stale and fees.
I'm preparing a version with a better pool-side effective hashrate compared to the instant blue one (even if it looks like it is already >100%) and with some boost for v8 on the CPU part too, for Zen, measured +0.6%
I fixed the remaining bad shares on Heavy that dates back from the b-x versions.
There will be boost on v8 for RX too.
I'm preparing a version with a better pool-side effective hashrate compared to the instant blue one (even if it looks like it is already >100%
) and with some boost for v8 on the CPU part too, for Zen, measured +0.6%I fixed the remaining bad shares on Heavy that dates back from the b-x versions.
There will be boost on v8 for RX too.
I'd prefer a lower power usage. I won't mine V8 because it's too costly to mine.
Why
Am about to try this miner and was reading the parameter file.
There is a --watchdog that stops the miner is there is not activity or H/R under a threshold. After the miner shut down does it start over again on its own, something like a reboot, or do I need to manually start it again ?
Am about to try this miner and was reading the parameter file.
There is a --watchdog that stops the miner is there is not activity or H/R under a threshold. After the miner shut down does it start over again on its own, something like a reboot, or do I need to manually start it again ?
Thanks, in fact it is strange that the pool reports a higher number, my effective net is supposed to be equal to the pool report. It's as strange to see it above than below. It already deduces bad shares, stale and fees.
I'm preparing a version with a better pool-side effective hashrate compared to the instant blue one (even if it looks like it is already >100%) and with some boost for v8 on the CPU part too, for Zen, measured +0.6%
I fixed the remaining bad shares on Heavy that dates back from the b-x versions.
There will be boost on v8 for RX too.
I'm preparing a version with a better pool-side effective hashrate compared to the instant blue one (even if it looks like it is already >100%
) and with some boost for v8 on the CPU part too, for Zen, measured +0.6%I fixed the remaining bad shares on Heavy that dates back from the b-x versions.
There will be boost on v8 for RX too.
40 hours and counting mining BITTUBE with 4 RX 574.
JCE says:
Miner uptime 40:27:11
Hashrate GPU Thread 0: 462.68 h/s
Hashrate GPU Thread 1: 462.68 h/s - Total GPU 0: 925.35 h/s
Hashrate GPU Thread 2: 442.32 h/s
Hashrate GPU Thread 3: 442.01 h/s - Total GPU 1: 884.32 h/s
Hashrate GPU Thread 4: 454.64 h/s
Hashrate GPU Thread 5: 454.77 h/s - Total GPU 2: 909.40 h/s
Hashrate GPU Thread 6: 467.90 h/s
Hashrate GPU Thread 7: 467.57 h/s - Total GPU 3: 935.47 h/s
Total: 3654.53 h/s - Max: 3668.63 h/s
Effective net hashrate 3493.57 h/s
The pool says:
Hashrate 15m: 4.29 kH/sec
2h: 3.87 kH/sec
24h: 3.57 kH/sec
JCE says:
Miner uptime 40:27:11
Hashrate GPU Thread 0: 462.68 h/s
Hashrate GPU Thread 1: 462.68 h/s - Total GPU 0: 925.35 h/s
Hashrate GPU Thread 2: 442.32 h/s
Hashrate GPU Thread 3: 442.01 h/s - Total GPU 1: 884.32 h/s
Hashrate GPU Thread 4: 454.64 h/s
Hashrate GPU Thread 5: 454.77 h/s - Total GPU 2: 909.40 h/s
Hashrate GPU Thread 6: 467.90 h/s
Hashrate GPU Thread 7: 467.57 h/s - Total GPU 3: 935.47 h/s
Total: 3654.53 h/s - Max: 3668.63 h/s
Effective net hashrate 3493.57 h/s
The pool says:
Hashrate 15m: 4.29 kH/sec
2h: 3.87 kH/sec
24h: 3.57 kH/sec
Tested heavy algo on SRB last version... Hmmm - it's very good! Speed stable as rock! On nicehash 20 hours of tests - speed on miner 2315 h/s, speed from pool - 2,3 kH/s. And for 20 hours only 2 errors - invalid nonce... Impressive...
JCE, waiting your next version to test... Please make something to increase effective hashrate...
JCE, waiting your next version to test... Please make something to increase effective hashrate...
hi guys, please give good timings for micron,
777000000000000022AA1C0073626C41B0551016BA0D260B0060060004061420EA8940AA0300000 01914292EB22E3B16-on these timings max 950 on heavy algo rx578....
Huh
777000000000000022AA1C0073626C41B0551016BA0D260B0060060004061420EA8940AA0300000 01914292EB22E3B16-on these timings max 950 on heavy algo rx578....
Huh
Jump to: