0.33g CPU Linux re-release
Quote
Fixed JSON timer
FreeHaven coin correctly defaults to FreeHaven fork
FreeHaven coin correctly defaults to FreeHaven fork
then I go back to GPU sync fixes.
Topic: [XMR] JCE Miner Cryptonight/forks, now with GPU! - page 24. (Read 90822 times)
a new version? sure, here's the
0.33g CPU Linux re-release
then I go back to GPU sync fixes.
0.33g CPU Linux re-release
then I go back to GPU sync fixes.
JCE, any news about new version? Heavy algo speed stabilization and lowering power draw on v8 is very needed!
Здpaвcтвyйтe. Бyдeт paбoтaть нa hd7850 c 1гб
нa v7 370-400h кoпaли.
Пoчти тaкжe дoлжнa кoпaть и нa v8. нa v7 370-400h кoпaли. Mining HAVEN (heavy) for >11H
4 RX570 4G with bios mod.
Display GPU: 1250C/2040M. Intensity set to 272.
Other GPUs: 1230C/2100M; 1240C/2020M; 1230C/2030M. Intensity set to 464.
Max HR: 3196H/s
Reported HR: 3290H/s (yep, more than the theoratical perf).
Share difficulty set by the pool: 169K
HR at the pool:
- 2 hours: 3,38KH/s
- 24 hours: 1,58KH/s. That's consistent to the fact I've been mining for less than 12Hs
24 hours mining with same settings:4 RX570 4G with bios mod.
Display GPU: 1250C/2040M. Intensity set to 272.
Other GPUs: 1230C/2100M; 1240C/2020M; 1230C/2030M. Intensity set to 464.
Max HR: 3196H/s
Reported HR: 3290H/s (yep, more than the theoratical perf).
Share difficulty set by the pool: 169K
HR at the pool:
- 2 hours: 3,38KH/s
- 24 hours: 1,58KH/s. That's consistent to the fact I've been mining for less than 12Hs
- Max HR is 3234,55H/s
- Reported average HR by the miner is 3150H/s
- Pool says 3150 H/s
Power draw at the wall: 405-410W.
Quote
yep, more than the theoratical perf
On a 11h run with a high diff, this is very normal.Quote
with nearly 40% bad shares even if not moded
yeah my hybrid on the b-xyz is pretty bad on Hawaii, i want to add an option in next GPU version to enable or not the new hybrid. Disable will typically lower the peak hashrate by 1% but provide zero bad shares. 
Mining heavy/haven:
280x give stable 430 h/s.
390 are very unstable. Cards report between 500 and 800 whatever intensity I chose. Most cards gravitate towards 640 h/s, but I have some that can't go beyond 540 h/s with nearly 40% bad shares even if not moded. For comparison with xmrig all 390 cards are very stable with 660 h/s and none bad shares. On the other hand, 280x are not even working with xmrig.
280x give stable 430 h/s.
390 are very unstable. Cards report between 500 and 800 whatever intensity I chose. Most cards gravitate towards 640 h/s, but I have some that can't go beyond 540 h/s with nearly 40% bad shares even if not moded. For comparison with xmrig all 390 cards are very stable with 660 h/s and none bad shares. On the other hand, 280x are not even working with xmrig.
Mining HAVEN (heavy) for >11H
4 RX570 4G with bios mod.
Display GPU: 1250C/2040M. Intensity set to 272.
Other GPUs: 1230C/2100M; 1240C/2020M; 1230C/2030M. Intensity set to 464.
Max HR: 3196H/s
Reported HR: 3290H/s (yep, more than the theoratical perf).
Share difficulty set by the pool: 169K
HR at the pool:
- 2 hours: 3,38KH/s
- 24 hours: 1,58KH/s. That's consistent to the fact I've been mining for less than 12Hs
4 RX570 4G with bios mod.
Display GPU: 1250C/2040M. Intensity set to 272.
Other GPUs: 1230C/2100M; 1240C/2020M; 1230C/2030M. Intensity set to 464.
Max HR: 3196H/s
Reported HR: 3290H/s (yep, more than the theoratical perf).
Share difficulty set by the pool: 169K
HR at the pool:
- 2 hours: 3,38KH/s
- 24 hours: 1,58KH/s. That's consistent to the fact I've been mining for less than 12Hs
Hey JCE
I figured out a manual fix to get those rx 580 cards to hash at max speeds on Heavy and be stable, any time i see one that has lost the max speed, i pause/unpause 4 times each (8 button pushes) in quick succession and the card comes back to maximum speed. May be something like this can be coded into the miner?
I figured out a manual fix to get those rx 580 cards to hash at max speeds on Heavy and be stable, any time i see one that has lost the max speed, i pause/unpause 4 times each (8 button pushes) in quick succession and the card comes back to maximum speed. May be something like this can be coded into the miner?
Yeah, I've been doing this since 0.33B5 and it works on all my rigs, except sometimes it takes more than 4x pause/un-pause. This also works on SRB miner, but takes a bit more time to achieve.
In the end you get all the card hashing at max speed this way.
I need to make it the normal way, not needing a manual tweak such this one. I knew my opencl was good, but the sync is glitchy, and the hybrid didn't help.
Online is the 0.33g CPU Windows re-released undercover with the said regression fixed.
* With normal mode, kill the parent, the child attrib suicides, and vice-versa.
* With --elevate, four processes are started, two jce and two attrib, one of each normal, one of each elevated. Kill any, the three other suicide.
* With --elevate-and-quit, the parent suicide at the beginning, hence the name, so the attrib remains in all cases, on purpose. Don't use this mode if you want to grab the parent process-id to kill JCE from an external tool.
Online is the 0.33g CPU Windows re-released undercover with the said regression fixed.
* With normal mode, kill the parent, the child attrib suicides, and vice-versa.
* With --elevate, four processes are started, two jce and two attrib, one of each normal, one of each elevated. Kill any, the three other suicide.
* With --elevate-and-quit, the parent suicide at the beginning, hence the name, so the attrib remains in all cases, on purpose. Don't use this mode if you want to grab the parent process-id to kill JCE from an external tool.
That's about HD6990 but that's a dual HD6970, the results on a HD6950 should be around 240.
Thanks.Method to restore maximum heavy algo speed after speed drop often works. Just quick pressing 8 times number of GPU on which speed droped can restore it! It's strange that quick pause\unpause GPU 4 times in row can do that...
I've one remaining HD6950 but not on a rig, on a cheap PC whose PSU cannot afford real mining so I tested it works, but not for speed.
I could unplug it and put it on a real rig to do real tests but not immediately, lack of time.
The minning speed provided come from a ticket in the Github support.
I could unplug it and put it on a real rig to do real tests but not immediately, lack of time.
The minning speed provided come from a ticket in the Github support.
Quote
Ok I tested the miner now, best results I achieved is 270 h/s per core on 6990.
So that is 2x 270 h/s = ~ 540 h/s total for 6990 (which is 2 gpu cores of 6970s in it)
Settings used : 32 worksize and 864 intensity.
That's about HD6990 but that's a dual HD6970, the results on a HD6950 should be around 240. So that is 2x 270 h/s = ~ 540 h/s total for 6990 (which is 2 gpu cores of 6970s in it)
Settings used : 32 worksize and 864 intensity.
Could someone share proper settings and estimated h/s for 5704GB -580 8GB for heaven algo?
Дык пoэтoмy я и cпpaшивaю, ecть ли cмыcл cтaвить win 10 и иcпoльзoвaть Baш мaйнep? У мeня 250 h/s, нa Baшeм бoльшe?
He знaю. Boзмoжнo и нeт. Taм вoн y чeлoвeкa бoльшe 113 нe пoлyчaeтcя нa 6950... Haдo выяcнить, cкoлькo JCE нa 6950 дoлжeн выдaвaть...JCE, how much h/s your miner must give on HD6950 ? Did you test this card?
Дык пoэтoмy я и cпpaшивaю, ecть ли cмыcл cтaвить win 10 и иcпoльзoвaть Baш мaйнep? У мeня 250 h/s, нa Baшeм бoльшe?
Minimum is Windows 8.1 x64 for JCE GPU
For CPU, that's ok down to Vista32
For CPU, that's ok down to Vista32
У мeня msi HD6950 2Gb, win 7, дpaйвepa 13.12, выдaeт нa xmrig-amd-2.8.6 250 h/s. Hacтpoйки: 1 пoтoк, worksize 64, multi_hash 832.
Cкoлькo дoлжнa дaвaть h/s нa мaйнepe JCE? Ecть ли cмыcл cтaвить Win 10?, yж oчeнь мнoгo нyжнoгo xлaмa и кoшeлькoв нa этoм pигe....
Boss_One пoпpoбyйтe дpaйвepa 13.12
Cкoлькo дoлжнa дaвaть h/s нa мaйнepe JCE? Ecть ли cмыcл cтaвить Win 10?, yж oчeнь мнoгo нyжнoгo xлaмa и кoшeлькoв нa этoм pигe....
Boss_One пoпpoбyйтe дpaйвepa 13.12
I rushed the 33g to provide the MoneroOcean new feature, and it shows...
so far three regressions/bugs
* Stak JSON timers
* Shadow sub-process suicide
* FreeHaven wallets defaults to... Monero algo
I'm rebuilding it and will re-release.
so far three regressions/bugs
* Stak JSON timers
* Shadow sub-process suicide
* FreeHaven wallets defaults to... Monero algo
I'm rebuilding it and will re-release.
Quote
Looks like for OpenCL this card have less than 2Gb vmemory...
Did he set the env variables?Code:
set GPU_MAX_HEAP_SIZE=100
set GPU_USE_SYNC_OBJECTS=1
set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
set GPU_USE_SYNC_OBJECTS=1
set GPU_MAX_ALLOC_PERCENT=100
set GPU_SINGLE_ALLOC_PERCENT=100
It's strange... Can you provide screenshots of 1st and 2nd tabs GPU-Z? And GPU Caps Viewer - OpenCL tab...
Looks like for OpenCL this card have less than 2Gb vmemory...
try this set:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 240},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 240},
],
wait about 10 minutes to look real speed. At start speed maybe low.
Looks like for OpenCL this card have less than 2Gb vmemory...
try this set:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 240},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 240},
],
wait about 10 minutes to look real speed. At start speed maybe low.
Try to use double threads this way:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 224},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 224},
],
also try this config:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 464},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 464},
],
or
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 448},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 448},
],
or
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 432},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 432},
],
Double thread 224 => 113 h/s same as 1 Thread
Double thread 464 => PC Freez
Double thread 448 => Driver crash
Double thread 432 => Driver crash
What's wrong ?
(same result on a VTX HD6950 and Gigabyte HD6950)i've already try 2 thread before asking on forum, same result as 1 thread ? Is it normal with this card ?
Yes i'm on W8.1
My 6950 got 2Gb ram
I'm mining V8 cryptonight the lastest fork ...
So, it's hash a little now, my config parameters sucks.
I'm testing on 33B6 and with this "jce_cn_gpu_miner64.exe Experimental boost ~2% for HD6000/7000"
I've try a lot of parameters, but get not more than 100/113 h/s
It's crash when i up "multi_hash" value more than 240
That's the best result i can get with this config
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash":240},
],
if i try Worksize 16/32 i can't UP than 240 thread.
Did u have some values i can try ? because i've try a lot of combination but can't reach more hashrate, driver crash.
i didn't understand whats that 2 values (alpha" : 64, "beta" : 8 ) ?
The most curious it was, if i didn't OC my card like @910/1250 driver crash instantanetly when i start miner.
in 800/1250 or 830/1250 driver crash. With all same values in config.txt . Wtf hell !!!
I've try on each card on different PC (don't have a rig) 3 different PC.
Thx for helping.
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 224},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 224},
],
also try this config:
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 464},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 464},
],
or
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 448},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 448},
],
or
"gpu_threads_conf" :
[
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 432},
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "index" : 0, "multi_hash": 432},
],
Jump to: