L3 Miner Very Inefficient

[dog1965]

what it does is increases my effeciency and my share rate and reduces my stales also makes my higher profit as well. these commands you would use on grapgic card mining but they also work on any type antminer or asic miner as welll. you really have to play with these numbers because every body's connect speed latency ext is different you have to find the best numbers that work for you.

--scan-time|-s <arg> Upper bound on time spent scanning current work, in seconds (default: -1)
--expiry|-E <arg> Upper bound on how many seconds after getting work we consider a share from it stale (default: 120)
--queue|-Q <arg> Minimum number of work items to have queued (0+) (default: 1)

try playing with these settings they work good on this site.

these work for me very well yours might be different.

--scan-time=7
--expiry 28

as I said you have to play with the values.

I am getting shares and blocks much quicker.

[dog1965]

I got those numbers from this link https://github.com/sgminer-dev/sgminer/issues/22

also I see alot of people use 7/28 as i posted erlier for alt coins alot of people are using it and it works great for me as well I agree with you on alot of mis-info floating around but these numners really work I dont know why I am still trying to figure it out.

did you use scp in winscp when you connected also run it as administrator as well. it saves a verification file when you first time run it let it save that file.

I get into my L3+ and MY S9 with winscp no problen.

[hashingpro]

Dog what is the address you use to mine on prohashing site?
Whats the pool address line say you use on your miner to connect in?

And you know that article was posted back in 2014 right?
Is there any more recent up to date info on those settings?
Like from the last year?

[micca410evo]

You could search in this forum for L3 share issues, but yeah... imma fool

TS already said, adjusting some pw arguments solved one and another. Watching pool issues is a good one, sometimes there is an (couple of) hour(s) efficiency issues to take in account.

@TS: i'm not sure if worker history charts are working for you, but you can see rejected/accepted hashrate longer term (2 weeks or something)

[megaquake]

Difficulty will not affect efficiency, the issue is pool sided

[mrSnipes]

How do you guys determine which difficulty-setting to use ? I always see different numbers for that param but no explanation on how to come up with it.

[GregoryGHarding]

How do you guys determine which difficulty-setting to use ? I always see different numbers for that param but no explanation on how to come up with it.

trial and error

[dog1965]

Dog what is the address you use to mine on prohashing site?
Whats the pool address line say you use on your miner to connect in?

And you know that article was posted back in 2014 right?
Is there any more recent up to date info on those settings?
Like from the last year?

I use....

stratum+tcp://prohashing.com:3333

1d3h53m10s elapsed
502.422 MH/S(RT)
499.99 MH/S(avg)
84 FoundBlocks
108,016 LocalWork
6.72 Utility
457,585.18 WU
636823054902 BestShare

I wish I could post a image of my miner screen but I dont know how or even if I can.

My diff is set to 65536 along with the expiry and scantime values I posted before. I know is an old post but its working for me. You can play with the values on --scantime and --expiry to see wich ones work best for you but try to keep it around 28 and 7 as i posted before and use 65536 as your diff works best for me. I make $42.67 usd in a 24 hour period with these settings and payout on one coin only will not use more than one coin payout.

[dog1965]

what do you guys think about this. my settings maake $42.00 usd a day.



set you diff to 65536 and....

--scan-time=7
--expiry 28

set these settings using winscp or putty like I posted before.




I think thats proof enough.

[micca410evo]

Looking good dog, doesn't care much for others though since every miner acts/reacts different. I got 2 the same Alchemist miners and one works better at 16384 and the other on 32768 or 65536.