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

[jerrybusey]

Est. Daily BTC Earnings Seem really low today???  I hope its just an error..

Oh and glad your feeling better..

I think it will go up once this endless tag round is over. I think it doesn't estimate till the end of the round so the estimate includes nearly 7 hours of nothing in the average currently. That's my impression at least since my back of the envelope calculation for this round showed nearly as much as the daily estimated total.

This is accurate.  Similar to the payout itself, the estimate wont include a round until its matured.

How does it work with tag rounds late in a day? Do the payouts go out next day or do you delay the day's payouts for the 300 years it takes for TAG to mature?

[nearmiss]

Est. Daily BTC Earnings Seem really low today???  I hope its just an error..

Oh and glad your feeling better..

I think it will go up once this endless tag round is over. I think it doesn't estimate till the end of the round so the estimate includes nearly 7 hours of nothing in the average currently. That's my impression at least since my back of the envelope calculation for this round showed nearly as much as the daily estimated total.

This is accurate.  Similar to the payout itself, the estimate wont include a round until its matured.

How does it work with tag rounds late in a day? Do the payouts go out next day or do you delay the day's payouts for the 300 years it takes for TAG to mature?

Yeah just rolls into the next day.  Any round not 100% matured *and* exchanged for BTC, rolls over.  This is for BTC payouts only of course. If you were getting paid out in TAG, you get as soon as the blocks mature, block by block.

[swiftshoot]

DID TAG FORK?

CGMiner reporting 11k Network Difficulty yet Coinwarz reporting 46.112 Difficulty?

[nearmiss]

DID TAG FORK?

CGMiner reporting 11k Network Difficulty yet Coinwarz reporting 46.112 Difficulty?

Its possible, though most of the pools seem to agree with each other (including us). 

[hotwired007]

0.007 BTC per MH and day... this profit barely covers a 0.10 USD/kwh rate. I keep my rigs working because they heat my house nicely, but this is the only reason now.

How is your efficiency on your mining Rigs?  I generally have 500 Watts per MH of hashing power, which translates to roughly $4/day in power at 11/kwh electricity rates.

Same results, about 0.5 kw per MH. That's 5 cents per hour per MH/s, so 1.20 $/day for every MH/s.

What HW are you guys running? i'm still running 5 series GPUs and my rig eats 650w for 1Mh/s (5870/5850/5770/5770).

I have a weird mix of 5xxx and 7xxx.

I have now got a 7950 added (7950/5870/5850) whats the best config? i have: -g 1 -w 256 --thread-concurrency 8000 -I 15,18,18 --auto-fan --auto-gpu --temp-target 70

edit - i'm getting a lot of HW errors with the 7950 (i think this is the thread-concurrency being wrong though)

[Thirtybird]

0.007 BTC per MH and day... this profit barely covers a 0.10 USD/kwh rate. I keep my rigs working because they heat my house nicely, but this is the only reason now.

How is your efficiency on your mining Rigs?  I generally have 500 Watts per MH of hashing power, which translates to roughly $4/day in power at 11/kwh electricity rates.

Same results, about 0.5 kw per MH. That's 5 cents per hour per MH/s, so 1.20 $/day for every MH/s.

What HW are you guys running? i'm still running 5 series GPUs and my rig eats 650w for 1Mh/s (5870/5850/5770/5770).

I have a weird mix of 5xxx and 7xxx.

I have now got a 7950 added (7950/5870/5850) whats the best config? i have: -g 1 -w 256 --thread-concurrency 8000 -I 15,18,18 --auto-fan --auto-gpu --temp-target 70

edit - i'm getting a lot of HW errors with the 7950 (i think this is the thread-concurrency being wrong though)

As hashcows has vardiff, I used multiple instances of cgminer - 1 for each card in the system.  This allowed me to tune each card individually (7850 & 5870 & 5770) and for each one to have its optimal difficulty.

[hotwired007]

As hashcows has vardiff, I used multiple instances of cgminer - 1 for each card in the system.  This allowed me to tune each card individually (7850 & 5870 & 5770) and for each one to have its optimal difficulty.

What thread concurrency (t/c) are you using for your 5870? - i'm running 6144 atm but i'm conviced it can do better (850 clock - getting about 400)

my 7950 is running at t/c atm 21712 but only getting a very low hashrate

[willittobe]

Hmm, seems like the cows are out to pasture at the moment? Went down maybe 10 minutes ago...

[GBattaglia]

Hmm, seems like the cows are out to pasture at the moment? Went down maybe 10 minutes ago...

Indeed.  Something is off.  Can't connect my miners to the pool; just hangs at 'Starting CgMiner'

[jedimstr]

COW DOWN COW DOWN!!!

Who's gone Cow Tipping? 

[aTriz]

COW DOWN COW DOWN!!!

Who's gone Cow Tipping? 

Fixed up, sorry about that guys...


Cows had to poo!

[Thirtybird]

As hashcows has vardiff, I used multiple instances of cgminer - 1 for each card in the system.  This allowed me to tune each card individually (7850 & 5870 & 5770) and for each one to have its optimal difficulty.

What thread concurrency (t/c) are you using for your 5870? - i'm running 6144 atm but i'm conviced it can do better (850 clock - getting about 400)

my 7950 is running at t/c atm 21712 but only getting a very low hashrate

8192 for my 5870 w/1GB

Code:

cgminer --scrypt --worksize 256 --lookup-gap 2 -I 15 --thread-concurrency 8192 -o stratum+tcp://stratum01.hashco.ws:8888 -u username.worker -p password

this gets me ~375 kh/sec with stock clock of 850/1200 so I think you're spot on with your config.  I had to balance mine with using the machine, so I tend to run a lower intensity on that card as it's my everyday workstation.

[dolby]

What should I do in order to keep reject ratio lower? I'm constantly getting Rejected after Stratum from pool 0 detected new block on my faster rig.

My reject ratio in cgminer 3.30 is  4.3% after 24h  on my faster rig 2462 kh/s
......................................and only 0.4% after 24h  on my slowest rig 2128 kh/s

some advice please
thx

[goofy73]

guys you should take difficulty from the coin client (getmininginfo command in console, think you know it) Otherwise sites like coinchoose, coinwarz etc shows wrong value or show it with big delay.. And why you don`t mine MNC?!

[nearmiss]

guys you should take difficulty from the coin client (getmininginfo command in console, think you know it) Otherwise sites like coinchoose, coinwarz etc shows wrong value or show it with big delay.. And why you don`t mine MNC?!

I assume your referring to the site itself.  Of course we take difficulty from the coin client.  We don't use coinchoose/coinwarz or any other similar site for anything.  MNC was in the rotation for quite some time, but it had some issues recently with forks.  I've been trying to track down a legitimate new client/src and ensure we are on the correct chain before re-enabling.  Hopefully this will be done today.

[sal002]

guys you should take difficulty from the coin client (getmininginfo command in console, think you know it) Otherwise sites like coinchoose, coinwarz etc shows wrong value or show it with big delay.. And why you don`t mine MNC?!

Do I show the wrong value?  I get it from the getmininginfo.  My delay is five minutes, though, so maybe that is what you mean.

[nearmiss]

guys you should take difficulty from the coin client (getmininginfo command in console, think you know it) Otherwise sites like coinchoose, coinwarz etc shows wrong value or show it with big delay.. And why you don`t mine MNC?!

Do I show the wrong value?  I get it from the getmininginfo.  My delay is five minutes, though, so maybe that is what you mean.

Could be, hashco.ws is also delayed a couple minutes in updating the site, but is using live values for all its calculations behind the scenes.

[Prelude]

I know that each coin has their own share difficulty configurations, but would it be possible to lower the max from 1000? On fast coins like WDC (current round) my fastest rigs often don't even have time to submit a share, and when they do have time it's only from 1~3 GPUs  out of 6. Makes me feel like I'm burning electricity for nothing. Perhaps until (if?) ASICs come out for scrypt, a worker's overall speed/difficulty calculation should be limited to the fastest GPU available, roughly 800KH/s. My 4.5MH/s rigs get hit the hardest since they are being treated as one single 4.5MH/s number cruncher instead of the 6x 740~800KH/s number crunchers that they really are.

[Thirtybird]

I know that each coin has their own share difficulty configurations, but would it be possible to lower the max from 1000? On fast coins like WDC (current round) my fastest rigs often don't even have time to submit a share, and when they do have time it's only from 1~3 GPUs  out of 6. Makes me feel like I'm burning electricity for nothing. Perhaps until (if?) ASICs come out for scrypt, a worker's overall speed/difficulty calculation should be limited to the fastest GPU available, roughly 800KH/s. My 4.5MH/s rigs get hit the hardest since they are being treated as one single 4.5MH/s number cruncher instead of the 6x 740~800KH/s number crunchers that they really are.

run 6 instances of cgminer for the time being if you think you're getting penalized by unnaturally high vardiff.  If all the cards take the same settings, it's amazingly simple to create a batch file and use a variable from the command line to choose a specific device when firing it off.

[Prelude]

I know that each coin has their own share difficulty configurations, but would it be possible to lower the max from 1000? On fast coins like WDC (current round) my fastest rigs often don't even have time to submit a share, and when they do have time it's only from 1~3 GPUs  out of 6. Makes me feel like I'm burning electricity for nothing. Perhaps until (if?) ASICs come out for scrypt, a worker's overall speed/difficulty calculation should be limited to the fastest GPU available, roughly 800KH/s. My 4.5MH/s rigs get hit the hardest since they are being treated as one single 4.5MH/s number cruncher instead of the 6x 740~800KH/s number crunchers that they really are.

run 6 instances of cgminer for the time being if you think you're getting penalized by unnaturally high vardiff.  If all the cards take the same settings, it's amazingly simple to create a batch file and use a variable from the command line to choose a specific device when firing it off.

Eh, I suppose I could do that but it would be a huge pain in the ass considering my CGWatcher and CGRemote setup I have going on.