I think it's a really good thing that such a client gets public, it decreases the chance that the blockchain gets overtaken by NSA XD

What are your -frames and -worksize arguments like? Also what -askrate interval do you have?

I did get two cards working (had to use the crossfirex cable and enable crossfirex).

The thing that baffles me is how to get the same performance out of two cards together as I got out of two cards seperately. It seems if i set the frames very low like -frames=2 I can get one card to do about 97% gpu capacity. The other card, however drops to 60-80%. When I make the frames high like 256 it does ok but any other program on my machine seems to have a higher priority and will make poclbm.exe run slow.

Currently the best compromise I found was
--frames=25 --rate=3 --worksize=256 --device=1 --askrate=30

On a single core processor machine this produces about 90% on each card average but has wild swings.

For a while I thought the issue was my MB or CPU not feeding the data fast enough but I tried the cards in my gaming machine with a quad core and dual x16PCIe slots and it still was about the same.

Any ideas?

bethel : -f 35 and -w 128 . I don't have any rate or askrate variable.

da2ce7 : If you started to generate before having all the block downloaded, then the block you found isn't valid. Restart your client and start to generate once you got all the block. This happened to me too, david explained it to me pretty well =)

Malouin

Nop, my bitcoin client don't generate from CPU.

OpenCL can run on CPUs, too. It seems like that's what is happening. Maybe. Does poclbm ask you to choose your device when you start it?

My CPU usage is <5% for poclbm, so something's wrong.

$ nice -n 15 ./poclbm.py  --user=******** --pass=******** -f 60 -w 256
No device specified, you may use -d to specify one of the following

found: 46380061, 26/10/2010 14:46
found: 46380061, 26/10/2010 14:46
17616 khash/s                          

Found this just now.  Why did it find the same block twice?  Could it be there are, oh, like two threads repeating the same work?

EDIT: also, the main bitcoin client credited me with 50btc, one block, at 14:45.  Total to my credit is just one block 50btc.  What's going on?  I looked through the source, and the RPC commands list.  Where does the source poclbm.py tell the bitcoin client that it found a hash below the target?  (I'm a python newbie).

mornin' miners, up for another update?
here we go...


short version:

HD5850 300.000 khash/s @ 925MHz


long version:

i did some more testings and tweaks and finally reached my goal,
to break the 300M-barrier while keeping below 70°C (setting higher voltages would not only consume more energy, as a result it'll also create noise which i really don't like).

while Catalysts (and others) tests fail at clocksets above 910MHz, the pocl-miner doesnt care much about it, it runs fine up to 935MHz, more and the miner starts to get laggy and just starting the GPU Caps Viewer crashes the system (not if it's already running).

to stay safe i set it to 925MHz, which still gives hangups and failures in tests, Fallout:New Vegas doesn't even start, stuff like that,
but the miner runs fine, stable and averages at above 300Mhash/s.
i think i'll keep it like that and just set it to defaults to kill Mr.House and save (or rule?) the world, that old guy kinda scares me.


however, the ordinary screenshot this time is also a nice comparison of both of my OpenCL-capable Cards, funny that both of 'em found a block within 1hour.

to the left (via vnc) we see a GTX260@685MHz at work, mining 45.000 khash/s on win7x64,
to the right her greatness HD5850@925MHz, mining 300.000 khash/s on xp64.


not to mention that theres still 5x2-3GHz CPUs left on those 2 machines that don't do anything right now, but hey, i'd get what, ~1000 khash/s per core? on the HD-miner that's <1%! and it'll also create more heat and noise and will need more energy too,
i'd rather tweak the card/s a little more.
but i think i'm done now and more than happy, hell i'm thrilled by those results, never thought the card would go that far.

what do you think?
how's your machine/s working?
tell us about it, we wanna know, well at least i do.

have a great day.

nah, i wouldn't say that,
the bitcoin-randomizer-node only runs at ~800khash/s on a single core and still generates blocks every now and then,
i even got miners running on an intel-Atom and PIII-1GHz that just get ~250khash/s.

you just need some more luck, any single hash could be the one we'r all looking for.

if your running a GPU-miner anyway though, there's at least on midclass-ati-cards no real need to run CPUs, they'll consume more power than needed to get what you want. give your gfx-core another 1-2% speed and your done, this'll take ~5W+ instead of >50W+ for CPUs@full throttle.

if your thinking about, or going to build a new miner-machine, i agree,
don't bother with CPUs, nor with nvidia. 

careful though if you buy new stuff, dont get one of those shiny new HD6850/70, or you'll be dissapointed.

yeah, that's why i didn't use it

and i havent been compiling any miners myself (tried a few times but had no luck so far installing all required components on x64), so grabbing code x from y to patch z wouldn't help me much.
i'm just a user anyway, not a coder (php-scripter for fun, but that's it),
one could say i represent the masses (at least those that are interested in how it works), that's why i'm so happy that there's a few nice people to realease binaries.

playing around with frames just gives me a ~1-2% increase, not really worth mentioning and for the cost of a very low responding desktop.


@m0mchil: you should really put your btc-address either into the initial post of this thread, or your sig, kinda hard to find already and will get even worse over time. 

i noticed some strange disconnections lately,
everything seems alright, but it somehow hangs and doesnt get new blocks,
happens while
connected un-forwarded (showing 8connections),
-connect=<forwarded-nodes-ip> (showing 1connection),
-addnode=<forwaded-nopdes-ip> (showing 8connections),
forwarded-node has 50<80connections and seems to always have all blocks, other nodes sometimes just don't get them, no matter how i connect them.
not sure yet what's causing this, a feature to force getblock or somethin' would be handy sometimes.

but this made me try to set up both OpenCL miners to run on one node.
starting the (former GTX-only) node with -rcpallowip, connection and mining works fine,
eatin' a few Mhashes though.
while running the (remote) HD-miner at defaults (askrate=5), the (local) GTX-miner slows down from ~45M to ~43M average, setting (remote) askrate=10 helped here, still a noticable but <1M loss,
the HD-miner also goes down ~2%, from 300 to 294.

tested on 100MBit, maybe there's <2% loss on gigabit networks, i'll try as soon as i find someone to pay for some switches and cards.  

happy crunching
and if anyone knows of, or finds a solution to that spooky non-forwarded-node-disconnects, let me know, thanks.