python OpenCL bitcoin miner

[TurdHurdur]

I am 10......

Pretty good spelling and grammar for 10, better than some other users, hah.

Wonder if you'll get COPPA'd...

What do you want Bitcoins for, buying NX codes?

[foxmulder]

May be the port 8332 blocked in your router.
allow transmission incoming & outgoing in router configuration page.
port forwarding google for your router model.

Like i said it's already on dmz, my computer is fully exposed to the internet without any intermediatary , the listener not full time throwing up that error only occasionally, pocldbm can accept and send new work but i get lost on efficiency because of this lost 'packet'.

[marcus_of_augustus]

Sounds like it could be hardware related, try another router? Test your connection integrity, packets lost on a ping test?

[slush]

the listener not full time throwing up that error only occasionally

If it isn't permanent and the error appears only time to time, it might be problem on my side. Please PM me your pool login and time (ideally in UTC) when the problem appeared last time.

[fatcom4]

I am 10......

Pretty good spelling and grammar for 10, better than some other users, hah.

Wonder if you'll get COPPA'd...

What do you want Bitcoins for, buying NX codes?

1. Thanks, I have no idea why I type everything like this.
2. COPPA'd?
3. NX? It's for some online game.

[Nevezen]

Question.. what are vectors and how do they affect the performance of your miner specifically? If I recall correctly, vectors have something to do with stream processing?

Been playing around with the command arguments lately and when omitting -v, hashrate jumps up about +15M; for a lowly 8800GT, from 20M..

Decreasing the frames option makes the desktop almost unresponsive but contributes about +1M when setting from 120 to 10.. would like to know how this works as well.

[urizane]

As far as -v goes, I'm not entirely sure, but I think it just allows the calculations to take place in a wider field.  -f controls how long an instance of the miner can run for on the GPU (inverted to work on the concept of frame rate).  The larger the parameter, the more opportunities other tasks (such as updating the desktop) have at actually executing.  You may also want to mess with -w (work size).  For your GPU, I would probably guess 128 is best, but 64 might work as well.  I'm fairly certain 256 will spew randomly large hash/s at you and crash shortly thereafter.

If you haven't done so yet, at least check out puddinpop's RPC CUDA miner as this may net you a small boost in performance.  It won't be much at first, but you can do some tweaking to get more.

[m0mchil]

New version is up. All changes are pool related.

- long polling is slightly better in preventing stales to escape to server;
- miner now supports 'time rolling' whenever there is 'X-Roll-NTime' header in HTTP response;
- improved check for end of current task

[lupio]

Hello,

I want use poclbm with my HD 5770 vapor-x.

You know the tools at install with poclbm ?


Thanks

[urizane]

Hello,

I want use poclbm with my HD 5770 vapor-x.

You know the tools at install with poclbm ?


Thanks

If you're running Windows, the first link in the first post on this thread should be all you need.  In the command prompt, navigate to the directory you unpacked poclbm to and type 'poclbm --help' to get an idea how to get started.

EDIT: Also, there's a link in there for Kiv's GUI if you're not comfortable with command line stuff.

[LobsterMan]

With the latest version while mining for myself, I seem to be getting intermittent "problems communicating with bitcoin rpc" errors. They appear and disappear seemingly randomly...

[slush]

With the latest version while mining for myself, I seem to be getting intermittent "problems communicating with bitcoin rpc" errors. They appear and disappear seemingly randomly...

This may be related to the getwork locking in bitcoind, the same trouble as I solved. More people already reported troubles with mining on their own with many pending transactions.

You can a) patch the bitcoind with m0mchil's patch published yesterday b) Join my pool, now you even know how to do that

[jaybob20]

New version is up. All changes are pool related.

- long polling is slightly better in preventing stales to escape to server;
- miner now supports 'time rolling' whenever there is 'X-Roll-NTime' header in HTTP response;
- improved check for end of current task

Working much better for me now. Before this update, I had the miner restart if it threw a RPCError in getwork.
Now I see a bunch of "warning: job finished, miner is idle," but it keeps chugging along.
I haven't looked at the new code yet, but would some pre-fetching help?

[m0mchil]

Working much better for me now. Before this update, I had the miner restart if it threw a RPCError in getwork.
Now I see a bunch of "warning: job finished, miner is idle," but it keeps chugging along.
I haven't looked at the new code yet, but would some pre-fetching help?

No. You need as fresh jobs as possible. Try to figure out why it fails to fetch new one in a reasonable time. If not in pool - there is an issue currently which can make getwork() extremely slow, see http://bitcointalk.org/index.php?topic=4853.0

[travex]

Eh, do I have to disable crossfire for my 5970(1 card) using this miner guys ?

[qed]

Version 20110325 is a good 5%-10% slower on my 2nd and 3rd card compared to version 20110311.

[m0mchil]

Version 20110325 is a good 5%-10% slower on my 2nd and 3rd card compared to version 20110311.

There is a change in the way '-f' works. Simply said, just use lower '-f' now to achieve same performance/desktop lag as before. 5% seems too much though, what's your setup? Is the first card faster?

[qed]

Version 20110325 is a good 5%-10% slower on my 2nd and 3rd card compared to version 20110311.

There is a change in the way '-f' works. Simply said, just use lower '-f' now to achieve same performance/desktop lag as before. 5% seems too much though, what's your setup? Is the first card faster?

3x HD 6950@725MHz and 0.950V.
Windows 7 64-bit and catalyst 11.4 RC2.
CrossfireX enabled.

With the 20110311 version everything is fine and i'm getting around 270 Mhash/s on each card. With the 20110325 the crossfire issue is back, random drop at 180-190Mhash/s and an average of 250-260 Mhash/s on the 2nd and 3rd card.

Thanks for your great work.

EDIT: I'm using "-f 60"

[Raulo]

Version 20110325 is a good 5%-10% slower on my 2nd and 3rd card compared to version 20110311.

On the contrary, on my 2x5970 Linux mining rig, no difference in hashspeed compared to older versions. Everything works fine.

[OVerLoRDI]

Has anyone found some remedies I can get rid of the 100% core usage of poclbm?  I have 2 miners running with my 6970s and they each load up a core on my system.

The system seems to be tied to SDK 2.3 + 69xx cards.  I have two 5870s running on SDK 2.3 also and their instances of poclbm do not suck up much cpu time at all.

I tried the 11.4 RC1 driver that came out a few days ago, no change.  I'm back on 11.2 currently.