Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 772. (Read 4382797 times)

Agree for a quick test that works for a long block. But to be sure or for short block you need to look at logs.

Personally, I use the U: field in cgminer to calculate my approx submitted shares. It's in submitted/min rate.

OK so we agree on everything. So there was a problem. Block confirmed and missing shares according to log.

Exactly the opposite ('confirmed' is after 100 blocks), but let's stop here. There's no point in arguing.

So you are saying the delay is still in effect when block is confirmed? No way... You haven't read all or you have real problems with understanding English. Or you are trolling me.

I did read all your posts, but it seems we can't understand each other (sorry not a native English speaker, so it's probably my wording the reason).

What i am trying to say is: there is no problem, but only a delay (sometimes considerable) in calculating your shares. Then i have pointed several observations (and methods that can be used) in proving that.

Thanks but you are not talking to someone who has no clue what cgminer is. I have logs so I can do more then that. I can look into them and see what was going on. And when I see shares missing with no connection problems(we are not talking right now it as some time ago) that means that something was off and I was not the only one seeing that. So I relay do see what you would like to tell me unless you haven't read all posts.

For 2G miner Diff 2 is suggested, but as you have 2 miners/workers (especially if on different locations) and close to the minimum (of 2G), then Diff 1 may be in fact better.
After a few hours (or a full round) of mining pay attention to the top line of CGMiner:
'... | A:XXX  R:YY  HW:0  U:Z.Z/m'
XXX - the number of shares submitted = should match the number of shares registered from the pool (1)
Z.Z/m - average shares per minute = should match you 'Total:' shares when multiplied to the number of minutes shown (1)

(1) -  if you haven't mined for another one, because of connection problems.

It was startup... And it goes over all pools and connect to all of them. So there is a lot of idle time. And no it is difficulty 1 as log suggest... There are a 468,7M miner and 1.623G miner... Just in case. And running diff 1.

His Diff is 1 and can't be lower, so your post is useless in this case even if it is correct as statement.

He said, he is mining with ~2GH/s (or 'From my 460 miner' it's 460MH/s ?), which suggests Diff 2 as optimal, but 1 share every 20 sec is actually ~200MH/s ?!?

Did you ever used cgminer?  [2013-05-05 18:02:13] Accepted ee29bdaf Diff 1/1 GPU 0 pool 0 <--- diff 1 accepted... What dose that tells you?

Oh, guess i was off on that. Now i know something that i didn't before. thanks.

I'm not sure if this Diff is the same as Difficulty as specified on your account (for each miner). If that's the same thing - then that's probably a problem for you. The issue is that if you assign a very high difficulty for your miner you pretty much tell the server that it will do a rather high number GH/s and your worker will report once all of that work has been completed - that's to minimize traffic. (I'm over-simplifying the explanation but that's roughly the idea)

The issue is that if you say you'll do many GH/s but you do much less then you may have a lot of unreported work at the end of the round - resulting in shares that were never reported.

See if a block is off, move the logs to my computer and look when it was started and when it was ended, copy to excel, do some searches if I got disconnected or move to other pool and then see last call number... See if shares match up and then see the speed of last 200 shares if it was off. This is my method... I'm thinking of creating macro for that...

EDIT: remove stratum detected new block and so on

That's why I was curious as to how you came about your numbers.  It's hard to be precise when counting shares/block unless you do a lot of work or have some sort of reporting or logging features that I've not seen in the past...

CPU miners where also worthless in less than an year, then the same for GPUs ... it's just as it is for the mining and ASICs are designed to do only that.

@ Lucko

Then it means it could take 70+.
I doubt they get into the next block, because that would brake the score calculation - they enter the database later, but in the exact place and when submitted are triggering recalculation, which explains the jumps up and down for the last few rounds (and unconfirmed rewards), but will never happen for the 'confirmed' ones.

EDIT: Just look at the top for accepted shares "| A:xxx" no need to count them for 1h

Its been a long time since ISA VGA cards were on market.  For 5GH/s ASIC it may last only a year or so before its worthless.

Hire is just start of one... From my 460 miner... Only 2 minutes from start...

 [2013-05-05 17:58:19] Started cgminer 2.11.4
 [2013-05-05 17:58:20] Probing for an alive pool
 [2013-05-05 17:58:22] Switching to pool 5 http://eu-stratum.btcguild.com:3333 - first alive pool
 [2013-05-05 17:58:22] Pool 4 slow/down or URL or credentials invalid
 [2013-05-05 17:58:26] Switching pool 3 http://api.bitcoin.cz:8332 to stratum+tcp://stratum.bitcoin.cz:3333
 [2013-05-05 17:58:27] Accepted 84459d1b Diff 1/1 GPU 0 pool 5
 [2013-05-05 17:58:31] Accepted 273e278b Diff 6/1 GPU 0 pool 5
 [2013-05-05 17:58:34] Accepted ea70fa7a Diff 1/1 GPU 0 pool 5
 [2013-05-05 17:58:37] Pool 2 http://stratum3.bitcoin.cz:3333 alive
 [2013-05-05 17:58:37] Switching to pool 2 http://stratum3.bitcoin.cz:3333
 [2013-05-05 17:58:37] Pool 1 http://stratum2.bitcoin.cz:3333 alive
 [2013-05-05 17:58:37] Switching to pool 1 http://stratum2.bitcoin.cz:3333
 [2013-05-05 17:58:37] Pool 0 http://stratum.bitcoin.cz:3333 alive
 [2013-05-05 17:58:37] Switching to pool 0 http://stratum.bitcoin.cz:3333
 [2013-05-05 17:58:56] Accepted 4a78a96e Diff 3/1 GPU 0 pool 0
 [2013-05-05 17:58:56] Stratum from pool 0 requested work restart
 [2013-05-05 17:59:16] Accepted b88a98d6 Diff 1/1 GPU 0 pool 0
 [2013-05-05 17:59:33] Accepted 01c758f4 Diff 143/1 GPU 0 pool 0
 [2013-05-05 17:59:36] Accepted 6ad80539 Diff 2/1 GPU 0 pool 0
 [2013-05-05 18:00:19] Accepted c32e9a34 Diff 1/1 GPU 0 pool 0
 [2013-05-05 18:00:55] Accepted 9c4d1901 Diff 1/1 GPU 0 pool 0
 [2013-05-05 18:01:09] Accepted 96a868f5 Diff 1/1 GPU 0 pool 0
 [2013-05-05 18:01:12] Accepted eb0123b1 Diff 1/1 GPU 0 pool 0
 [2013-05-05 18:01:25] Accepted b38ac9be Diff 1/1 GPU 0 pool 0
 [2013-05-05 18:01:34] Accepted 83d8a855 Diff 1/1 GPU 0 pool 0
 [2013-05-05 18:01:45] Accepted 42d9e41a Diff 3/1 GPU 0 pool 0
 [2013-05-05 18:01:53] Accepted b628c371 Diff 1/1 GPU 0 pool 0
 [2013-05-05 18:02:13] Accepted ee29bdaf Diff 1/1 GPU 0 pool 0

So for one hour block it would be extremely long...

I agree with that but when I posted 17878 it was 50+. And I have had 100 conformations and some still didn't check out... From what I can figure some shares got into next block... Since 0.0048 and 0.0062 were together...