Pages:
Author

Topic: python OpenCL bitcoin miner - page 34. (Read 1239035 times)

full member
Activity: 126
Merit: 100
February 13, 2011, 04:50:22 PM
What are good settings for a HD 5970? I just added -v -w 128 and it increased each GPU from 270MHash to ~280MHash.
That's about as fast as you'll get fiddling around with the flags, in my experience.
sr. member
Activity: 302
Merit: 250
February 13, 2011, 01:30:00 PM
I'm getting 340000 khash/s on each of my 6970s.  Running Stream SDK 2.3... I will see about downgrading in the near future since I have read 2.2 is faster.

My main question is each of the instances of poclbm is maxing out a core.  I have noticed if I max out all 4 cores with prime95, my khash/s does not increase, so it seems the miner is just wasting cpu cycles?  Is there something I can do to address this or is it a problem with the program?

Win 7 64bit
Cats 11.1a
AMD Stream 2.3
Dual 6970s

I personally run it on Win 7 64bit, but with cat 10.12 and Stream SDK 2.2 and CPU utilization is pretty low, actually close to 0% Could you please try with Stream 2.2 and post results?

m0mchil, I could not get the miner to work on my Win 7 64b setup with cats 10.12 and ATI Stream 2.2. It works fine on 2.3, however when I downgrade to 2.2 ( I also tried after a fresh reformat a few days ago ) the miner starts out at full speed for a second or two, then quickly degrades to like 5,000khash/s, and the miner process(es) crash a few seconds later.

Any way around this?
newbie
Activity: 47
Merit: 0
February 13, 2011, 09:10:15 AM
What are good settings for a HD 5970? I just added -v -w 128 and it increased each GPU from 270MHash to ~280MHash.
newbie
Activity: 10
Merit: 0
February 13, 2011, 07:18:40 AM
Radeon HD 5870

ATI Stream 2.3k SDK:           290,000 kHash/s
Downgraded to Stream 2.2k:  312,000 kHash/s
use "-v" and "-w 128"           324,000 kHash/s

thanks m0mchil for your work.
legendary
Activity: 1596
Merit: 1100
February 13, 2011, 02:17:56 AM

Feature request:  support HTTP/1.1 persistent connections, to maintain the TCP connection across 'getwork' JSON-RPC requests, when the server supports it.

That makes JSON-RPC much more network-efficient.  Hopefully bitcoind will be upgraded to support this, soon, and I believe slush's server already supports it.
sr. member
Activity: 406
Merit: 250
February 13, 2011, 12:35:28 AM
if my gpu finds a block will the 50 btc be added to my bitcoin wallet.

If you are solo mining, yes. If you are pooled mining, the pool operator will receive the 50BTC and will distribute them in the manner agreed upon.
full member
Activity: 133
Merit: 100
February 13, 2011, 12:33:15 AM
if my gpu finds a block will the 50 btc be added to my bitcoin wallet.

also poclbm says ip 27.0.0.1. but bitcoin is accepting from ip 127.0.0.1 did the first 1 just get cut off in the command line or is something wrong.
sr. member
Activity: 406
Merit: 250
February 13, 2011, 12:32:08 AM
Hi xenon481,

have you got a miner running on the xenon XCGPU processor?

If so what kind of Mhash/s are you seeing?

thnx.

No, I am not running that.
hero member
Activity: 726
Merit: 500
February 13, 2011, 12:25:58 AM
when i run the poclbm.exe iam able to get to the point when it shows my khash/s which is 308775, but in bitcoin it says only 10762khash/s is this how it is supposed to look.

The 308775 is your GPU (m0mchil's program) and the 10762 is your CPU (bitcoin client).  You'd be better off pool mining with the CPU.
hero member
Activity: 726
Merit: 500
February 13, 2011, 12:24:07 AM
I received a message "accepted" a couple of hours ago. Does that mean I found a block? Nothing has appeared in my wallet, though. Unfortunately I rebooted the PC by now, so I can't remember the value associated with the message - unless it is in some log file?

You will receive the 50 BTC once the block has been confirmed 100 times.  Less than a day usually.
full member
Activity: 133
Merit: 100
February 12, 2011, 11:40:34 PM
when i run the poclbm.exe iam able to get to the point when it shows my khash/s which is 308775, but in bitcoin it says only 10762khash/s is this how it is supposed to look.
legendary
Activity: 3920
Merit: 2349
Eadem mutata resurgo
February 12, 2011, 09:44:54 PM

Hi xenon481,

have you got a miner running on the xenon XCGPU processor?

If so what kind of Mhash/s are you seeing?

thnx.
newbie
Activity: 47
Merit: 0
February 12, 2011, 08:22:53 PM
I received a message "accepted" a couple of hours ago. Does that mean I found a block? Nothing has appeared in my wallet, though. Unfortunately I rebooted the PC by now, so I can't remember the value associated with the message - unless it is in some log file?
hero member
Activity: 726
Merit: 500
February 12, 2011, 04:30:23 PM
I upgraded about 2 Ghash/s worth of miners a couple days ago with the latest version and haven't found anything since either.  Maybe it's just a spell of bad luck.  I'll update the thread if anything manifests.

Finally got a block, on my slowest GPU, a 5770 running about 190 Mhash/s.  This is the first block in three days.  The 95th percentile for my cluster is about 2 days.  Has anyone kept records and compared ideal generation rate to actual rate over a longer period of time?  I'm going to start doing so.
member
Activity: 60
Merit: 10
February 12, 2011, 01:50:22 PM
I'll test 2.2 and see if it fixes the cpu usage problem soon.

Another question, how often do you guys get invalid or stale blocks?  I'm hooked up with a mining pool.  It seems to me I get 1/25 blocks as stale or invalid.  Is this normal? or should I look into stability issues with my video cards?  They are not overclocked and I haven't had any issues with them gaming.
sr. member
Activity: 302
Merit: 250
February 12, 2011, 01:24:00 PM
It's not so much that I'm complaining or surprised. I just find it REALLY odd that the first day I mined Bitcoin on like 1/22 or so, I found 4 blocks. Then after that, (once a version was upgraded) I found nothing...

Variance.

I was watching Slush's pool yesterday while it was running ~60GHash/sec. At that rate, the pool should have been solving a block every ~30 minutes and should have had a 95% chance to have found one within ~1.5hrs. But, there was one that took over 5hrs to solve.

If you average 625MHash/sec solo mining running 24/7, (at the current difficulty) you should average ~2 days per block. But the variance is a killer. That 5hrs solve for Slush's pool yesterday? That's 10x longer than the average. For you, that level of variance would have taken ~20 days.

Okay, is there a way to get around this in solo mining?

Changing the getwork rate or anything? Just wondering if theres anyway to dump the workload if it's been working on a block for 'too long'

Not sure if that'd even make sense, but it seems like it would be a good idea
donator
Activity: 826
Merit: 1060
February 12, 2011, 01:05:22 PM
Just look at Bitcoin Monitor and see the variance in block generation.
sr. member
Activity: 406
Merit: 250
February 12, 2011, 12:56:58 PM
It's not so much that I'm complaining or surprised. I just find it REALLY odd that the first day I mined Bitcoin on like 1/22 or so, I found 4 blocks. Then after that, (once a version was upgraded) I found nothing...

Variance.

I was watching Slush's pool yesterday while it was running ~60GHash/sec. At that rate, the pool should have been solving a block every ~30 minutes and should have had a 95% chance to have found one within ~1.5hrs. But, there was one that took over 5hrs to solve.

If you average 625MHash/sec solo mining running 24/7, (at the current difficulty) you should average ~2 days per block. But the variance is a killer. That 5hrs solve for Slush's pool yesterday? That's 10x longer than the average. For you, that level of variance would have taken ~20 days.
donator
Activity: 826
Merit: 1060
February 12, 2011, 12:38:46 PM
I just find it REALLY odd that the first day I mined Bitcoin on like 1/22 or so, I found 4 blocks. Then after that, (once a version was upgraded) I found nothing...
Generation is hugely variable. I have seen statistics for seven similar generators. In the same timespan they generated 1, 2, 4, 0, 7, 0 and 0 blocks. Go figure!
sr. member
Activity: 302
Merit: 250
February 12, 2011, 12:07:35 PM
There was a version which had a problem, generally not calculating correct hashes above first 32 bits. But with 20110204 I was able to find blocks on test net (which had significantly higher than 32 bits difficulty by the time).

Do you at least get 'invalid or stale' message? This should show up from time to time even if miner is broken. Bitcoin will reject the solution. But I really can't imagine other reason for not seeing anything, not even 'invalid' message - the one and only reason to not see any message for a long time is difficulty.

I haven't ran it 24/7 due to workstation limitations, Ihave to reboot at least once a day.

It's just that I ran for like 5 or 6 days for like 22 out of 24h in the day and got nothing.

I'm using Win7 64 with latest Cats and Stream 2.3.

It's not so much that I'm complaining or surprised. I just find it REALLY odd that the first day I mined Bitcoin on like 1/22 or so, I found 4 blocks. Then after that, (once a version was upgraded) I found nothing...

Is there a way you can link the version from 2 or 3 revisions ago I can test with? It's the one from late Janurary
Pages:
Jump to: