Author

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

newbie
Activity: 49
Merit: 0
FYI (for coblee in special)
3h and a bit into work
about a third of coblee's hash rate but ~half of his shares/minute
Code:
 [(5s):730.5  (avg):734.3 Mh/s] [Q:3332  A:2868  R:10  HW:0  E:86%  U:9.88/m]
 TQ: 5  ST: 5  LS: 0  SS: 0  DW: 91  NB: 36  LW: 41  LO: 13  RF: 0  I: 9
 Block 00014b8ee2314e0f883f034dff1e4a0f  started: [2011-07-17 15:08:25]
--------------------------------------------------------------------------------
 GPU 0: [372.6 Mh/s] [Q:1660  A:1442  R:5  HW:0  E:87%  U:4.97/m]
 GPU 1: [361.9 Mh/s] [Q:1619  A:1426  R:5  HW:0  E:88%  U:4.91/m]


setting intensity to higher values gives me more hashes/second but less shares/minute
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I was getting 760 shares in 35 minutes with cgminer. With my previous poclbm, I got 960 shares in 35 minutes. So I'm definitely returning less shares with cgminer at I 14. I will change it to I 8/9 and test it. But I won't have time to do that for until maybe 8 hours later. I will report back what I find out.

Is it possible that I'm doing that many hashes but not reporting back to the pool all the hashes I found? Are some hashes lost when intensity is set so high? It would be nice if that information is captured somewhere.

No hashes should be lost. It doesn't work that way. It queues everything asynchronously for upload in a separate thread that has nothing to do with the hashing so everything eventually gets pushed to the server if it was found.
donator
Activity: 1654
Merit: 1351
Creator of Litecoin. Cryptocurrency enthusiast.
I was getting 760 shares in 35 minutes with cgminer. With my previous poclbm, I got 960 shares in 35 minutes. So I'm definitely returning less shares with cgminer at I 14. I will change it to I 8/9 and test it. But I won't have time to do that for until maybe 8 hours later. I will report back what I find out.

Is it possible that I'm doing that many hashes but not reporting back to the pool all the hashes I found? Are some hashes lost when intensity is set so high? It would be nice if that information is captured somewhere.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Because your efficiency is low. The pool reports back what it thinks your hash rate is based on the number of accepted shares you return.

Efficiency is just accepted share divided by requested work. A low efficiency just means that cgminer is calling more getworks than necessary. The hashrate should represent how many accepted share I generate.

So the question still stands: why is cgminer reporting a higher hashrate? How is it calculating the hashrate if not using the accepted shares?

Another question is what does the intensity actually mean? I'm running on a headless dedicated miner. Why not set it to 14? And why not 9 instead of 8?

Thanks!
Efficiency 14 can take up to 15 seconds to return data from the GPU. That's a long time to not have reported back any shares. So it usually is less efficient to give such a big chunk of work to the GPU at any one time without reporting in more frequently, even though in theory it would be nice to keep the GPU as busy as possible. It's the law of diminishing returns where there doesn't seem to be any benefit beyond 8 or 9, and it starts introducing more problems.

The hashrate reported by cgminer is just how many hashes it's doing. Nothing more, nothing less. The pool is reporting an estimated hash rate based on returns. If your returns are relatively low (for whatever reason) then the pool will think you're hashing less. Now as for why you're having a bad return, I'm not really sure, but the high intensity is only doing you harm. Are you putting in a big queue? Are you running lots of threads?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
1.2.7 regression on nvidia cards.

Mh/s are calculated, but after 1 hour no shares are submitted.

With the 1.2.6 binary nvidia cards function 100%.


win32 v1.2.7 still has problem with combined gpu+cpu mining and with cpu mining.


Yes sorry, noted and fixed in the git tree with nvidia mining. The poclbm kernel was not updated to match the other changes and has been since fixed. Need to do a git clean -f and get the latest tree to fix it. The cpu mining issue... I dunno yet but the c algorithm seems dodgy though the assembly 64 bit one works fine here. Too much else to look at.
donator
Activity: 1654
Merit: 1351
Creator of Litecoin. Cryptocurrency enthusiast.
Because your efficiency is low. The pool reports back what it thinks your hash rate is based on the number of accepted shares you return.

Efficiency is just accepted share divided by requested work. A low efficiency just means that cgminer is calling more getworks than necessary. The hashrate should represent how many accepted share I generate.

So the question still stands: why is cgminer reporting a higher hashrate? How is it calculating the hashrate if not using the accepted shares?

Another question is what does the intensity actually mean? I'm running on a headless dedicated miner. Why not set it to 14? And why not 9 instead of 8?

Thanks!
member
Activity: 145
Merit: 10
1.2.7 regression on nvidia cards.

Mh/s are calculated, but after 1 hour no shares are submitted.

With the 1.2.6 binary nvidia cards function 100%.


win32 v1.2.7 still has problem with combined gpu+cpu mining and with cpu mining.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Because your efficiency is low. The pool reports back what it thinks your hash rate is based on the number of accepted shares you return.
donator
Activity: 1654
Merit: 1351
Creator of Litecoin. Cryptocurrency enthusiast.
Your efficiency is particularly low. That may be the result of setting the intensity too high. Drop it from 14 to 8.

I've tried 8 and I was not getting good hashrate. Would 9 work?
Why would the hashrate reported here not be accurate versus what the pool sees?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Your efficiency is particularly low. That may be the result of setting the intensity too high. Drop it from 14 to 8.
donator
Activity: 1654
Merit: 1351
Creator of Litecoin. Cryptocurrency enthusiast.
And after I stopped it, here's the summary:

Code:
Summary of runtime statistics:

Started at [2011-07-17 04:12:34]
Runtime: 0 hrs : 35 mins : 37 secs
Average hashrate: 2255.4 Megahash/s
Queued work requests: 1533
Share submissions: 765
Accepted shares: 760
Rejected shares: 5
Reject ratio: 0.7
Hardware errors: 0
Efficiency (accepted / queued): 50%
Utility (accepted shares / min): 21.39/min

Discarded work due to new blocks: 18
Stale submissions discarded due to new blocks: 0
Unable to get work from server occasions: 4
Work items generated locally: 13
Submitting work remotely delay occasions: 0
New blocks detected on network: 5

Summary of per device statistics:

 GPU 0: [376.2 Mh/s] [Q:254  A:108  R:0  HW:0  E:43%  U:3.08/m]
 GPU 1: [375.7 Mh/s] [Q:254  A:143  R:1  HW:0  E:57%  U:4.05/m]
 GPU 2: [375.7 Mh/s] [Q:254  A:116  R:1  HW:0  E:46%  U:3.27/m]
 GPU 3: [375.7 Mh/s] [Q:253  A:123  R:2  HW:0  E:49%  U:3.51/m]
 GPU 4: [376.2 Mh/s] [Q:254  A:128  R:0  HW:0  E:50%  U:3.60/m]
 GPU 5: [376.2 Mh/s] [Q:254  A:142  R:1  HW:0  E:56%  U:4.00/m]
donator
Activity: 1654
Merit: 1351
Creator of Litecoin. Cryptocurrency enthusiast.
I have a weird problem. cgminer is reporting a hashrate that is a bit better than what I had before. BUT my pool (arsbitcoin) is reporting something much lower after I switched. And I did wait 30 minutes to make sure since the stats are for the last 10 minutes.

Here's what cgminer is showing:

Code:
 cgminer version 1.2.7 - Started: [2011-07-17 04:12:34]
--------------------------------------------------------------------------------
 [(5s):2201.5  (avg):2249.4 Mh/s] [Q:1380  A:690  R:2  HW:0  E:50%  U:21.43/m]
 TQ: 6  ST: 6  LS: 0  SS: 0  DW: 13  NB: 4  LW: 13  LO: 4  RF: 0  I: 14
 Connected to http://arsbitcoin.com:8344 as user ChocoboLee.12
 Block 0001aa09e56fefcc16d9935ed9e1e9b6  started: [2011-07-17 04:30:40]
--------------------------------------------------------------------------------
 GPU 0: [376.3 Mh/s] [Q:230  A:101  R:0  HW:0  E:44%  U:3.15/m]
 GPU 1: [376.3 Mh/s] [Q:229  A:127  R:0  HW:0  E:56%  U:3.97/m]
 GPU 2: [375.7 Mh/s] [Q:230  A:110  R:0  HW:0  E:49%  U:3.52/m]
 GPU 3: [375.7 Mh/s] [Q:229  A:115  R:1  HW:0  E:50%  U:3.58/m]
 GPU 4: [376.3 Mh/s] [Q:230  A:112  R:0  HW:0  E:49%  U:3.50/m]
 GPU 5: [376.3 Mh/s] [Q:230  A:125  R:1  HW:0  E:56%  U:3.99/m]
--------------------------------------------------------------------------------

Here's what my pool is saying:

ChocoboLee.12      Y   1460

Any ideas? I've been running this for 35 minutes. Can someone do a quick calculation to see if the amount of accepted shares is correct for my hashrate?
full member
Activity: 126
Merit: 100
Ideal would be to add a flag to disable the gpu mining.
eg
-g 0 would disable gpu mining.

cgminer.exe -o http://localhost:8332 -u username.1 -p 1234 -t 4 -g 0

could then be used to force only cpu mining with 4 threads..

why would one want todo this: if u wanted to play a game or use the gpus for something else.. my cpu averages 40Mh/s

currently
i use bitcoin-miner.exe for cpu mining
Wow, do you have some dual xeon or something? 40 megahashes for a cpu is quite a lot.
member
Activity: 145
Merit: 10
Ideal would be to add a flag to disable the gpu mining.
eg
-g 0 would disable gpu mining.

cgminer.exe -o http://localhost:8332 -u username.1 -p 1234 -t 4 -g 0

could then be used to force only cpu mining with 4 threads..

why would one want todo this: if u wanted to play a game or use the gpus for something else.. my cpu averages 40Mh/s

currently
i use bitcoin-miner.exe for cpu mining
full member
Activity: 126
Merit: 100
In that case, wouldn't you be better just running bitcoin -gen ? See http://forum.bitcoin.org/index.php?topic=2356.0
Sorry, but the integrated CPU miner in the older builds is much slower than say CGMiner's 4way algorithm or Ufasoft's SSE2 optimization.
hero member
Activity: 588
Merit: 500
The windows build has gpu mining built into it. You cannot do plain cpu mining on the generic windows build unless you build it without GPU mining support.

I didn't realise that. The previous version I had - the on that had "Generate Coins" in a menu used the CPU to mine.

If the current Windows version really does use the GPU to mine, then why should I be using CGMiner? (Can't test at the moment due to PSU issue.) http://www.weusecoins.com/mining-guide.php seems to imply that GPU mining is not native to the Windows Bitcoin Application.

The Windows build of cgminer has gpu mining built into it.

Mining is being phased out from the official Bitcoin client.
member
Activity: 77
Merit: 10
EDIT: Me == Comprehension Fail Sad Thanks for corrections below.

I didn't realise that. The previous version I had - the on that had "Generate Coins" in a menu used the CPU to mine.

If the current Windows version really does use the GPU to mine, then why should I be using CGMiner? (Can't test at the moment due to PSU issue.) http://www.weusecoins.com/mining-guide.php seems to imply that GPU mining is not native to the Windows Bitcoin Application. Likewise, https://en.bitcoin.it/wiki/FAQ#Why_was_the_.22Generate_coin.22_option_of_the_client_software_removed.3F makes no mention of this capability.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
The windows build has gpu mining built into it. You cannot do plain cpu mining on the generic windows build unless you build it without GPU mining support.
member
Activity: 77
Merit: 10
In that case, wouldn't you be better just running bitcoin -gen ? See http://forum.bitcoin.org/index.php?topic=2356.0
Jump to: