Titan work restart time ...

gaanthony wrote:0.8967% on one and 1.5226% on another.

quite a weird difference, anything configured differently between them? and whats bfgminer runtime?

Mines been consistent 1.2% for the past 35hrs of bfgminer runtime.

Guess this is too much of a oranges vs apples comparison cuz different ping times to servers , bfgminer runtime , actual coins mined ... etc etc..

Mining Status

Miner Status Running BFGMiner (pid=14421)
Last Checked Sat Jul 30 06:49:24 UTC 2016
BFGminer Ver bfgminer 5.4.2
BFGMiner Up Time 219.38 Hrs
20s Hash Rate 432.558 Mh/s
Avg Hash Rate 437.207 Mh/s
WU 6
Difficulty Accepted 80346
Accepted Shares 20754
Pool Rejected 0.8834%
Error Rate 0.5249%
Best Share 234084

I need to check and tweak this one as one die was running with 18% hardware error rate. Also this one has a cube with one dead die set to off.
Miner Status Running BFGMiner (pid=1400)
Last Checked Sat Jul 30 06:49:53 UTC 2016
BFGminer Ver bfgminer 5.4.2
BFGMiner Up Time 219.40 Hrs
20s Hash Rate 399.958 Mh/s
Avg Hash Rate 408.853 Mh/s
WU 5
Difficulty Accepted 75229
Accepted Shares 19473
Pool Rejected 1.5185%
Error Rate 1.4136%
Best Share 89651

What h value and vardiff?
Also, I wonder if error rate is included in rejects ... I've never figured that out lol! Some device drivers include it and others dont.
Your 2 Titans %'s would seem to indicate it does but... it may be just coincidental.

d=262144. No h value set.

gaanthony wrote:d=262144. No h value set.

Hrm... ok thats kinda nutty =P
You must LOVE variance =)

GenTarkin, have you had any more progress on getting Titans to work well with Prohashing? I really love the idea of this site but switched back to straight LTC last year because my stock firmware kept hanging. Would love to try your code but it's hard to justify at the price (sorry). I might be convinced though if somehow you and prohashing could make the Titans work ideally to flush old work. Do you suspect your firmware fixes any major slowing issues so that ProHashing will just work better with it?

ltc2084 wrote:GenTarkin, have you had any more progress on getting Titans to work well with Prohashing? I really love the idea of this site but switched back to straight LTC last year because my stock firmware kept hanging. Would love to try your code but it's hard to justify at the price (sorry). I might be convinced though if somehow you and prohashing could make the Titans work ideally to flush old work. Do you suspect your firmware fixes any major slowing issues so that ProHashing will just work better with it?

Well according to the timing shown in bfgminer with full work flush & restarts, my code slims off at least 1-2s total off a 4 cube titan.
These improvements are not part of my firmware. They most likely will never be due to licensing conflicts w/ bfgminer.
That being said, its not like Titans are BAD with this pool, they just dont perform as optimally as fast work restarting ASICs, the performance loss is negligible tho, if blocks(full work restarts) average a couple/few seconds apart and the pool has a quite lenient reject policy then Titans easily perform at 100%. Its when you are switching between blocks of different coins every 1second or lower consistantly and the pool has a really strict reject policy that the Titan cant achieve maximum useful throughput.

Regarding the price of my firmware, many others would strongly disagree that its not worth the price =P
Consider you would ROI on the firmware in just right around a week(half that if you bought more than 1 license) and all the features / protections / power usage optimization and much more I've built into it...

But yeah, I will update this thread if I ever decide to make my bfgminer titan driver changes public.