Topic: [ANN][AUTO-SWITCH] Profit-switch auto-exchange pool: CleverMining.com - page 72. (Read 554380 times)

Are there any good resources that people can recommend to convert my GPU miner (running windows and cgminer) to x11 or scrypt-n?  Also - which one of those options should I be considering more (I have 4x7950)

Great news, I will then stick to CleverMining
Thanks!

I notice that some operator start to offer auto-algorithm-switch based on profitability.
Is that in the pipeline for CleverMining?
I'd be happy to run some test if required.

Hello,

I have been mining on this fabulous clevermining of yours for days now. Unfortunately there hasn't been any payout at all in 12 days. Would some of you please look into the matter? The BTC address

1NB7s2uADPoJTw1VHCz5v6jhihcCeGg3WF

is correct. I'd very much love to keep being a "small" part of clevermining.

Thank you very much
Yours

Salina

I want to thank Terk, that after he add the difficulty and review what my miners are doing and gave me few pointers, now my miners are performing where they should be.

thanks  Terk

That's amazing news, CleverMining will get loads more hashes with that.
Maybe a contest for promotion? :p

This is fantastic news Terk!! Always on top of everything here! I'll be switching back to CM when you open the beta for X11.

That's awesome news! Especially now Scrypt-N proves to be this profitable, and X11 too. Both appear to be more profitable than scrypt / just mining LTC.

Soon or later the Scrypt market will be based allmost purely on Scrypt ASICS. Can't wait to receive mine though .

Great news! Are you going to implement X13 as well?

Awesome news Terk  , been waiting for this for quite some time now.

Regards
Mining Master

We're launching X11 and Scrypt-N this week!

As for fixed difficulty. You should use it only if you experience lower hashrate than expected. If you don't have issues then it's best to use VARDIFF (so don't setup difficulty by password).

The issues are mainly with some ASIC miners built of several chips (double digit number of chips) and if these chips are sometimes going dead/frozen. If you have 28 MH/s miner with 128 chips and VARDIFF sets your miner to send one share per 10 seconds, then each individual chip will send one share per 20 minutes if you have as much as 128 chips in one miner. If these chips tend to fall dead then the chip controller might not detect it quickly enough (to restart it) if they're supposed to send one share per 20 minutes and in result your hashrate will get down, because your miner won't be using all of its chips.

If this is the case, then you might want to try using fixed difficulty to send more frequent shares. Remember that valid difficulty values are powers of two: 128, 256, 512, 1024, 2048, 4096, 8192, 16384, 32768, 65536.

As a rule of thumb:
- if you have 16 chips or more, multiply your miner MHs * 32 and round up to the next diff value. E.g. 3.5 MH/s miner with 16 chips: 3.5 * 32 = 112, round up to 128.
- if you have 32 chips or more, multiply your miner MHs * 16 and round up to the next diff value. E.g. 12 MH/s miner with 32 chips: 12 * 16 = 192, round up to 256.
- if you have 64 chips or more, multiply your miner MHs * 8 and round up to the next diff value. E.g. 28 MH/s miner with 128 chips: 28 * 8 = 224, round up to 256.

Please never use difficulty lower than your MHs * 8.

Also, when you test everything with these values, please try to use one step higher and see if it's still OK. So if you have 12 MH/s miner with 32 chips and you used 256 and it's OK, change it to 512 and see if it's still OK, because at 256 your miner will send one share per 1.4 second and this is too frequent (and 28 MH/s miner will send two shares per second). This should be used only as emergency if your miner has issues with higher difficulty - as an exception, not a rule.

Sending more frequent shares than one per 10 seconds makes sense only if your chips are falling dead and you need to make them find shares faster (in order to faster detect if they're dead and not sending shares as expected and to restart them). Hammering the pool with one share per second isn't healthy neither for the pool nor for you (using more bandwidth) and should be used only if necessary.

So, if you don't experience issues, just use VARDIFF. If you play with manual difficulty, always please check one step higher to see if it also works fine with your miner. All this manual difficulty should be needed only for miners with falling chips where the miner controller silently restarts them if they're dead.

Indeed WafflePool does now support X11 and Scrypt-N.
According to their calculation it looks more profitable than Scrypt:

scrypt   vsLTC: 107%
nscrypt   vsLTC: 160%
x11      vsLTC: 135%

I'll be switching to WafflePool shortly this week ; mainly for X11 profit switching mining.
I'll keep CleverMining as Scrypt pool but looking at profitability I plan to run scrypt-n during day time and x11 at night.

I'd be happy to return on CleverMining if/when X11 and/or scrypt-n is/will be supported

Thanks for adding this feature Terk!

I've got mostly GridSeed 5 chips, and when peeking in on their performance on CM I noticed that often there would be a few struggling a bit, with several hundred seconds between shares submitted. My guess is that this was because the difficulty assigned by the pool was based on the total MH/s visible through the single IP address of the rig, without visibility into the individual mining units.

For now I've set my rig difficulty to 128. This seems to make the GridSeeds "happier", with more frequent submits. I've used 256 on other pools and have had similar results.

Experimentation aside, do you have a specific difficulty recommendation for GridSeed 5 chip based rigs?

I realize that this has nothing to do with overall profitability, it just affects variability. Although I suspect that in extreme cases it could be that some miner software might inadvertently reset a GridSeed that goes away for too long laboring under high difficulty. Since that could result in lost work, it makes sense to try to "right size" the difficulty for these devices.

Thanks in advance for any specific difficulty recommendations for GridSeeds.

is diff=4096 will be ok for my 10.4 Mh/s miner speed?
i have found the recommended values here , because i wasn't able to find it on clevermining website.

thanks

Thank you!  That's all I wanted, to know what was going on

I am genuinely sorry for calling you a botnet :-)

I believe there are not many CPU mining users left. Some people are turning off their GPU rigs these days with the flood of new ASICs increasing difficulty.

I don't want to lower difficulty more than 128 because there will always be some users wanting to “optimize” and set the lowest possible difficulty even while having high-hashrate miners. Sending multiple shares per second doesn't help anything and is not good for anyone (pool servers load, user network saturation, etc). I think 128 at the lower end should be optimal.

65W for 20 KHash??? You are going to be rich man. :-D

Even a single 350 kH/s Gridseed will submit one share per 24 seconds on average with difficulty 128. This is more than enough. Hardware errors shouldn't be dependent on difficulty and rather on frequency which you setup at your miners.

As for CPU: nobody is CPU-mining scrypt any more except botnets.

I don't think 64 is needed for any miner used nowadays. What miner do you have?

NEW! Setup your own difficulty

Our new stratum server has VARDIFF enabled and it should work great for most users. But if you have a miner with dozens of chips working as a single connection you might want to setup your own difficulty. You can do this by using password d=XXXX where XXXX is number between 128 and 65536 (only powers of 2 are accepted, so 128, 256, 512, etc, e.g. d=512). This will set a fixed difficulty and disable vardiff. It works per connection so you can choose separate difficulty for each of your miners.