[ANN][MTC] GPU Miner for Metiscoin - 35% FASTER on R9 280x

[terry00285]

how can I change the thread number on GPU?

[terry00285]

I have 4 280X cards.How can I set for letting  them work at same time.And the speed only 2300k/s.Can I change number of threads  to improve the speed and how  can I set number of threads?another question is why its speed will  direct gonging down to 60k/s and ask me Whether to exit the batch after  running somrtime？

[dezzuria]

I have 4 280X cards.How can I set for letting  them work at same time.And the speed only 2300k/s.Can I change number of threads  to improve the speed and how  can I set number of threads?another question is why its speed will  direct gonging down to 60k/s and ask me Whether to exit the batch after  running somrtime？

You can start several devices by setting "-d 0,1" in your .bat file (0,1 would be OpenCL device indexes which is listed when you start the miner, yours might be different).
The decreasing hash rate is not to worry about, it´s simply a 32bit counter wrapping (reaching it´s maximum value and starts over from 0) it is only visual and won´t affect actual performance.

Well now that I actually helped someone for a change I would like to give some feedback to the developer. Currently if/when the miner lose connection with the pool there are never any attempts to connect back again, it would be awesome to have a reconnect feature so we don´t lose any hash time. I know I'm a lazy bastard asking you to implement this rather than doing it myself but it is probably a quick matter for someone familiar with the code

Also, thanks a lot for your efforts with this miner.

[girino]

Well now that I actually helped someone for a change I would like to give some feedback to the developer. Currently if/when the miner lose connection with the pool there are never any attempts to connect back again, it would be awesome to have a reconnect feature so we don´t lose any hash time. I know I'm a lazy bastard asking you to implement this rather than doing it myself but it is probably a quick matter for someone familiar with the code

Also, thanks a lot for your efforts with this miner.

This is quite strange since i didn't mess with the networking code from ypool, but you're not the first to point it out. I'll look into this today (the 32 bit counter is already fixed in the code and in the linux and mac binaries, just the windows binaries still have the bug).

Thanks for the support.

[girino]

NEW RELEASE

Build 5, fixes the following bugs:

- bogus hash count after half on hour or so in fast GPUs. Now it report the right hashrate for several years.
- Not reconnecting after disconnection. Now it waits 45 secs after every disconnect and tries again.

New Features:

- counts invalid and valid shares separately, so it is easier to spot problems.

Todo:

- several AMD optimizations are on the pipeline, but they were not yet mature (too many invalid shares) so they were NOT included in this version.

Download binaries and source from the same old place. OSX binaries not ready yet, only linux and Windows available.

Binaries link: https://www.dropbox.com/sh/2wv2awwgebpdo0m/STzOU5tlXa

Source code: https://github.com/girino/xptMiner

Thanks, and enjoy the new version.

[girino]

Any idea why the miner seems to just stop finding shares after a while? I noticed the kh/s going down over time but it was still finding shares pretty quickly, but this morning it was reporting 0 kh/s and not finding shares. Win 7, R9 290 if that helps.

never heard of it stopping finding shares. isn't it a network problem or something? maybe the pool was down.

about the speed, the original xptminer from ypool used a 32 bit counter for hashes, but it overflows quite quickly with gpu hashing speed (30 minutes to 1 hour, depending on the gpu). so reported speeds after the first half an hour or so are just bogus. I'll release a fix for that later today. (code is already fixed, but i didn't create the binaries yet).

Found this bug, it is fixed in Build 5!

[Tons0fun]

Awesome, keep the updates coming. I noticed that you can include the CPU in the list of devices to be used with your miner, is this efficient?

[girino]

Awesome, keep the updates coming. I noticed that you can include the CPU in the list of devices to be used with your miner, is this efficient?

Not at all. It will use opencl on the CPU, and you will get at most half the hash rate you get with a decent CPU miner.

[terry00285]

I want to know how to set number of thread? My 280X can suport at least 11 threads, but now I see only 1 thread running.

[Aalesund]

Great Job!  

PowerColor R9 290X OC
1 mining thread

[zerodegree79]

Doesn't work for me, starts initializing and then nothings happening. I'm on Win 8.1 64bit with a Radeon HD6770

Code:

Exception: STATUS_ACCESS_VIOLATION at rip=001004293ED
rax=000000000023A838 rbx=0000000000000002 rcx=000000000023A930
rdx=0000000000000000 rsi=000000000023A930 rdi=0000000000000002
r8 =0000000000000000 r9 =0000000000000000 r10=0000000000240000
r11=0000000100429E34 r12=00000006000574C0 r13=0000000000000000
r14=0000000000000000 r15=000000000023AB26
rbp=000000000023A880 rsp=000000000023A800
program=C:\Users\Admin\Desktop\GPU-xptMiner-Win64-Cygwin-build5\xptminer.exe, pid 4644, thread main
cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame        Function    Args
0000023A880  001004293ED (00000000002, 0000023A6CC, 00000000463, 00600057060)
0000023AA20  0010042537C (00000000002, 0000023A6CC, 00180137010, 00000000081)
0000023AA20  0010042F064 (00180067001, 00000000000, 0020000002F, 00000000000)
0000023AB80  0018004836B (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  001800461CB (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  0018004638F (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  0010042CC11 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  00100401010 (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  7FFCE39215CD (00000000000, 00000000000, 00000000000, 00000000000)
00000000000  7FFCE54B43D1 (00000000000, 00000000000, 00000000000, 00000000000)
End of stack trace

[jk_14]

NEW RELEASE

Build 5, fixes the following bugs:

New Features:

- counts invalid and valid shares separately, so it is easier to spot problems.

Todo:

- several AMD optimizations are on the pipeline, but they were not yet mature (too many invalid shares) so they were NOT included in this version.

My test rather unsuccessfull:

root@bamt-miner:~/xptMiner-master# ./xptminer -o ypool.net -u xxx.w11 -p xxx -d 0 | grep total
kHash/s: 10747.90 Shares total: 300 (Valid: 0, Invalid: 2)
kHash/s: 10846.21 Shares total: 651 (Valid: 0, Invalid: 2)
kHash/s: 10857.13 Shares total: 986 (Valid: 0, Invalid: 4)
kHash/s: 10878.98 Shares total: 1294 (Valid: 0, Invalid: 6)
kHash/s: 10865.87 Shares total: 1589 (Valid: 0, Invalid: 5)
kHash/s: 10857.13 Shares total: 1964 (Valid: 0, Invalid: 7)
kHash/s: 10869.61 Shares total: 2322 (Valid: 0, Invalid: 1)
kHash/s: 10878.98 Shares total: 2643 (Valid: 0, Invalid: 3)
kHash/s: 10886.26 Shares total: 2955 (Valid: 0, Invalid: 73)
kHash/s: 10892.08 Shares total: 3281 (Valid: 0, Invalid: 4)
kHash/s: 10896.85 Shares total: 3623 (Valid: 0, Invalid: 115)
^C
root@bamt-miner:~/xptMiner-master#

card: Gigabyte 7950 WF3

[girino]

NEW RELEASE

Build 5, fixes the following bugs:

New Features:

- counts invalid and valid shares separately, so it is easier to spot problems.

Todo:

- several AMD optimizations are on the pipeline, but they were not yet mature (too many invalid shares) so they were NOT included in this version.

My test rather unsuccessfull:

root@bamt-miner:~/xptMiner-master# ./xptminer -o ypool.net -u xxx.w11 -p xxx -d 0 | grep total
kHash/s: 10747.90 Shares total: 300 (Valid: 0, Invalid: 2)
kHash/s: 10846.21 Shares total: 651 (Valid: 0, Invalid: 2)
kHash/s: 10857.13 Shares total: 986 (Valid: 0, Invalid: 4)
kHash/s: 10878.98 Shares total: 1294 (Valid: 0, Invalid: 6)
kHash/s: 10865.87 Shares total: 1589 (Valid: 0, Invalid: 5)
kHash/s: 10857.13 Shares total: 1964 (Valid: 0, Invalid: 7)
kHash/s: 10869.61 Shares total: 2322 (Valid: 0, Invalid: 1)
kHash/s: 10878.98 Shares total: 2643 (Valid: 0, Invalid: 3)
kHash/s: 10886.26 Shares total: 2955 (Valid: 0, Invalid: 73)
kHash/s: 10892.08 Shares total: 3281 (Valid: 0, Invalid: 4)
kHash/s: 10896.85 Shares total: 3623 (Valid: 0, Invalid: 115)
^C
root@bamt-miner:~/xptMiner-master#

card: Gigabyte 7950 WF3

Did you build it from code or did you use one of the binaries? The code might be buggy since I was doing some tests in it. I'll check what went wrong.

[jk_14]

NEW RELEASE

Build 5, fixes the following bugs:

New Features:

- counts invalid and valid shares separately, so it is easier to spot problems.

Todo:

- several AMD optimizations are on the pipeline, but they were not yet mature (too many invalid shares) so they were NOT included in this version.

My test rather unsuccessfull:

root@bamt-miner:~/xptMiner-master# ./xptminer -o ypool.net -u xxx.w11 -p xxx -d 0 | grep total
kHash/s: 10747.90 Shares total: 300 (Valid: 0, Invalid: 2)
kHash/s: 10846.21 Shares total: 651 (Valid: 0, Invalid: 2)
kHash/s: 10857.13 Shares total: 986 (Valid: 0, Invalid: 4)
kHash/s: 10878.98 Shares total: 1294 (Valid: 0, Invalid: 6)
kHash/s: 10865.87 Shares total: 1589 (Valid: 0, Invalid: 5)
kHash/s: 10857.13 Shares total: 1964 (Valid: 0, Invalid: 7)
kHash/s: 10869.61 Shares total: 2322 (Valid: 0, Invalid: 1)
kHash/s: 10878.98 Shares total: 2643 (Valid: 0, Invalid: 3)
kHash/s: 10886.26 Shares total: 2955 (Valid: 0, Invalid: 73)
kHash/s: 10892.08 Shares total: 3281 (Valid: 0, Invalid: 4)
kHash/s: 10896.85 Shares total: 3623 (Valid: 0, Invalid: 115)
^C
root@bamt-miner:~/xptMiner-master#

card: Gigabyte 7950 WF3

Did you build it from code or did you use one of the binaries? The code might be buggy since I was doing some tests in it. I'll check what went wrong.

Compiled from code.

[girino]

Compiled from code.

strange. Couldn't reproduce it here. But this code is outdated, you should use gigawatt's version which has some optimizations i didn't port back yet. (he used vector types for shavite and metis/fugue, and gained some 20% speed).

his code is at: https://github.com/llamasoft/xptMiner

[jk_14]

Compiled from code.

strange. Couldn't reproduce it here. But this code is outdated, you should use gigawatt's version which has some optimizations i didn't port back yet. (he used vector types for shavite and metis/fugue, and gained some 20% speed).

his code is at: https://github.com/llamasoft/xptMiner

In the same time I have tried gigawatt's version also - and with the same results.
Maybe it's due to BAMT 1.2 used (32 bits OS)

[girino]

Compiled from code.

strange. Couldn't reproduce it here. But this code is outdated, you should use gigawatt's version which has some optimizations i didn't port back yet. (he used vector types for shavite and metis/fugue, and gained some 20% speed).

his code is at: https://github.com/llamasoft/xptMiner

In the same time I have tried gigawatt's version also - and with the same results.
Maybe it's due to BAMT 1.2 used (32 bits OS)

Hum, probably yes! Even the original networking code from ypool was not meant for 32 bits. This might be solvable, but would take me some time...

[lovecoin99]

how to set params to change the gpu-clock and gpu-memclock?

xptminer --gpu-engine ?  it doesn't work

[girino]

how to set params to change the gpu-clock and gpu-memclock?

xptminer --gpu-engine ?  it doesn't work

This miner doesn't change the GPU clock. You need to use and external tool for that.

[lovecoin99]

do you have some  recommandation? i don't know  which one can  support to change multi-displaycard gpu-clock.