Author

Topic: [ANN]Bminer: a fast Equihash/Ethash/Cuckaroo29z miner for AMD/NVIDIA GPUs 16.4.9 - page 130. (Read 148347 times)

full member
Activity: 210
Merit: 100
after all this posts

i think it fair to say that Bminer is n't the prefer one to mining Equihash VS DSTM

Right?

After weeks of switching mining software. I now prefer Bminer.

newbie
Activity: 176
Merit: 0
dstm 0.5.8:    https://zcash.flypool.org/miners/t1aoQJwvJqYT32xHVpYezWBxKuxPSwaJB1h
bminer 5.3.0:  https://zcash.flypool.org/miners/t1dU7Gve41A3b4mxL7a3oVAnBLsF9kMgDgA


0.00540 ZEC DSTM vs 0.00543 ZEC Bminer

Total immanature+balance

Bminer a bit better on 0.55% Wink))

What cards are used for compare? (x1 1070) vs (x1 1070) ? what average speed im miner windows?
newbie
Activity: 17
Merit: 0
after all this posts

i think it fair to say that Bminer is n't the prefer one to mining Equihash VS DSTM

Right?
full member
Activity: 420
Merit: 184
Okay, comparison #3 started about 20 minutes ago concurrently mining ZEC on Flypool using a fixed difficulty of 10000 (by using the switch "-p 10000").

If you like watching paint dry then you will surely love to check on the status of the miners:

dstm: https://zcash.flypool.org/miners/t1aoQJwvJqYT32xHVpYezWBxKuxPSwaJB1h
bminer: https://zcash.flypool.org/miners/t1dU7Gve41A3b4mxL7a3oVAnBLsF9kMgDgA

I created these two addresses just for this test so they are starting from 0.
dstm catches up. After beeing some steps behind its now close up.

Yes, I've noticed that too each time I've done this test. Bminer starts off strong but then settles down after a few hours, while dstm seems to take a few hours to ramp up to speed.
full member
Activity: 420
Merit: 184
Just a thought... What if one card performs better than the other? (Silicon lottery). Will you interchange miners for those cards on your next experiment?

I did do that when I ran a Neoscrypt miner test because one of the miners can't tolerate nearly as much overclocking, but for this test what I did was run one of the miners on both machines for a few minutes then tweak the MSI AB settings so that reported hashrate was the same for that miner regardless of which machine it ran on.

*If* we can all agree on a *practical* test methodology here (ie - one that doesn't involve me buying lots more GPUs at 2x MSRP) and the difference in earnings/shares/whatever is less than 1% after 24 hours then for the next iteration I will flip the machines the miners are running on at the 12 hour mark so that any remaining difference in GPU speed will get cancelled out.

But like I said, we need to be realistic about test conditions here. I don't have a mining farm, but I do have a willingness to test in as scientific a manner as possible and that seems to be strangely absent here.
full member
Activity: 420
Merit: 184
What you just experienced is the "lovely" PPLNS payout scheme (each block is different in length and each miner gets different shares in) ... like I said, you really should stop looking at payouts - when doing such short term tests, and with such low hashrates.

I'm pretty sure I understand how PPLNS works: you get credited for your last n shares, where n is fixed but the time this window lasts varies depending on the average time to find a block. If a pool consistently finds a block every few minutes (less than 5, let's say) and the share difficulty is fixed, then there shouldn't be more than a +/- 0.5% difference in earnings between two separate but identical miners. If I understand this incorrectly please, please correct me because all of my tests depend on this rather than counting shares because the latter is not possible/practical at many pools and I want to use a testing methodology that is consistent whether I am evaluating Neoscrypt miners or Ethash, etc. For example, on Flypool it looks like I have to total up all the blue bars then subtract the orange bars then normalize my share difficulty to 1000 (e.g. - if I set 10000 then I need to divide the share count in the bars by 10, as I got 1/10th the shares which are 10x more valuable).

EDIT: 10k difficulty is too high for a single card ... you'd introduc more variability like this. You want frequent shares, but not too frequent. Lower diff such that the average share submission time you see reported by the miner is around 5 seconds if you have a good ping to flypool (< 50 ms) or 10 seconds if your ping to flypool is closer to 100 ms

Ping time is 16ms average, which is the best of any pool I've used. I aim for under 100ms, but I've even had decent results with Zergpool and my ping time to their server is 147ms average (I'm in Florida, they're in Latvia).

Difficulty of 10k is just about right for 550 Sols/s if one is not conducting a mining test, but I agree it should be lower. The thing is, I found a post on the Zcash forum by someone who was having trouble setting difficulty on Flypool, saying that it kept resetting to 8k no matter what, and someone else replied that this was because the minimum had been increased to 8k even though the website still says it is 2k. See here: https://forum.z.cash/t/zcash-flypool-difficulty/14147/8. Since I can't change Flypool's rules and I can't buy more GPUs even if I were willing to sell my non-existent first born child this appears to be the best I can do right now.
jr. member
Activity: 30
Merit: 1
Okay, comparison #3 started about 20 minutes ago concurrently mining ZEC on Flypool using a fixed difficulty of 10000 (by using the switch "-p 10000").

If you like watching paint dry then you will surely love to check on the status of the miners:

dstm: https://zcash.flypool.org/miners/t1aoQJwvJqYT32xHVpYezWBxKuxPSwaJB1h
bminer: https://zcash.flypool.org/miners/t1dU7Gve41A3b4mxL7a3oVAnBLsF9kMgDgA

I created these two addresses just for this test so they are starting from 0.
dstm catches up. After beeing some steps behind its now close up.
member
Activity: 461
Merit: 49
@MagicSmoker

- Flypool reports 24h hashrate right there in the graph. It's the rightmost orange dot or the value reported at the top for average, e.g. https://i.gyazo.com/2026ef989969e01c7003d854512bedc5.png (the orange dot is better because you can read it with 2 decimals more or less, the value at the top only gives you a single decimal)

- Luckpool only gives you a 12h average, which is shit (and all miner stats are lost when their GUI goes down, which it does almost daily), it's the small number at the bottom of the first box: https://i.gyazo.com/611445b6a74f35539321d1adf621be35.png

To all of you: Please STOP using Luckpool. You're aware that it gives a full coin to the block finder (that "jackpot" shit they have), and reduces the payout for everyone else, right (block finder gets 1 ZEN, everyone else shares only 10 ZEN instead of 11 ZEN)? This advantages the large miners. You will lose profits with it unless you have a large hashrate larger than the majority and you mine for very long periods uninterrupted. Don't listen to the idiots who claim that everyone has the same chance to find a block and get the jackpot. That only holds if *everyone* mines an infinite amount of time. Otherwise, guess who will find more blocks per unit time, and who is more likely to leave the pool before they find a block? Anyone with some statistics background can see the scam behind this. If that bullshit were true, casinos would be going bankrupt, instead of thriving (they have more money than you).

Go build your own cuda miner

Awww, isn't that cute. There had to be someone who'd resort to the fabulous and very constructive argument of "do it yourself if you don't like it" ... sounds like you're either a genius who can do everything and needs nobody or are content with everything thrown at you. If you're happy paying bminer 2% despite some suspicions of fraud, good for you. Some of us aren't. Some of us care about frauds being exposed if they are indeed frauds.

Fraudulent behaviors will not get you very far and it hurts the community. That's not what I'm interested in.

I see that the relationships between miners and developers are partnerships -- the mission of the developers of bminer is to bring the best mining software to the community. The miners can benefit from a faster and more reliable miner.

There are significant amount of users that are actively using bminer and getting more payouts from the pools every single day. That's the value that bminer brings to the community and that's what I care about. If there are bugs that prevent you to get the maximal benefits from the hardware then I'm more than happy to look into it and try to fix them for you.

To the technical points, there are some confusions about the connections to api.bminer.me. I explained a few times that bminer will request runtime and licensing information from time to time. It might be a better idea to add it explicitly to the LICENSE file, I'll try to do it in the next release.

Bminer is a relatively new miner and I understand that it might not get the benefits of doubts. I can assure that there are no fraudulent behaviors in the miners, it is always difficult to claim or verify the statements given that it is close-source miners. The argument not only applies to bminer, but also any closed-source miners, including dstm, Claymore, and EWBF. If there are no mutual trusts between miners and developers then FUDs can fly around -- therefore I think it is always a good idea to test whether the miner works well for you. At the end of the day the important thing is to mine more efficiently.

I would suggest not using bminer, or any other miners if you don't trust them or you do not agree with the LICENSE file. There are slightly slower, but solid implementations for EquiHash miners available (e.g., kudos to nheq). While I'm trying hard to make the miner work well for you as many other users, at the end of the day it is always important to find the miners that work best for you and you're comfortable with (e.g., open-source miners).
newbie
Activity: 43
Merit: 0
I have eight mining rigs. Each has 6 GPUs (1070s and 1080Tis). I usually mine on nanopool. If anyone tells me how to set up a test. I can do it as well to provide more data points. I am curious which miner is faster for me to use as well, bminer or dstm.

Should I just put 4 machines on bminer and 4 machines on dstm? I am too lazy to tune OC settings of each machine. Can I just make the test two rounds. Switch the machines of bminer and dstm in the next round?
newbie
Activity: 23
Merit: 0
Can you share your batch file for bminer on flypool? I cant get it to work on flypool for some reason. Also, what cards are you using?
Thanks for the Test-setup.  Grin


BTW: Did anyone notice, that bminer-thread in z.cash Forum was closed? --- SCAM?
https://forum.z.cash/t/new-miner-bminer-a-fast-equihash-miner-for-cuda-gpus-5-1-0/26197

Quote
ShawnModerator12d
Beware: OP has been Banned for creating multiple sock-puppet accounts to promote this miner.

I wouldn’t trust software from someone who uses deceptive techniques. Links have been removed from original post.

Sock puppet accounts are against the Code of Coduct: https://forum.z.cash/faq40

Thread is closed.

Thanks for pointing that out. Too bad they closed it. Was interested in where the conversation was going at the end of the thread about how where IP's were being pointed (especially "104.31.69.221:443 - www.bminer.me (looks like telemetry from miner to author)"). Wonder if it is still the same and what happens if it is blocked.
jr. member
Activity: 30
Merit: 1
Can you share your batch file for bminer on flypool? I cant get it to work on flypool for some reason. Also, what cards are you using?
Thanks for the Test-setup.  Grin


BTW: Did anyone notice, that bminer-thread in z.cash Forum was closed? --- SCAM?
https://forum.z.cash/t/new-miner-bminer-a-fast-equihash-miner-for-cuda-gpus-5-1-0/26197

Quote
ShawnModerator12d
Beware: OP has been Banned for creating multiple sock-puppet accounts to promote this miner.

I wouldn’t trust software from someone who uses deceptive techniques. Links have been removed from original post.

Sock puppet accounts are against the Code of Coduct: https://forum.z.cash/faq40

Thread is closed.
newbie
Activity: 3
Merit: 0
Okay, comparison #3 started about 20 minutes ago concurrently mining ZEC on Flypool using a fixed difficulty of 10000 (by using the switch "-p 10000").

If you like watching paint dry then you will surely love to check on the status of the miners:

dstm: https://zcash.flypool.org/miners/t1aoQJwvJqYT32xHVpYezWBxKuxPSwaJB1h
bminer: https://zcash.flypool.org/miners/t1dU7Gve41A3b4mxL7a3oVAnBLsF9kMgDgA

I created these two addresses just for this test so they are starting from 0.


Just a thought... What if one card performs better than the other? (Silicon lottery). Will you interchange miners for those cards on your next experiment?
member
Activity: 308
Merit: 12
member
Activity: 297
Merit: 10
What you just experienced is the "lovely" PPLNS payout scheme (each block is different in length and each miner gets different shares in) ... like I said, you really should stop looking at payouts - when doing such short term tests, and with such low hashrates.

I guess I really need to finish that proxy

EDIT: 10k difficulty is too high for a single card ... you'd introduc more variability like this. You want frequent shares, but not too frequent. Lower diff such that the average share submission time you see reported by the miner is around 5 seconds if you have a good ping to flypool (< 50 ms) or 10 seconds if your ping to flypool is closer to 100 ms

Alright, let's cut to the chase: how much hashrate do I need to deploy for a valid test in your opinion, and how long do I need to run it for on Flypool? Because as of right now it appears I am wasting my time and electricity when I don't want to mine ZEC in the first place.

Note that the minimum difficulty on flypool appears to be 8000 now, so setting it to 10k wasn't really a stretch, and you did say that fixed difficulty would give more accurate results.

Ping time is 16ms, so very good.

I explained just above, in the EDIT, what you should do if you want to go forward with this test. Also, Flypool says they default to 2000 difficulty. Aim for 5-10 seconds share submission time, so lower the difficulty, start the miner, and time the first 5 minutes. If you get fewer than 30 submitted shares, decrease difficulty. If you get higher than 60, increase difficulty. Once you're done, fix it for both dstm and bminer, and let it rip for 24h. Don't forget that stales matter as they aren't paid, so make a note of the number of stale shares at the end (there were reports that bminer has a high stale share rate). High hashrate is useless if accepted share rate isn't improved.

And to remove your frustration, I'm happy to sponsor you for 24h worth of mined Zen with 2x1080Ti. Send me your zen address.

You asked about how much hashrate: as much as possible given you can't make the time window longer than 24h at Flypool ...

EDIT: you should also ensure that the two rigs/cards give the same hashrate with the same miner (i.e. there is no variability between rigs).
full member
Activity: 420
Merit: 184
What you just experienced is the "lovely" PPLNS payout scheme (each block is different in length and each miner gets different shares in) ... like I said, you really should stop looking at payouts - when doing such short term tests, and with such low hashrates.

I guess I really need to finish that proxy

EDIT: 10k difficulty is too high for a single card ... you'd introduc more variability like this. You want frequent shares, but not too frequent. Lower diff such that the average share submission time you see reported by the miner is around 5 seconds if you have a good ping to flypool (< 50 ms) or 10 seconds if your ping to flypool is closer to 100 ms

Alright, let's cut to the chase: how much hashrate do I need to deploy for a valid test in your opinion, and how long do I need to run it for on Flypool? Because as of right now it appears I am wasting my time and electricity when I don't want to mine ZEC in the first place.

Note that the minimum difficulty on flypool appears to be 8000 now, so setting it to 10k wasn't really a stretch, and you did say that fixed difficulty would give more accurate results.

Ping time is 16ms, so very good.
hero member
Activity: 756
Merit: 500
Whats requirements system for this to run? I have it successfully running on one PC, but on a different PC it doesn't even start. It throws no errors, so I don't know where to even begin....
member
Activity: 297
Merit: 10
make sure you add your crypto address so we can drop you some donations. this is something i'm surprised no one has done yet and would love to see ACTUAL numbers.

pre-thanks!

Aww, thanks, but no tips are necessary.

i think he was talking to me Smiley

I was going to build a 6x 1080 rig with these 2 1080s, but these were all I could buy before prices went full retard so I decided to use them to do a bunch of head-to-head comparisons of miners and pools while waiting to get 4 more.

Because of the comments @cryotoyes made about Luckpool not being the best choice for this test (or, really, the best choice of pool at all...) I'm going to repeat the comparison Yet Again, except mining ZEC on Flypool. It turned out that what @cryptoyes warned about occurred - that luck on a per-share basis, as well as variable difficulty, can skew the results enough to render them pointless.

In this case, the average hashrate reported on the pool side was 547 for bminer and 532 for dstm, or 2.8% higher for bminer. However, dstm earned slightly more ZEN, at 0.10776779 for dstm vs. 0.10643226 for bminer, of 1.25% more for dstm. Both of these metrics can't be true unless dstm got slightly more difficult shares and/or had slightly better luck at solving them.

What you just experienced is the "lovely" PPLNS payout scheme (each block is different in length and each miner gets different shares in) ... like I said, you really should stop looking at payouts - when doing such short term tests, and with such low hashrates.

I guess I really need to finish that proxy

EDIT: 10k difficulty is too high for a single card ... you'd introduc more variability like this. You want frequent shares, but not too frequent. Lower diff such that the average share submission time you see reported by the miner is around 5 seconds if you have a good ping to flypool (< 50 ms) or 10 seconds if your ping to flypool is closer to 100 ms
full member
Activity: 420
Merit: 184
Can you share your batch file for bminer on flypool? I cant get it to work on flypool for some reason. Also, what cards are you using?

Here ya go:

bminer -no-timestamps -uri stratum://t1dU7Gve41A3b4mxL7a3oVAnBLsF9kMgDgA.eleusis2:[email protected]:3333

Obviously change the ZEC address and worker name. This fixes difficulty at 10000, too (theoretically, anyway).

newbie
Activity: 1
Merit: 0
hi mate,

i dont get the miner to start if i want to deactivate my 1st GPU. I have 5GPUs in my Rig.
is it the -devices value?


This dont work:


@echo OFF

REM Change the following address to your Zcash taddr.

SET ADDRESS=t1RZpCpUurCoijUcaydfagdffhgadfsdf

SET USERNAME=%ADDRESS%.w

SET POOL=eu1-zcash.flypool.org:3333

SET SCHEME=stratum

START "Bminer: When Crypto-mining Made Fast" bminer.exe -uri %SCHEME%://%USERNAME%@%POOL% -api 127.0.0.1:1880 -devices value 1,2,3,4





please can someone send me an example?




**Solved... dont type in "value" **

START "Bminer: When Crypto-mining Made Fast" bminer.exe -uri %SCHEME%://%USERNAME%@%POOL% -api 127.0.0.1:1880 -devices 1,2,3,4
newbie
Activity: 23
Merit: 0
Can you share your batch file for bminer on flypool? I cant get it to work on flypool for some reason. Also, what cards are you using?
Jump to: