Bitcoin Forum
December 11, 2016, 02:28:28 AM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: 3% Efficiency with CGMINER  (Read 3695 times)
eatnumber1
Newbie
*
Offline Offline

Activity: 1


View Profile
August 11, 2011, 10:42:12 AM
 #1

Is this normal? Granted I'm new to bitcoin mining, but I was hoping for ~90% efficiency, not 3!

Code:
Average hashrate: 10.9 Megahash/s
Queued work requests: 3423
Share submissions: 107
Accepted shares: 105
Rejected shares: 2
Reject ratio: 1.9
Hardware errors: 0
Efficiency (accepted / queued): 3%
Utility (accepted shares / min): 0.14/min

Discarded work due to new blocks: 3464
Stale submissions discarded due to new blocks: 0
Unable to get work from server occasions: 1
Work items generated locally: 4389
Submitting work remotely delay occasions: 0
New blocks detected on network: 72

Pool: http://mineco.in:3000
 Queued work requests: 3350
 Share submissions: 105
 Accepted shares: 103
 Rejected shares: 2
 Reject ratio: 1.9
 Efficiency (accepted / queued): 3%
 Discarded work due to new blocks: 3396
 Stale submissions discarded due to new blocks: 0
 Unable to get work from server occasions: 1
 Submitting work remotely delay occasions: 0

Pool: http://uswest.btcguild.com:8332
 Queued work requests: 71
 Share submissions: 2
 Accepted shares: 2
 Rejected shares: 0
 Reject ratio: 0.0
 Efficiency (accepted / queued): 3%
 Discarded work due to new blocks: 68
 Stale submissions discarded due to new blocks: 0
 Unable to get work from server occasions: 0
 Submitting work remotely delay occasions: 0

Summary of per device statistics:

 CPU 0: [2.7 / 2.7 Mh/s] [Q:724  A:22  R:1  HW:0  E:3%  U:0.03/m]
 CPU 1: [2.7 / 2.7 Mh/s] [Q:866  A:26  R:0  HW:0  E:3%  U:0.04/m]
 CPU 2: [2.8 / 2.8 Mh/s] [Q:763  A:20  R:1  HW:0  E:3%  U:0.03/m]
 CPU 3: [2.8 / 2.8 Mh/s] [Q:924  A:37  R:0  HW:0  E:4%  U:0.05/m]
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481423308
Hero Member
*
Offline Offline

Posts: 1481423308

View Profile Personal Message (Offline)

Ignore
1481423308
Reply with quote  #2

1481423308
Report to moderator
Minerd
Newbie
*
Offline Offline

Activity: 3


View Profile
August 11, 2011, 11:05:34 AM
 #2

Looks about right to me. CPU's are very slow at hashing compared to GPU's. If it recieves a Long-poll on the network telling it a block has been solved before it has completed the current share it will cause it to drop that share and any that are in the queue and ask the pool for more work. Your stale submissions are around 1.9% which is acceptable. You should consider utilising your GPU if possible it will be a lot more efficient.
Axez D. Nyde
Jr. Member
*
Offline Offline

Activity: 31


View Profile
August 11, 2011, 11:14:20 AM
 #3

Quote
Utility (accepted shares / min): 0.14/min

That's approximately 7 Minutes for ONE accepted share. If you watch the bitcoin monitor for a while ... Cheesy ... then you may notice that's almost the rate blocks get generated.
Also, a block per 10 minutes is the target generation rate regulated by the difficulty setting.

Anyway, I'm not good with statistics, but the current difficulty, 1888786.7053531, is the number of shares you need to calculate on average to find a block. So CPU mining is really pointless at this difficulty level. Maybe if everyone was to turn off their GPUs...
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!