I updated my response above after analyzing the comment I was responding to.   Cant really comment on rejects other than let diff be default at first.    Basically explain to me what exactly you are trying to calculate?   your profitability scaling for the miner password or how much your hashrate should net you?

highlighted a typo...

Easiest way to calc profitability is:
multiply algo by hashrate, then convert from mBTC to BTC.

in ccminer it was "blakecoin"

stratum hasn't ever changed the difficulty on my manually set machines.

on neoscrypt;  I had a forced 16;  and now;  with no diff;  within 20 seconds of shares, it kicks me to 32.   So;  I am sure it wasn't changing my manual diff setting at all.

On the wallet page:
How hard would it be to add a dot on the graphs for each algo to show when a coin was found by your rig?

try not setting a diff and see where stratum levels you off.... that's normally a good place to start.

It seems recently hes been trimming the acceptable limits of shares per second.   Ive been having to up the numbers on my miners recently due to rejects (I assume too many lower shares).

are you using manual diff?

Hahahahahaha =)    Yeah;  They are pretty nice cards for sure;  He couldn't just replace them and toss em.   Im interested as well;  That much hash would be a nice thing to have.  It would give me incentive to build a 3V battery arrays out of commonly available cells.   Doesn't take much work to make a few nice 4Kw batteries to be charged with a solar array.  It would be a truly off-grid mining setup at that point cause it would be a wifi signal to a cellular link! lol.

I hope I can get some good efficiency with a generator and vapor feed system.  If I can get down to 1 gallon a day making a steady 13Kw;  I think Ill be a happy camper.  I can dream right?  So far my crude tests show promise.

Awesome reply.  I'm watching now.

My friend is co-owner of Elevate PRoductions;  they do lots of live shows and video mapping... so putting the hardware to use that's old an dunused, or not currently used at events;  He loves me right about now for introducing him to mining

Got these dropped in my lap last night.   6x R9 280X OC editions.

Time to build another multi-algo rig.  Im just going to source some board and cheap processor/memory;  but make sure that it has at least 6 PCIE ports on it.  Ill have to build a custom enclosure and also use socket extensions;  but that's no worry.  all 6 are the exact same card.

Does someone have a normalization values already for this card?   (save me some time   I'm wondering if just leaving pool default would suffice for this card.....

And does someone have any recommendation of the best version of software for this slightly old card?

Simple.  look a few pages back for my posted batch.  You will see the normalization factors I created.  They directly correlate to hashrate at the level of profitability that the particular algo is paid at.  You find the details in the profitability preview at the upper right of zpool:  *** values in mBTC/Mh/day (mBTC/Gh/day for sha256 and blake algos)


So:

If your machine does 500Kh of SCRYPT;  and since scrypt is measured in Mh, then its going to be 0.5Mh or scrypt=0.5
If your machine does 1.5Gh of DECRED;  and since decred is measured in Gh;  then its going to be 1.5Gh or decred=1.5
If your machine does 11.5Mh if LYRA2V2; and since lyra2v2 is measured in Mh;  then its going to be 11.5Mh or lyra2v2=11.5
If your machine does 110Kh of ARGON2; and since  argon2 is measured in Mh; then its going to be 0.110 or argon2=0.110

This way they are all balanced to the scale they are paid on;  and thus;  balanced to each other.

We normalized a machine with 2x 750Ti's in SF recently;  Ill try and post that batch when I head back to the City again.  But its worth notice a 750Ti is about half the computing power of a GTX980.

I'll comment that cheap reliable and fast are rarely used all together to describe something.  Usually it's just two of the three that you get.


You're still doing an amazing job with the pool

Right now due to power constraints where I have it;  my S7 is plugged in with only 2 hash boards hooked up.

Surprisingly this is the best share its ever given me so far =)    Im going to stick it out until the halving at least.   Try to make the miner pay for itself and a few more.

same.

Hoping for that lotto ticket!

{"hashrate1m": "2.37T", "hashrate5m": "2.05T", "hashrate1hr": "460G", "hashrate1d": "1.77T", "hashrate7d": "2.33T", "lastupdate": 1461809298, "shares": 2234951360, "bestshare": 11854253646.424986, "bestever": 11854253646}

only very recently for the first time have I ever seen rejected hashrate from zpool in the past 2-3 days.

And that's from machines on a nice connection in SF....  But I still haven't see them on my main machine at home on the cellular link.  So Id chalk it personally up to the connection you are using... a node down the line or something.

If you get your difficulty set right;  your hashrate on the site will more or less be within 10% of your miner at any given time.

As far as SHA256 disconnects;  your hashrate average drops to zero and must build up again, so the graph will not be exactly what your hashrates actually were.
You may notice your hashrate drop a ton or completely;  look at the pool statistics and notice that the hashrate probably dropped substantially and is building back up again....  look at the pool statistics for sha256;  you see the spikes in hashrates/profitability lined up as they happen.  sometimes they are more frequent than others.   Faster miners take a harder hit than slower miners with this issue.  I have no issues keeping my S3's pointed at zpool;  but I just have my s7 on solo bitcoin.   Too much intervention needed from the disconnects causing issues with the miner switching pools, etc.

decred... 11 hours on a 2 hr ttf....   wow.  speechless.   And how is one block reporting a hash of zero?

Could there be an overall server side hashrate calculation throwing ttf off somehow?  or are we just that unlucky the past few days with this much hashrate we've been having?

difficulty is changed through the password:  "c=BTC,d=XXX,scrypt=0.5"

Yeah thats what I thought might be happening.  At least that what was shown as an orphaned block was a real hit =)

i can't comment at the moment;  im pointing speciaifally to DCR this month to see overall profitability...

which ports aren't connecting?   My X11 rig in SF is mining fine right now.... so are the CPU algos.

what port(s)?

My DCR miner is up and running.... my SHA devices are off at the moment or on solo.....



I am going to do a trial run of mining ETH on the side.  Since DCR uses almost no memory;  why not run them at the same time right?  I got this GTX980;  might as well put the fast memory to use!

Ill report back the changes in hashrates of DCR, and the overall profitability increase by doing so.