[ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9

[george2019]

well i made some more testing VS gminer 1.30 and f2pool gives quite big drop of hashrate using gminer with 28.1g/sec hashrate vs only 26.8g.sec actual hashrates that bminer 14.0 has, maybe it's because this setting:

Improved the miner fidelity by 8%-10%. You will not see big local difference but you will see roughly 10% higher speed on the pool side.

here's result :

https://i.imgur.com/WNwcjkd.png

i will test it further in longer periods, it's quite interesting result, if this fidelity option really works (i'm not quite sure yet whether gminer also has it or not) i will receive higher earnings than gminer with 28g/sec hashrate, with gminer there's no rejected shares, but teamviewer works slower with gminer, it also uses around 32gb pagefile

[bakermining76]

well i made some more testing VS gminer 1.30 and f2pool gives quite big drop of hashrate using gminer with 28.1g/sec hashrate vs only 26.8g.sec actual hashrates that bminer 14.0 has, maybe it's because this setting:

Improved the miner fidelity by 8%-10%. You will not see big local difference but you will see roughly 10% higher speed on the pool side.

here's result :

https://i.imgur.com/WNwcjkd.png

i will test it further in longer periods, it's quite interesting result, if this fidelity option really works (i'm not quite sure yet whether gminer also has it or not) i will receive higher earnings than gminer with 28g/sec hashrate, with gminer there's no rejected shares, but teamviewer works slower with gminer, it also uses around 32gb pagefile

After mining GRIN for about 1 1/2 weeks with bminer, I've consistently had higher hashrates on F2pool than has been shown on the miner. I thought it might be an outlier *luck* result, but it has held true the whole time on both my 1080Rig (1080Ti x2 + 1080 x2) on GRIN-31 part of the time and GRIN-29 the rest of the time and on my P106Rig (P106-100 x6) on GRIN-29 the whole time. I've also seen that going from version 13.2 to 14.1 decreased rejects from ~1.8% to ~1.3% (again on F2pool). I've tried sparkpool and grinmint for a few days with different rigs and have had much poorer results, with sparkpool's reject rate hovering above 4.5% now (it was over 5% on v 13.2). Not sure what to make of all that except to keep using bminer on F2pool.

[george2019]

i tested gminer 1.30 and f2pool showed less average hashrate after few hours of mining, i think it's because this bminer setting:

Improved the miner fidelity by 8%-10%. You will not see big local difference but you will see roughly 10% higher speed on the pool side.
gminer doesn't uses this tweak

https://i.imgur.com/TaG86Wm.png

so bminer 14.0 has higher recorded f2pool hashrate, i will countinue using bminer at the moment it has highest recorded pool hashrate for grin c29 algo than any other miner, even if miner itself shows otherwise

[niooron]

Sent a PM about adding an option to disable NVML, its giving me trouble to run bminer in a docker container.

[QZLP]

Bminer is not showing accepted shares on the miner on my rig but it is showing I am getting shares on the pool at thegrinpool.... I have 3 different workers connected and it is hard to tell which ones are working as the pool does not list workers separately. One of the three rigs is showing accepted shares but the other two are not but they are obviously working as my G/s are higher than any one rig will make. Just wanted to let someone know as it seems like a bug.

[GustDK]

when Bminer can see the ms connection with the pool ?? @realbminer

[realbminer]

Bminer is not showing accepted shares on the miner on my rig but it is showing I am getting shares on the pool at thegrinpool.... I have 3 different workers connected and it is hard to tell which ones are working as the pool does not list workers separately. One of the three rigs is showing accepted shares but the other two are not but they are obviously working as my G/s are higher than any one rig will make. Just wanted to let someone know as it seems like a bug.

Can you please share your command?

[realbminer]

for grin I'm getting

Code:

[INFO] [2019-01-31T21:30:55+02:00] Authorized with the server                   
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x7540b6]
[WARN] [2019-01-31T21:30:57+02:00] Miner died! It will be restarted soon...     

on all my nodes with 14.1.0. Ubuntu 16.04. nvidia 415.27. Cuda 10.

it doesn't do it immediately. sometimes it runs for hours before doing this

14.0.0 was fine

Never seen this. Can you please share the command?

[realbminer]

We’re pleased to release Bminer 14.2.0.

• Experimental support for Cuckatoo31 on 1080Ti.
• Fix the regression where ETH dual mine fails to start on Windows.
• Fix the regression where ETH dual mine fails to start on Windows.
• Improve performance on mining Aeternity.
• Support tweaking the CPU usage for mining AE / Grin with the -intensity flag.

Please see https://www.bminer.me for more details.

Happy mining!

[twente-mining]

Grin31 with 1080ti version 14.2.0 give me errors

Insufficient memory 9171,7 MB available on device (#0). unable to run the solver
Miner died!

[agente]

Grin31 with 1080ti version 14.2.0 give me errors

Insufficient memory 9171,7 MB available on device (#0). unable to run the solver
Miner died!

Me too.. same error

[coinzzzman]

Grin31 with 1080ti version 14.2.0 give me errors

Insufficient memory 9171,7 MB available on device (#0). unable to run the solver
Miner died!

Me too.. same error

same for me; I tried reducing memory usage by desktop without success.  I also checked available RAM for the GPU and it was well over 10.5GB

[Juniormkl]

BMiner 14.2.0 added to https://www.minermonitoring.com/



Join our discord https://discord.gg/aGGaeqq



also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark

[sandinthebones]

• Experimental support for Cuckatoo31 on 1080Ti.

Expected hashrate?

[joaocha]

• Experimental support for Cuckatoo31 on 1080Ti.

I have tried it on grinmint with 9x1080ti rig, hashrate was ok, averaging 0.9 per card as specified, however all the shares where rejected. Is grinmint not supported yet?

On Btc.com im getting more rejected shares them accepted shares too

[FFI2013]

Is there anyway amd for beam can get some love the hashrates are lower compared to lolminer but seems that dev is lost somewhere

[chuckn3v3rsold]

Grin31 with 1080ti version 14.2.0 give me errors

Insufficient memory 9171,7 MB available on device (#0). unable to run the solver
Miner died!

Me too.. same error

same for me; I tried reducing memory usage by desktop without success.  I also checked available RAM for the GPU and it was well over 10.5GB

same here.

[cracker76]

Has anybody been able to get grin 31 working on 1080ti cards?

[bracinac]

It's working but not hashing close as it shows

[VoskCoin]

planning any support for AMD Radeon VII ?