When I added my first SP20 here it takes a while to build up to the hashrate I usually see on other pools much faster.
I'm not complaining I want to understand.
Is it because I do not set a difficulty? Starting at 1k should be perfect for an SP20 and be right there at 1.3 1.6 however you have it setup.
I restored an S3, new used fans, re-pasted the chips, put it on the pool and local hashrate was straight to 450ish right away.
I try to pay attention and I know I've read the pool shows what matters. Does it truly take that long at any pool, do I have a poor connection, or something set wrong?
Thanks
The diff itself makes no difference except on a few of the miners that have faulty firmware and need it to be above some value.
Some of the bitmain miner firmware versions have a minor issue that if the diff is a power of 2, then best share stays on zero.
If you have higher diff, then you'll expect to submit fewer shares, if you have lower diff then you'll expect to submit more shares.
The statistical expectation is that
High x Few ~= Low x Many ... and you can't pick a different diff to expect to get better results.
One thing to look at on the pool is the Invalid % of the worker.
If the miner gets a lot of invalids when it starts, it may take a while to get up to speed.
Another thing to look at is the API of cgminer - though some of the manufacturer hacked versions of cgminer don't report that correctly.
Anyway, the API may also show you what is going on with the miner.
Lastly, there is also a simple calculation you can do with any cgminer if you can access the API summary.
DifficultyAccepted * 2^32 / ElapsedThis is the paid hash rate at the pool - the shares the pool accepted over the time since cgminer started.
Edit: cgminer miner.php the "Kano" button shows that value
