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

[nearmiss]

short hiccup, things will be back momentarily.  Sorry.


Edit: back (as of a few min ago)

[willittobe]

Yesterday for me was 0.0152 BTC per MH.  

Pretty bad day.

Almost 25% below middlecoin...

You sure you didn't have any problems?
Showing .0173 per MH here.

We did have a few small outages yesterday morning but they were fixed. Def a slower day than normal, it happens!

Well, yes, the problem is the profitability was low
No technical problems, if that's what you mean.

You guys consider adding NoirBits? (NRB)

[nearmiss]

You guys consider adding NoirBits? (NRB)

We've looked into it a few times.  Not a huge fan of its tiny global hashrate and really low diff though....generally that combo hasn't worked out very well for us with other coins.

[Epeus]

Sorry to report I switched the 6990 rig over to a LTC pool.
Reason : rejects all over the place.
The 7970 rig is still happy moooo-ing away however.
As I mentioned before, the 6990 on I 19 setting does not like the low diff coins.
The 7970's on I 13 dont care about it.
Same mobo/os/miner etc.
It has nothing to do with the pool.
Perhaps I'd better sell the 6990's and buy back 7970 instead....

[nearmiss]

Sorry to report I switched the 6990 rig over to a LTC pool.
Reason : rejects all over the place.
The 7970 rig is still happy moooo-ing away however.
As I mentioned before, the 6990 on I 19 setting does not like the low diff coins.
The 7970's on I 13 dont care about it.
Same mobo/os/miner etc.
It has nothing to do with the pool.
Perhaps I'd better sell the 6990's and buy back 7970 instead....

Very interesting observations.  Glad to hear its at least the more powerful card still happy!

[willittobe]

Sorry to report I switched the 6990 rig over to a LTC pool.
Reason : rejects all over the place.
The 7970 rig is still happy moooo-ing away however.
As I mentioned before, the 6990 on I 19 setting does not like the low diff coins.
The 7970's on I 13 dont care about it.
Same mobo/os/miner etc.
It has nothing to do with the pool.
Perhaps I'd better sell the 6990's and buy back 7970 instead....

Yeah, this has to do with the intensity value. Dropping down to i18 on a 7950 helps some, at the loss of hashrate, of course. Perhaps not a bad compromise, it's what I used back when I was mining DGC.

Since the 7970's for whatever reason like i13 as a sweet spot, as you say, they do quite a bit better.

[Wipeout2097]

This KrugerCoin is a pain

Hashrate     74 Kh/s
Reject Rate    89.19 %   

otoh, I have a 6950 and a 7870 XT, one used and the other is a well known failure at scrypt.

I wonder if I'm having the same problem as Epeus, just at a smaller scale. If not, honestly don't know what to do. Your pool is by far the best in so many ways, but my weird setup has some trouble with it.

[Eastwind]

I run my 7950 at 13 intensity with 2 GPU threads to reduce the rejected shares. It is 15% slower than 19 intensity with 1 GPU thread.

[MrJay]

I run my 7950 at 13 intensity with 2 GPU threads to reduce the rejected shares. It is 15% slower than 19 intensity with 1 GPU thread.

I've dropped the intensity on all of my cards down to 18 (5850's, 5870's, 6950's and 7950's) running 1 GPU thread and the rejects are around 4-5%  If I put them any higher the rejects jump to 12-15%.

Sorry to report I switched the 6990 rig over to a LTC pool.
Reason : rejects all over the place.
The 7970 rig is still happy moooo-ing away however.
As I mentioned before, the 6990 on I 19 setting does not like the low diff coins.
The 7970's on I 13 dont care about it.
Same mobo/os/miner etc.
It has nothing to do with the pool.
Perhaps I'd better sell the 6990's and buy back 7970 instead....

Try lowering the diff on your 6990, even try multiple threads on a lower intesity.  Yes you get a slightly lower hashrate (difference on my cards is like 5-10kh/s) but you get less stales and a higher return, at-least that's what I have found anyway.

[MrJay]

I'm tripping over to my backups again

[Oldminer]

Got 2 x machines that cant get connect.

Moooo

[johndec]

Pool down again.  Come on guys, either stay awake 24 hours a day or get a back up server online..   

[Racer8]

I'm glad I set up a failover pool this morning.

In that respect it would be good to have a stat on the most profitable coin the cow has seen the last 3,5,7 days to help us figure out what pool to set up for the (hopefully rare) occasion requiring a failover?

[aTriz]

Oddly, this seems to be a common theme at around the same time (of course when we are sleeping) the stratum goes down for a short time, we will have this fixed ASAP.

We are sorry for the inconvenience but we do have some good news on the way soon


- Stratum back up

[Epeus]

Try lowering the diff on your 6990, even try multiple threads on a lower intesity.  Yes you get a slightly lower hashrate (difference on my cards is like 5-10kh/s) but you get less stales and a higher return, at-least that's what I have found anyway.

Thanks for your advise.

However, I do need the high intensity because this rig is also CPU mining XPM.
If I cut intensity below 18 the hashrate skydives, unless I stop the CPU miner.
The 6990 does 950 Kh/s on I 19, with CPU miner enabled it drops to 915.
Any lowering of intensity has a dramatic impact on the hashrate. (I 17 gives 600-650)
So, thats why I'm reluctantly pointing it at a LTC pool. High hashrate, almost no rejects, and my CPU is doing something usefull.

[swiftshoot]

Try lowering the diff on your 6990, even try multiple threads on a lower intesity.  Yes you get a slightly lower hashrate (difference on my cards is like 5-10kh/s) but you get less stales and a higher return, at-least that's what I have found anyway.

Thanks for your advise.

However, I do need the high intensity because this rig is also CPU mining XPM.
If I cut intensity below 18 the hashrate skydives, unless I stop the CPU miner.
The 6990 does 950 Kh/s on I 19, with CPU miner enabled it drops to 915.
Any lowering of intensity has a dramatic impact on the hashrate. (I 17 gives 600-650)
So, thats why I'm reluctantly pointing it at a LTC pool. High hashrate, almost no rejects, and my CPU is doing something usefull.

Set CPU Miner to Lowest Priority in Windows or set the NICE value to 10 (using RENICE) for *nix to give your CGMiner higher priority.  This should give you more breathing room.

[Thirtybird]

Try lowering the diff on your 6990, even try multiple threads on a lower intesity.  Yes you get a slightly lower hashrate (difference on my cards is like 5-10kh/s) but you get less stales and a higher return, at-least that's what I have found anyway.

Thanks for your advise.

However, I do need the high intensity because this rig is also CPU mining XPM.
If I cut intensity below 18 the hashrate skydives, unless I stop the CPU miner.
The 6990 does 950 Kh/s on I 19, with CPU miner enabled it drops to 915.
Any lowering of intensity has a dramatic impact on the hashrate. (I 17 gives 600-650)
So, thats why I'm reluctantly pointing it at a LTC pool. High hashrate, almost no rejects, and my CPU is doing something usefull.

When mining scrypt, you need 1 core on your CPU "available" to get your best hashrate.  It doesn't seem like it should be that way, but I discovered that when I was trying LTC on the GPU and CPU at the same time.  The loss of 1 core on CPU was trivial compared to the hashrate lost on the GPU.

[Thirtybird]

Is the server causing queuing of submissions for HBN? 
I'm watching my miner for the current HBN round (1448), and was noticing that each of my miners was exhibiting the following behaviour:  There would be no submissions for 20-30 seconds, then on each of them the screen would fill either a stream of accepts or rejects, all submitted on the exact same second.  After five minutes or so, it stopped doing this, and they all started submitting as they were found, but looking a the reject rate for the round being 20%, I thought I would bring it up.

[nearmiss]

Is the server causing queuing of submissions for HBN? 
I'm watching my miner for the current HBN round (1448), and was noticing that each of my miners was exhibiting the following behaviour:  There would be no submissions for 20-30 seconds, then on each of them the screen would fill either a stream of accepts or rejects, all submitted on the exact same second.  After five minutes or so, it stopped doing this, and they all started submitting as they were found, but looking a the reject rate for the round being 20%, I thought I would bring it up.

I wasn't able to catch this at the time, but unrelated, we've noticed HBN has been a rather poor performer for us of late.  We've reduced its chances of being hit for the time being.  I'll try and catch it next time to keep an eye on it, should we happen to hit it again anyways.

[BigDaddyWooWoo]

Try lowering the diff on your 6990, even try multiple threads on a lower intesity.  Yes you get a slightly lower hashrate (difference on my cards is like 5-10kh/s) but you get less stales and a higher return, at-least that's what I have found anyway.

Thanks for your advise.

However, I do need the high intensity because this rig is also CPU mining XPM.
If I cut intensity below 18 the hashrate skydives, unless I stop the CPU miner.
The 6990 does 950 Kh/s on I 19, with CPU miner enabled it drops to 915.
Any lowering of intensity has a dramatic impact on the hashrate. (I 17 gives 600-650)
So, thats why I'm reluctantly pointing it at a LTC pool. High hashrate, almost no rejects, and my CPU is doing something usefull.

When mining scrypt, you need 1 core on your CPU "available" to get your best hashrate.  It doesn't seem like it should be that way, but I discovered that when I was trying LTC on the GPU and CPU at the same time.  The loss of 1 core on CPU was trivial compared to the hashrate lost on the GPU.

Lol I did not know this and thought you were full of hoowie until I tried it myself and it turns out sir that you know what you are talking about.  I was having problems with hash rate on 3 rigs where I had been running my CPU on SRC and never made the connection until I read this.  I was killing myself trying to figure out what the issue was.  I freed up one core on each machine and TADA! back to normal.  I say good on you.  Thanks!