- GenTarkin
- Archived posts: 135
- Joined: Dec 02, 2015
Re: Bad profit
CritterDog wrote:Ah, good idea... I have some gridseed blades I can fire up to see how their reject rate fares is in comparison to the Titan.Steve Sokolowski wrote:My reject rate on the A2 is about 0.12 on both pools..I think its around the same on my gblacks but I reset them so cant say for sureGenTarkin wrote:I spent some time this morning investigating the rejection rate. The rate of shares that are completely rejected are 0.7%.
So, you made 86% pps @ prohashing, 14% less than 100% ltc pps.
What was your reject % on prohash vs litecoinpool?
Now, lets run some quick math:
Lets assume prohashing pulled off paying miners even(100%pps ltc)
Prohashing takes 5% in fees(drops to 95%pps ltc)
If your reject rate is 3-5% like mine has been, then thats another 3-5% loss(drops to 90%)
Add the 3% bonus you get at litecoinpool currently and that equates to another 3% loss at prohashing(drops to 87%)
So....
That 86% is awfully close to the 87% we just guestimated.
Prohashing needs to A: fix their high reject rate(if thats indeed happening) B: continue to work on their multi algo switching - Clevermining manages to always payout more than prohashing(as ive experimented with in the past month or so).
The nice thing about prohashing tho, is the ability to be paid in any coin you want, which saves on service fees when using something like shapeshift.io
Chris is running a query right now to investigate some other possibilities. One possibility is that many shares are being submitted stale, and therefore only the merge mining portion of those shares are being credited. Chris will have more information on that soon.
We ran a query and determined that coin selection can't be the cause of this problem because with the existing coins, only 92% of expected is being earned. Even after we penalized those "low luck" miners (who apparently fixed their systems, because there are no more forfeitures occurring), 8% is not being accounted for. We thought that the "low luck" miners were responsible for the entire difference, but there must be another issue that we have yet to be able to determine.
I really am not sure about the Titan's work restart delay. I had the asic command scanning individual core activity on the last die in line (as per my previous theory of sequential die flushing & work updating) and the cores on the last die n line stay active except for maybe a 1/10th of a second on a work restart(flush & update). So, unless theres concrete proof of Titan's having horrible work restart delays ... right now its all a myth as per my asic/core work watching method.