Topic: ▂▃▅▆▇⫷[ 🆉🅿🅾🅾🅻.🅲🅰 ]⫸⫷[!KAWPOW!]⫸⫷[ the miners multipool ]⫸ ▇▆▅▃▂ - page 203. (Read 279614 times)

From what i understand yes, because at the top of the miner when it starts it says ccminer 2.2, it was just updated by member Skunk. He states he used ccminerTribus 2.1 as the base code to update from.

IS the skunk 2.2 the same as the ccminer 2.2?

Wanted to post up how the new CCminerSkunk2.2 fairs up to my typical lineup of miners on the 1080ti's this is a 3x 1080ti rig i ran the benchmark on. 65% tdp, 200+ core, 500+ mem

https://github.com/signatumd/releases/raw/master/ccminer-2.2-skunk.zip

Working nicely on all algos so far.  Tribus got a nice bump in hashrate.  Haven't noticed any others yet.

How is ccminer 2.2 doing? I haven't tested yet on a lot of algos.

try a different version of ccminer manually... I bet its a version that has broken compile support for the groestl algo....   mining C11 with alexis78 is an example of such a thing happening.

I have not been able to connect to groestl at all when it trys to switch to it, possible connection issue....
it attempts 3 times, then moves on but has failed 23 times to connect today

I added it to my mining rigs, but unfortunately its not yet once broke into the top 5 for profit on my rigs, so since benchmarking it on my rigs, its not been mined again since... I found CCminerTribus 2.1 to have the highest hashing rates on the 1080 and 1080ti's on it

Hi,

I just added the jha algo and SWEEP coin to zpool.

Cheers

Okay  I will delete that post. Thanks for info.

And deleted.

Payouts have changed since you were last mining here. It should be over 0.015BTC for every payout (except for the Sunday payouts).

https://bitcointalksearch.org/topic/ann-signatum-new-algorithm-fair-launch-no-premine-2030529

No exchange yet so won't be on zpool. Waiting for ccminer 2.2 to mine with Nvidia.

where you seeing this?

Whats this skunk algo all about?

This right here is a good strategy.  I'm going to have to pay attention to this.  Thanks!

FWIW on skien; up to 3Gh on one machine, the diff still hovered between .8 and 1.1....

keep an eye on your share % of an algo for ~10 min-2 hours...  average that percentage, then look at the pools total BTC earned for the last 24 hours... see how good of a theoretical cut you would get....

Take the low % ones, and just throw them out the window (disable in batch), leaving 4-5 algos and only the best earners... you will see more profitability.

Also consider my theory (that keeps proving in my life to be true) that when a hashrate on an algo grows past a certain amount;  profitability feels like the network total hash has increased.  Like skien;  when it was ~30Gh, and I was 1Gh;  I was making insane profits;  but as soon as another 70+Gh ended up there, the profitability flattened out until the hashrate dropped on the pool for a bit.

For nvidia rigs;  I choose skein, neoscrypt, C11, X17, and NIST5 currently.... as an example.  Might help you out.

Keeping the others in the batch allows you to gain the quickest benefit to ming a coin/algo that has suddenly surged in exchange pricing, so it's a double edged sword as to what you choose to do.

Every now and then, on some algos, I see reduced hashrate.  It is usually just a run of unlucky shares (no high results in your work units)....  and is sporadic when it happens.  sometimes just an hour or two, sometimes a day....

skein is notorious for having an odd share-to-hashrate calculation;  cause when you find a share @ lets say a diff of 30, often you will see an identical, or nearly identical sized share right after it....  happens a lot on skien.

I personally have always seen less profit on equihash, and haven't even bothered trying to mine it again since my last test several months ago.

The one I had issues with before was hmq1725 before the default diff was raised.  Also equihash somehow defaults to 200 (which is way too high), so I corrected that manually.

Then it was skein, which no one responded on:

"The hashrate for skein is off.  My miners are telling me they are hashing at 781 MH, but on the site I'm only seeing 57 MH.  One has 2x 1080 TI so it is getting 1.91 GH, but the site says 120 MH.

What's going on?"

I kind of gave up on following up after no one answered a 2nd post (got lost by the person screaming wolf).  But now I notice timetravel giving me hashrate issues.

I've been noticing my earnings isn't higher using the profit based method (multiple algos, factors, etc) compared to just mining on equihash only.  But I noticed it was on algos that were very low in profits and most likely because the % of shares is low due to the actual hashrate seen by the pool vs what's considered profitable by the miner based on hash rate of the miner (not on the pool side).

So now I am paying attention to the miner reported speed and what's being reported on the pool.  I give it about 5 minutes to "catch up" to see if the hashrate settles and get close to the reported hashrate on the miners.

PS:  No issues on the only 2 CPU algos (m7m and xevan).

It seems to be the nature of the Timetravel algorithm.  It seems like it won't accept any shares for a bit and then all of a sudden submit a ton of low difficulty shares all at once.  I don't think this is a pool problem because I've seen the same behavior on other pools I've tried Timetravel on as well.

Setting a fixed difficulty also doesn't seem to change this behavior much.  This leads me to believe it is something with how the shares are calculated or intended to be accepted by the pool.  It might be something with how it is coded in ccminer, but I'm not sure.  As for the difference between local and pool hashrate that is all up to the luck of which of your shares are being accepted.  If you're not seeing errors about shares being rejected then it is likely just unlucky hashing that has it down.  Overtime it will average out.

be sure diff is a proper multiple.   some algos don't like odd diffs, and some don't like fractions (decimals) for some reason.   Crackfoo may know more.

How many diffs did you try to set?    I noticed your issues on algos like the CPU mined low hashrate ones with 2-3 decimal places.