[ANN][Pool][Profit-Switch][Optional Auto-Exchange per Coin][Vardiff] ~ Hashcows

[zepadee]

Pool down ?

Were back up! sorry for the brief mintue or two downtime

Oh ok lol .

[1714627058]

1714627058

[1714627058]

1714627058

[1714627058]

1714627058

[zepadee]

Yup up again.

[zepadee]

Yup up again.

CGminer giving errors about idle time and Threads still existing. I think its down again.

NM, back up.

[swiftshoot]

CSC causing > 50% rejects... Guess the coin is too fast.  May need to Downgrade this coin on the profitability list when the Diff is low but increase when diff is higher.

[nearmiss]

CSC causing > 50% rejects... Guess the coin is too fast.  May need to Downgrade this coin on the profitability list when the Diff is low but increase when diff is higher.

Yeah that was crazy high.  Will take a look at what we make on it (outside chance its still worthwhile), but otherwise will downgrade it.

[willittobe]

Looks like there might be some problems recently, rounds 1608-1610 ?

A 22 minute CGB round with 0 blocks.
A CSC round with a time of 00:00:-1
A 2 minute MEC round with no blocks, and now we're on MEC currently for a long time.

[aTriz]

Looks like there might be some problems recently, rounds 1608-1610 ?

A 22 minute CGB round with 0 blocks.
A CSC round with a time of 00:00:-1
A 2 minute MEC round with no blocks, and now we're on MEC currently for a long time.

We were manually fixing things because CGB is having problems. Everything is a-ok

[zepadee]

Looks like there might be some problems recently, rounds 1608-1610 ?

A 22 minute CGB round with 0 blocks.
A CSC round with a time of 00:00:-1
A 2 minute MEC round with no blocks, and now we're on MEC currently for a long time.

CGB having PoS problems. All orphans.

[Rockbob]

I use 4 x 7950 but here is my CGMiner batch file adjusted for 1 x7950:

cgminer.exe --scrypt -o stratum+tcp://stratum01.hashco.ws:8888 -u username.1 -p x --intensity 18 --thread-concurrency 22400 --auto-fan --auto-gpu --temp-target 72 --temp-overheat 82 --temp-cutoff 90 --worksize 256

This gives me 570 Kh per card. The 2 important variables here are intensity and thread concurrency, these settings should work fine. You'll notice the "temp-target" is set to 72, this should be fine for a 7950. Note that if you reduce this number to say 60 or 65 your fan's rpm will jump up significantly. I think 72 is a good trade-off. Hope this helps.

Yeah after some pretty troublesome hours, with reading into all of it, setting up 2 setup configs (one for the time, when im on my pc and one for the sleeping/working hours) and a oc profile, i jumped from the 15 kh to ~670kh. And after i finished alll of this (damn, this were 7 troublesome hours procrastinating from my study stuff lol) i just recognized, that it's Kh and not Mh. Is this normal for alt-coining? When I'm on BTC (with the normal settings), im on around 450 Mh/s. This kinda freaked me out, when i noticed that, right as i finished the tuning.

Thanks for the help mate.

[aTriz]

CGB has been temporarily disabled until it's fixed.

[mercSuey]

Looks like there might be some problems recently, rounds 1608-1610 ?

A 22 minute CGB round with 0 blocks.
A CSC round with a time of 00:00:-1
A 2 minute MEC round with no blocks, and now we're on MEC currently for a long time.

CGB having PoS problems. All orphans.

CGB isn't having PoS 'problems'...PoS overrules PoW by design.  Long sequences of PoS blocks happen even for PPC, but it's about ten times more likely for CGB because of the one minute PoS blocks.  But PPC isn't susceptible to multipool hash spikes that can instantly double or triple the network hash rate, many dozens of times throughout each day.  Consequently there are roll backs when multipool or hashcows points their hashing at CGB right when a PoS block lands and/or in the middle of a sequence of PoS blocks.  PoS isn't the most friendly kind of coin for multipooling.  It's the risk you take when mining at multipools.

[aTriz]

We are looking into some issues with the last few rounds...will update here in a few!

[swiftshoot]

MEC and CBG killing the profits... lower their profitability plz...

Round #   Coin   Length   Mature Blocks   Mature Coins   Immature Blocks   Immature Coins   Coins Paid Out   Coins for Auto-Trade   My Est. Earnings
1611   MEC   01:28:01   0   0   0   0   0   0   0
1610   MEC   00:02:01   0   0   0   0   0   0   0
1609   CSC   00:00:-1   282   14100.08   7   350   550.24   13549.84   0.000006 BTC
1608   CGB   00:22:56   0   0   0   0   0   0   0. BTC
1607   CSC   00:10:45   204   10200.04   0   0   356.31   9843.73   0.000257 BTC

[nearmiss]

MEC and CBG killing the profits... lower their profitability plz...

Round #   Coin   Length   Mature Blocks   Mature Coins   Immature Blocks   Immature Coins   Coins Paid Out   Coins for Auto-Trade   My Est. Earnings
1611   MEC   01:28:01   0   0   0   0   0   0   0
1610   MEC   00:02:01   0   0   0   0   0   0   0
1609   CSC   00:00:-1   282   14100.08   7   350   550.24   13549.84   0.000006 BTC
1608   CGB   00:22:56   0   0   0   0   0   0   0. BTC
1607   CSC   00:10:45   204   10200.04   0   0   356.31   9843.73   0.000257 BTC

CGB has been addressed (for now).  the 1611 MEC round stats aren't correct, we are working on updating them, we earned ~1500 coins or so.

MEC round cleared up

[swiftshoot]

I use 4 x 7950 but here is my CGMiner batch file adjusted for 1 x7950:

cgminer.exe --scrypt -o stratum+tcp://stratum01.hashco.ws:8888 -u username.1 -p x --intensity 18 --thread-concurrency 22400 --auto-fan --auto-gpu --temp-target 72 --temp-overheat 82 --temp-cutoff 90 --worksize 256

This gives me 570 Kh per card. The 2 important variables here are intensity and thread concurrency, these settings should work fine. You'll notice the "temp-target" is set to 72, this should be fine for a 7950. Note that if you reduce this number to say 60 or 65 your fan's rpm will jump up significantly. I think 72 is a good trade-off. Hope this helps.

Yeah after some pretty troublesome hours, with reading into all of it, setting up 2 setup configs (one for the time, when im on my pc and one for the sleeping/working hours) and a oc profile, i jumped from the 15 kh to ~670kh. And after i finished alll of this (damn, this were 7 troublesome hours procrastinating from my study stuff lol) i just recognized, that it's Kh and not Mh. Is this normal for alt-coining? When I'm on BTC (with the normal settings), im on around 450 Mh/s. This kinda freaked me out, when i noticed that, right as i finished the tuning.

Thanks for the help mate.

That is slow... I get 645-670KH/sec on my 7950s...
intensity 20
thread-concurrency 40960
shaders 1792
gpu-threads 1
gpu-engine 1080
gpu-memclock 1250
gpu-vddc 1.020,1.01,1.003,1.07
gpu-powertune 0

I use to run my 4 x 7950 in low power mode getting 550kh/sec plus high power mode 7970 to get 715kh/sec total hash @ 2.9gh/s @ total power at wall of 1460 watts (Corsair AX1200i watt PSU) and now I run all boards at high speed with total hash of 3.3gh/sec and @total power at wall of 1250watts.  Saved 210 watts and gained 400kh/sec just by undervolting the gpus.
I had put my Rig in the big Living room now... It is a nice Heater for the whole house.. (cooler up north now) Wife hates it but if I am gonna pay for heating, I want a chance to make some money back.

[nearmiss]

Some updates....

CAP and CGB currently disabled.  We've got a new CAP client, though I ran into an error or two running a script, haven't had time to confirm if it was just an older artifact or an actual daemon problem. Hopefully we can re-enable tomorrow.  Undecided on what to do with CGB currently.   If its expected we may run into 40-50 blocks at a time being orphaned (though we've never seen it until tonight), then it likely deserves a fairly decent profitability hit.  I'll dig into this more tomorrow/later as well.

We've also been adding some LTC traded coins, such as FLO, MEM, XNC, IFC.  This is where the bulk of our time has been spent recently, ensuring the trade flow for these coins is smooth and functional.  These are currently in a somewhat 'beta' status, we are keeping a close eye on their performance, and will look for more to add if they prove profitable.

On the short term agenda:

* Code fix for minor daily outage
* Change ledger to be total historical record not just last 50
* Roll out diff caching to Hybrids (its been in place for non-hybrids for a week now)
* Roll out optional static and static-minimum diff options, likely including a drop in pool target diff, to help our low end miners hit their cached diff quicker.
* Start looking into implementation of 2nd stratum server, ideally on the North American West Coast.

More or less in that order.

[Wipeout2097]

Could someone please post last day's hashrate and payout? Thank you.

[Epeus]

It's the standard

"cgminer --scrypt -o stratum+tcp://stratum01.hashco.ws:8888 -u username.1 -p password" in a batchfile.

Sorry, if "settings" means something else, I'm pretty new to mining.

I use 4 x 7950 but here is my CGMiner batch file adjusted for 1 x7950:

cgminer.exe --scrypt -o stratum+tcp://stratum01.hashco.ws:8888 -u username.1 -p x --intensity 18 --thread-concurrency 22400 --auto-fan --auto-gpu --temp-target 72 --temp-overheat 82 --temp-cutoff 90 --worksize 256

This gives me 570 Kh per card. The 2 important variables here are intensity and thread concurrency, these settings should work fine. You'll notice the "temp-target" is set to 72, this should be fine for a 7950. Note that if you reduce this number to say 60 or 65 your fan's rpm will jump up significantly. I think 72 is a good trade-off. Hope this helps.

I agree on the intensity and thread concurrency settings, those are the most important to max out hashrate. You also might look into the number of threads. (  -g 1 or -g 2 )
Also important : the catalyst driver. My 6990 does best on 11.3, 7970 however needs 12.6

Note : I stopped using --auto-fan for temp control. This is just killing fans. Had 3 died because of this.
Rather use CGwather, as it lowers intensity when temp is too high.

[Aurics]

Could someone please post last day's hashrate and payout? Thank you.

My payment looks pretty low it was 0.01214 per MH.

[glon]

It's the standard

"cgminer --scrypt -o stratum+tcp://stratum01.hashco.ws:8888 -u username.1 -p password" in a batchfile.

Sorry, if "settings" means something else, I'm pretty new to mining.

I use 4 x 7950 but here is my CGMiner batch file adjusted for 1 x7950:

cgminer.exe --scrypt -o stratum+tcp://stratum01.hashco.ws:8888 -u username.1 -p x --intensity 18 --thread-concurrency 22400 --auto-fan --auto-gpu --temp-target 72 --temp-overheat 82 --temp-cutoff 90 --worksize 256

This gives me 570 Kh per card. The 2 important variables here are intensity and thread concurrency, these settings should work fine. You'll notice the "temp-target" is set to 72, this should be fine for a 7950. Note that if you reduce this number to say 60 or 65 your fan's rpm will jump up significantly. I think 72 is a good trade-off. Hope this helps.

I agree on the intensity and thread concurrency settings, those are the most important to max out hashrate. You also might look into the number of threads. (  -g 1 or -g 2 )
Also important : the catalyst driver. My 6990 does best on 11.3, 7970 however needs 12.6

Note : I stopped using --auto-fan for temp control. This is just killing fans. Had 3 died because of this.
Rather use CGwather, as it lowers intensity when temp is too high.

Another word of advise:

THE most important cgminer flag is:

--verbose

Without it the miner's not telling you if you are getting any errors at all. So while your KH/s may be sky-high (like the poster's above us), you're just mostly spewing garbage to the pool without even realizing it.