Is there way to set intensity?

Just wanted to start off by saying that i have been using Bminer for a few weeks now and am very happy with the performance.

There is one issue that I am encountering when using the miner though and would like to see if that can be fixed an a future release.

Sometimes when I lose connection to the mining pool or restart the pool I get the following error on the miners.  They can stay like this for quite some time before they establish a valid connection and begin submitting shares.



Cheers,

nUm

I need to test it a little more, but console might be artificially inflating the numbers.  I'm still new to mining and have tried to a bunch of different combinations of miners and mining pools to see what works best, but I don't think I've let any of them really run for a full day yet (which probably isn't the best way to test from what I've been reading).

Currently using dtsm Zcash miner against Slushpool.  I think I'm going to run that for a few days then try against flypool for a few days.  Then do the same for Bminer and compare results.

@cryptoyes with one thing i agree, make a test on a pool like Luckpool is bad idea 1. very small Hpower (~2 MS/s) 2. Jumpy & unstable (personal when i try first thing what i sen was high ping = bad, even website it take some time to load) 3. very few miner worker

A good test it can be done on a pool with better speed like at list 8-10 MS/s with +1000-2000 miner what can provide constant block found hour day & with less jump hoper around

@cryptoyes but at part with a test it can't be done with 1 single GPU i not agree only think what @MagicSmoker need to change is pool that it

p.s. Personal i will suggest to admin of pool like Luckpool, Zenmine to combine they'r power & make a single one, it will be more efficient for them & for miner to

cheers

I tried it and did not see any changes for the better. I hope there is a future for this project. 

Hmm... I'll give Flypool a shot, but I'm afraid I can't do anything about only dedicated 1 GTX 1080 to each miner for these tests right now - or for the immediate future - as GPUs simply aren't available unless you want to pay fuck-you prices.

I have to concede your point about pool luck, though. Luckpool was finding a block every few minute, but that information seems to be out-of-date because I just checked the blocks tab and it looks like the average TTF is now 1.1 hours, so 24 hours with a single card is, indeed, way too short of a time period.

BUT... if the TTF is less than 5 minutes then a 24 hour test based on payout should be just as accurate as counting up the number of fixed diff shares (fixed diff does not appear to be an option on Luckpool, however), even with a single GTX 1080.

I would prefer Miningpoolhub. :-) There are 4 coins of Equihash there to be mined, which are mostly top of profitable Nvidia mining these days.
(Just suggestion. :-) )

I did a concurrently run comparison between MPH and NiceHash for 1 week which ended a few days ago and MPH lost, earning 10% less than NH; that's not exactly a good showing, given that NH more or less sucks.

MPH's website is a confusing mess, as well. For example, they don't list the coins available for each algorithm like on most Yiimp-based auto-switch, multip-algo pools. Manually checking those coins I know use Equihash it looks like the only one that finds blocks frequently enough for a 24 hour test to be valid is Zclassic. I also don't have a wallet set up for Zclassic yet, but I've been meaning to do that so this isn't a real obstacle.

I don't want to use auto-convert to BTC mode, however, as I noticed my BTC balance actually going down while coins were still waiting to be auto-exchanged.

@MagicSmoker - you're missing the point about luck. It's not the pool's luck I was talking about (see my message again) but each share's luck. As I explained a while back, even if you are mining with 2 rigs simultaneously, the 2 rigs will receive different shares to mine, and those shares will have different luck. Because you have a single card in those rigs, the payout will thus be highly variable.

The biggest flaw is that you look at payout instead of pool reported hashrate. The second flaw is that you are using a single card (a single card would be ok if the pool could give you 1 week average, but none of them do). The third is that you are using a bad pool (bad because it goes down often, has a highly variable ping, only reports 12h average, and has a very low hashrate -- yes, 2MH/s is very low, especially given you're using a single card).

If you don't have the expertise to setup two identical private chains or divert rpc packets, then the best you can do is to use Flypool (226 MH/s) and look at the pool reported hashrate after 24h. It will be more reliable than luckpool+payout, but still slightly flawed (again, single card, different lucks for each card).

All that being said, I'm now pretty sure bminer artificially inflates numbers. Oh well, what do you expect - these guys want to stay anonymous and use shady https connections back to their own servers...

I'm getting annoyed by these guys charging a ridiculous 2% of all our profits. I coded an rpc proxy for equihash which i'm using in our farm. I will add functionality to report hashrate for each client connected to the proxy and will then open source it. The proxy impersonates a single miner and hides the actual miners from the pool. It relays the job sent by the pool to all proxy clients. At least you can be sure they all mine the same share, start at the same time for each share and have the count done locally. Sadly, because these guys closed sourced their miners, you can't control the seed they start with for each share, so luck will STILL be different between dstm and bminer ... i.e. you will still need to wait a long time for reliable results, but at least I can compute total average hashrates, rather than only 12h or 24h.

If bminer is cheating, I want to expose it. Will look into this next week when hopefully I'll have more time. I stopped using bminer after doing my dstm vs bminer test.