Topic: ### A ChainWorks Industries (CWI) Project - CWIgm | Simple Powerful Stable - page 37. (Read 67732 times)

Pool Workers now reached 521! 100% increase in a day or so 

Thank you. I haven't restarted miners and for DNR I've got 1.6diff for 6x1070.
But for Sigt for now i've got 1diff for 6x1080. Lets see where it will stop.
Anyway as for now I see hashrate on the pool very close to the miner.

P.S. But the starting difficulty for DNR is only 0.007 - it is very low - for cpu miner maybe OK, but not for gpu. I get 10-20% of rejects at the beginning, it lowers quickly but not good anyway.

P.P.S Several minutes later 6*1080 also are on 1.6Diff.

Denarius (DNR) mining speeds with the CWIgm 0.9.8.

I run the cards at the +/- best efficiency (MH per watt), I'm not after highest possible speed regardless of the power consumption. Said wattage result is what the software is showing, these results are very consistent across other mining softwares.

Intensity is set randomly to 21, otherwise I have not touched the settings (except took away the "lodiff" and "mean-net-diff=1.1" settings).

CWIgm 0.9.8:
GTX 1080 Ti: 85-90MH @ 155-160W
GTX 1070: 45-51MH @ 100-110W

CCminer 2.2 skunk:
GTX 1080 Ti: 70MH @ 155-160W
GTX 1070: 40MH @ 100-110W

So the CWIgm 0.9.8 is ~20% faster than ccminer 2.2 in the current settings. Rejection rate due to "duplicate shares" is also higher at least in the start but I have to see longer average results to draw conclusions. Also some stratum connection errors have popped, new jobs are not found etc. but they have not lasted long. I'll see how things progress.

Can someone please explain how net-mean-diff works with N

Thank you

so would a max of 1.6diff work? ...

then push anything higher to the hidiff port? ...

we can try - and let me know how it goes ...

in fact - a few seconds interruption to the sigt mining - and ill get it restarted now ...

interruption is momentary ...

edit - changed this for the denarius stratum also ... let see how it all goes now ...

#crysx

and again ...

the 'luck' factor is based purely on a speculative number ... its is almost never accurate ( and dont know why its in there in the first place - by the original MPOS pool developers ) - as its more a guess than anything else ...

the 'luck' estimation is based on a number of factors - from network hashrate to miner availability in the pool ...

so if you are looking for an accurate figure - or even a steady one for that matter - you will be sorely disappointed ... each coin and algo has MANY different components to the estimates that the pool pulls in - and if you watch the hashrate for dnr for example - the network hashrate drops to one tenth of what it actually is at times - then back up again a minute later ... this is the daemon presenting these figure to the pool ( which means the coin developers code ) ... this same phenomenon happens with sigt as well ...

how does one keep an accurate 'luck' estimate on such massive fluctuations that happen so consistently? ...

my apologies if i havent answered your question in full - because the answer to your question is - there really isnt an answer ... yiimp is another pool that shows the same occurrences ... if you want to know what that pool has - then ask epsylon3 ( tpruvot ) as he in the dev and maintainer of the yiimp code ...

better to hear it from the horses mouth ...

so basing mining on a guess of 'luck' / estimation is just as good as a stab in the dark ... unfortunately - ive been a miner long enough NOT to trust ANY pools 'luck' measures ... you eventually get the knack of seeing the figures and weighing it ... but that take practice - not estimated figures ...

...

#crysx

Can you please lower the maximum difficulty for lowdiff port.
All my rigs stabilize with diff 2.5 (both Sigt and DNR) after 30-60minutes, and to my opinion it is too high even for 6/1080.
And it is completely unacceptable for 2/1080 or 5/1060 etc. But they also get the same 2.5diff.
I think 1-1.5 is more than enough.

P.S. DNR lowdiff starts with extremely lowdiff so that many shares are rejected at the beginning. 0.25 (as with SIGT) wil work much better.

Actually you didn't answer the question.
Your pool hashrate relative to SIGT network is on the same board as with DNR:
SIGT
Est. Avg. Time per Round (Network)   45 seconds
Est. Avg. Time per Round (Pool)   25 minutes 10 seconds
DNR
Est. Avg. Time per Round (Network)   31 seconds
Est. Avg. Time per Round (Pool)   20 minutes 18 seconds

But the "luck" factor is constantly different.
So I just asked if someone know how to find "luck" of yiimp based pools. Whether it is normal for all (bad luck) or just bad luck for your pool.

need it mate, a handful to keep an eye on them. u can pm if u wish. just R option will be fine, no need W.

much tia for the quick reply.

told ya i'll be back lol

let's hit some blocks !, ah, brought some friends along too.

All 8 are working now, but power curve and GPU usage are very unstable.
Also, each GPU sends about 1-3 shares/minute even at lowdiff 2000 port.

Thank you for your hard work. Looking forward to test the monitoring functionality once available.

the api port - not likely ...

but funny that you are mentioning an added feature - as we are working on that right now ...

our dev is putting the preliminary components together for the initial internal test ... there are NO promises this will even make the next revision of the beta - but we are working on various avenues for such functionality ...

#crysx

Well understood. However, as for the monitoring the miner, will there be an api for port binding or an added feature to the pool for mining monitoring?

ok ...

will be interesting to see ...

#crysx

on your display panel on CWIgm - if the port is 6000 - then its high diff ...

with 4 x 1070 cards - this should be the lodiff port - which is port 2000 ...

#crysx

have you taken notice of the network hashrate? ...

sigt -

Net Hashrate
1,580,681.87 MH/s

dnr -

Net Hashrate
24,173.70 MH/s

then combine that with the pool hashrate and compare what 'luck' ( which is a completely false value mostly - as the diff and hashrate change constantly ) the pool might have ...

zpool - 9.2gh tribus ...
yiimp - 36.5 tribus ...
CWI-Pool Denarius - 1.6gh tribus ...

its all relative ...

the more miners to the pool - the higher the hashrate - the better the chance ( or 'luck' ) of solving a block ...

network hashrate play a massive part in this also ... as the network hashrate goes up - so does the network difficulty ... and thats what creates the so called 'luck' making it difficult ( which is also why its called difficulty ) ...

the network diff for tribus right now tho is 1626 - which is pretty high for this algo ... because right this second - the network hash rate is 156gh ... our pool has 1.6gh ...

again - its all relative ... when we DO solve a block - we get higher rewards per miner - because there are less miners ... but the chances of solving a block is far less with less miners ...

#crysx

I edited my first message and added screenshots for it.
https://bitcointalksearch.org/topic/m.20759481

My launch config is:
cwigm -c sigt -u shubaduba.100 -p d=0.1 --lodiff --max-temp=72 -d 1,4,5,6,7 --cpu-priority 3 --cpu-affinity 0xC -i 25 -s 3

I will try to launch 8 instances of CWIgm and will report my results.

is 4x 1070 a lodiff?

another idea is to separate each card while mining ...

this way you can determine whether its the card itself - or something else ...

to mine with one card at a time - and test for say 25min periods each - use the -d option ...

since you have 8cards in one machine - this mean the cards are allocated from 0 to 7 ...

so to mine on card 1 - use -d 0 ... card 2 is -d 1 ... and so on ...

if your last two cards seem to be the issue - just mine with those alone using -d 6,7 ...

if they function ok after 25mins of mining - this usually means you are not supplying the power that ALL the cards require to function at FULL capacity ...

remember - each algo hashes differently - and some algos use more power than others ...

let us know ...

#crysx

What about bad luck for denarius?
It is 120-140 constantly for several days. While signatum has 60-80-90 the same days.


P.S. Does anybody know how to check yiimp pool for luck, or any other mining DNR?