Author

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 540. (Read 5805546 times)

sr. member
Activity: 337
Merit: 252
Interesting. So this happens with eclipse as well. I don't have a solution but I have an interest Wink

The p2pool problem with this is taken care of, and perhaps I shouldn't keep beating a dead horse but I would like to take this oportunity to ask about how cgminer handles roll-ntime.

  • Under what circumstances does the miner call getwork? It seems to me that it happens more frequently than expected. If long polling is supported and "expire" is set to 120 it should be quiet and just keep rolling until 120 seconds has passed, should it not?
  • Second, if it sends a getwork request before there is new work to send, what is the pool to do? It can only roll ntime, but how can it tell by how much?
full member
Activity: 168
Merit: 100
hi!

i get a lot of duplicates on my ztex single and ztex quad.
almost 3.6% rejects and almost all from the duplicates.
it seems that the duplicate is send to the pool and then directly after that a new share.
anyone else got this with ztex boards? could it be a problem with the ztex bitstream that is included in cgminer or could it be
a problem in the ztex code in cgminer?

regards
streetuff

Code:
 cgminer version 2.4.4 - Started: [2012-07-07 17:27:29]
--------------------------------------------------------------------------------
 (5s):1082.1 (avg):1119.3 Mh/s | Q:33989  A:153800  R:5483  HW:0  E:452%  U:15.7/m
 TQ: 5  ST: 6  SS: 0  DW: 4569  NB: 1050  LW: 352379  GF: 0  RF: 15
 Connected to http://eu.eclipsemc.com:8337 with LP as user x
 Block: 0000053a1308f7e35d5a79fcb14bd2e9...  Started: [12:56:16]
--------------------------------------------------------------------------------
 [P]ool management [S]ettings [D]isplay options [Q]uit
 ZTX 0: 04A346FA61-1 | 216.00Mhz | 216.0/213.9Mh/s | A:29443 R:2482 HW: 280 U: 3.00/m
 ZTX 1: 04A3463533-1 | 232.00Mhz | 232.0/229.9Mh/s | A:31548 R: 531 HW: 861 U: 3.21/m
 ZTX 2: 04A3463533-2 | 232.00Mhz | 232.0/229.8Mh/s | A:31198 R:1123 HW:6762 U: 3.18/m
 ZTX 3: 04A3463533-3 | 224.00Mhz | 224.0/219.3Mh/s | A:30281 R: 696 HW:4770 U: 3.09/m
 ZTX 4: 04A3463533-4 | 228.00Mhz | 228.0/226.5Mh/s | A:31330 R: 651 HW:1697 U: 3.19/m
--------------------------------------------------------------------------------

 [2012-07-14 13:00:49] Accepted 94c671ec.7e43f506 ZTX 0
 [2012-07-14 13:00:50] Accepted c98039dc.e2dd193d ZTX 4
 [2012-07-14 13:01:00] Accepted 6484cbd6.79b30ba0 ZTX 0
 [2012-07-14 13:01:02] Rejected 6484cbd6.79b30ba0 ZTX 0  (duplicate)
 [2012-07-14 13:01:02] Accepted 689d56cf.ccd00e15 ZTX 0
 [2012-07-14 13:01:04] Accepted b78fb227.56cdcf2f ZTX 1
 [2012-07-14 13:01:06] Accepted 5fa20a11.3c04d2cf ZTX 1
 [2012-07-14 13:01:06] Accepted b0558cce.c80ceb95 ZTX 2
 [2012-07-14 13:01:08] Accepted 982cdbd7.b6e02789 ZTX 2
 [2012-07-14 13:01:10] Rejected 982cdbd7.b6e02789 ZTX 2  (duplicate)
 [2012-07-14 13:01:10] Accepted 056f515c.88895764 ZTX 2
 [2012-07-14 13:01:11] Accepted 2df142bf.e769ecab ZTX 3
 [2012-07-14 13:01:14] Rejected 2df142bf.e769ecab ZTX 3  (duplicate)
 [2012-07-14 13:01:14] Accepted 9f2edff7.331a4f6f ZTX 3
 [2012-07-14 13:01:19] Accepted da358746.bfc9a5f8 ZTX 2
 [2012-07-14 13:01:22] Accepted 469e33c7.eaf0d94e ZTX 0
 [2012-07-14 13:01:27] Accepted 22ae3128.bc906c00 ZTX 1
 [2012-07-14 13:01:28] Accepted ee3da833.ccaaec57 ZTX 1
 [2012-07-14 13:01:30] Accepted d31f7057.38c32fe0 ZTX 0
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
The odds are very easy to work out.
The chance of a single 1 difficulty share finding a block is 1 chance in D
Where D is the current difficulty.
(i.e. at the moment it is 1751454.5353407)
Of course you may have sent more 1 difficulty shares, but it won't count them, only the ones that are blocks.
So in reality the chances are even better.

Those are the odds of him finding a block. The odds of him finding a block where that magic share just happens to land on his 4th pool (solo) is quite a bit lower.
No, those are the odds that a share will be a block.
Any share.
legendary
Activity: 952
Merit: 1000
The odds are very easy to work out.
The chance of a single 1 difficulty share finding a block is 1 chance in D
Where D is the current difficulty.
(i.e. at the moment it is 1751454.5353407)
Of course you may have sent more 1 difficulty shares, but it won't count them, only the ones that are blocks.
So in reality the chances are even better.

Those are the odds of him finding a block. The odds of him finding a block where that magic share just happens to land on his 4th pool (solo) is quite a bit lower.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
The odds are very easy to work out.
The chance of a single 1 difficulty share finding a block is 1 chance in D
Where D is the current difficulty.
(i.e. at the moment it is 1751454.5353407)
Of course you may have sent more 1 difficulty shares, but it won't count them, only the ones that are blocks.
So in reality the chances are even better.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
A damn fine bazillion moment there, congrats!  Grin
legendary
Activity: 1876
Merit: 1000

I would just like to chime in about how cgminer sends misc shares to backup pools when not busy enough..


my 4th backup pool is solo (as i think all miners should have solo as final backup to protect network)

well cgminer found me this block https://blockchain.info/block-height/188729 a couple of hours ago.. what are the odds?


thank you clovias

My 5th backup is solo as well.  Though I haven't had any nice surprises like you just did.  Good for you.

I wonder how often this happens?  Anyone else find a block with a solo backup, I wonder?
Sam

Meni Rosenfeld I have seen around, answering questions and breaking down problems using complex math equations. Plenty more information would be needed, but if its possible to get an answer that is anywhere close, he's your guy. Recently I haven't come across his post as frequently as in the past, so I can't say he has the time or would even be willing to bother so...


Smiley, when i said "what are the odds"  it was meant as a rhetorical question...  its a bazillion to one!!
sr. member
Activity: 271
Merit: 250

I would just like to chime in about how cgminer sends misc shares to backup pools when not busy enough..


my 4th backup pool is solo (as i think all miners should have solo as final backup to protect network)

well cgminer found me this block https://blockchain.info/block-height/188729 a couple of hours ago.. what are the odds?


thank you clovias

My 5th backup is solo as well.  Though I haven't had any nice surprises like you just did.  Good for you.

I wonder how often this happens?  Anyone else find a block with a solo backup, I wonder?
Sam

Meni Rosenfeld I have seen around, answering questions and breaking down problems using complex math equations. Plenty more information would be needed, but if its possible to get an answer that is anywhere close, he's your guy. Recently I haven't come across his post as frequently as in the past, so I can't say he has the time or would even be willing to bother so...
legendary
Activity: 2492
Merit: 1473
LEALANA Bitcoin Grim Reaper
legendary
Activity: 3583
Merit: 1094
Think for yourself

I would just like to chime in about how cgminer sends misc shares to backup pools when not busy enough..


my 4th backup pool is solo (as i think all miners should have solo as final backup to protect network)

well cgminer found me this block https://blockchain.info/block-height/188729 a couple of hours ago.. what are the odds?


thank you clovias

My 5th backup is solo as well.  Though I haven't had any nice surprises like you just did.  Good for you.

I wonder how often this happens?  Anyone else find a block with a solo backup, I wonder?
Sam
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
legendary
Activity: 1876
Merit: 1000
I would just like to chime in about how cgminer sends misc shares to backup pools when not busy enough..


my 4th backup pool is solo (as i think all miners should have solo as final backup to protect network)

well cgminer found me this block https://blockchain.info/block-height/188729 a couple of hours ago.. what are the odds?


thank you ckolivas
sr. member
Activity: 337
Merit: 252
Every so often?  How much hash power do you have?  I'm seeing it all the time. 

After your hack, it was driving cgminer crazy "pool 2 not providing work fast enough" and diverting work to my backup pools.  p2pool was showing 1/2 my normal local hash power.  Just to make sure I wasn't doing something wrong with python, I put that line back in, and the dupe messages are back, but I'm back up to my normal local hashing power.
Ok ,all the time. Every few seconds.

I also never said it was the final solution, I said it was a short term fix for myself, and also a way to show if I was correct or not. The long term fix is probably to do it the other way around, but that require more than a one liner.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I have the same 2.4.4 and 2.5.0 causing massive problems
So went back to 2.4.3 which seems the only good version for now

Well that's rather non-specific. Information regarding hardware, command line options and debugging output run with "--verbose --debug -T" added might be helpful, as it says in the readme.
legendary
Activity: 1540
Merit: 1001
I think I know what's going on now. P2pool assumes that the miner will not roll ntime more than 10 seconds into the future (because it sets X-Roll-NTime to "expire=10"). At every work request it increments ntime by 12 and returns that.

cgminer doesn't respect the short expire, and rolls more than that. The two programs rolls independently and every so often they clash.

Every so often?  How much hash power do you have?  I'm seeing it all the time. 

After your hack, it was driving cgminer crazy "pool 2 not providing work fast enough" and diverting work to my backup pools.  p2pool was showing 1/2 my normal local hash power.  Just to make sure I wasn't doing something wrong with python, I put that line back in, and the dupe messages are back, but I'm back up to my normal local hashing power.

M
sr. member
Activity: 266
Merit: 250
The king and the pawn go in the same box @ endgame
Why is my AVG picking up a key logger when I download this?

Because some unscrupulous types have used the software in a malicious manner, and most AVGs have flagged it as malware of one form or another
newbie
Activity: 30
Merit: 0
Why is my AVG picking up a key logger when I download this?
newbie
Activity: 20
Merit: 0
2.5.0 seems to lock my fan speed at 63% on a 5870 of mine.
Automatic fan speed was turned off and I had sapphire set to 85% fan speed.
CGMiner wouldn't let me change it back to 85%.
Switched back to 2.4.1 and everything went back to normal.
hero member
Activity: 774
Merit: 500
Lazy Lurker Reads Alot
I have the same 2.4.4 and 2.5.0 causing massive problems
So went back to 2.4.3 which seems the only good version for now
legendary
Activity: 2702
Merit: 1468
Wrong.

...

Adjusting the abort time will not change the Hash rate unless there is something wrong either with the device or the computer's termios timing

If you are using 6.5 seconds to abandon jobs then you are aborting work too early.
However the reason you have to do that may be because you are using windows and the termios timing may not be accurate.

Well, in my setup, on Windows 7, abort time changes the hash rate.  the utility does not change much,  but hash rate is very sensitive to abort time.

Abort time lower than 8 seconds (80), increases the hash rate, higher than 8 secs (80) lowers the hash rate.

BTW, I've played with many timings, and 6.5 seconds abort time produce best utility rate.  I don't care about the hash rate reported by the cgminer. Number of submitted, valid shares per minute is what makes money.  So who cares if cgminer is reporting 410 or 210 Mh/s.  If utility is 5.35, I'm a  happy camper.

On Windows 7 (64bit), the new icarus code barely gets utility of 5. 
Kano, maybe you optimized too much for Unix and Windows performance took a hit.


Jump to: