Join a pooled bitcoin mining effort - page 6.

BitLex

hero member

Activity: 532

Merit: 505

Quote from: cartman on December 06, 2010, 04:05:41 PM

it seems that the performance is only half of the standard client. is there any way to improve the performance?

the cuda-client is still a bit slow, the cpu-version isn't,
performance shouldn't be that much of a difference.

let me guess, you're using a dual-core.
then just start a 2nd instance to double your performance. Wink

cartman

newbie

Activity: 48

Merit: 0

nice work doublec, thanks a lot.

it seems that the performance is only half of the standard client. is there any way to improve the performance?

mpkomara

full member

Activity: 183

Merit: 100

thank you, works now

doublec

legendary

Activity: 1078

Merit: 1005

Quote from: mpkomara on December 06, 2010, 02:34:35 AM

"Attempting to connect to 127.0.0.1:8335"

Are you using the new pooled client? The old one won't work:

http://www.bluishcoder.co.nz/bitcoin-pool/

mpkomara

full member

Activity: 183

Merit: 100

Quote from: BitLex on December 05, 2010, 11:01:08 PM

your missing the ='s, it's not spaces anymore like before,
-server=173.255.205.10 -address=XXXXX
should work

"Attempting to connect to 127.0.0.1:8335"

FreeMoney

legendary

Activity: 1246

Merit: 1016

Strength in numbers

Works now.

lysacor

newbie

Activity: 8

Merit: 0

Yep I confirm that the reports are coming across correctly now.

doublec

legendary

Activity: 1078

Merit: 1005

Quote from: BitLex on December 06, 2010, 12:12:09 AM

just be patient and keep reading here, or on the pool-website to upgrade, if needed, as soon as possible.

I fixed what looks like one bug in the best hash verification but it didn't solve this issue. I've switched back to the 'connected' distribution type and that is now printing things correctly. I'll wait till I hear from puddinpop before switching back to contributed and trying to solve the issue.

BitLex

hero member

Activity: 532

Merit: 505

seems like all connected clients get that same message,
doublec is working on it already, that's why the miners lose connection and reconnect as you might have noticed.

just be patient and keep reading here, or on the pool-website to upgrade, if needed, as soon as possible.

FreeMoney

legendary

Activity: 1246

Merit: 1016

Strength in numbers

Quote from: lysacor on December 06, 2010, 12:00:59 AM

The previous client reported within the first few messages how much BTC your address would get based on the khash it was contributing, and it reported it fairly quickly. Does it take longer before it calculates and adds you to the list of addresses receiving BTC if a block is won?

After a few hours mine is still not in. I think it is broken.

lysacor

newbie

Activity: 8

Merit: 0

The previous client reported within the first few messages how much BTC your address would get based on the khash it was contributing, and it reported it fairly quickly. Does it take longer before it calculates and adds you to the list of addresses receiving BTC if a block is won?

lysacor

newbie

Activity: 8

Merit: 0

The only thing left now is to isolate the CPU usage associated with this CUDA experimental client. Then you can get some seriously high level performance. I just hope we don't end up burning up your server resources with it!

doublec

legendary

Activity: 1078

Merit: 1005

Quote from: BitLex on December 05, 2010, 10:49:21 PM

it works, that's a start.

If there were 100 cuda clients in the pool we'd get a block every 5 hours or so.

BitLex

hero member

Activity: 532

Merit: 505

your missing the ='s, it's not spaces anymore like before,
-server=173.255.205.10 -address=XXXXX
should work

kiba

legendary

Activity: 980

Merit: 1020

Code:

Attempting to connect to :8335

Error?

BitLex

hero member

Activity: 532

Merit: 505

Quote

puddinpop noted to expect this

noticed that, just wanted to confirm it. Wink

it works, that's a start.

doublec

legendary

Activity: 1078

Merit: 1005

Quote from: FreeMoney on December 05, 2010, 10:29:52 PM

Me too, not found. Did you switch to contributed and rounding is causing this?

Contributed method is bad imo.

Why is it bad? I asked before switching and the majority of the responses requested contributed.

doublec

legendary

Activity: 1078

Merit: 1005

Quote from: BitLex on December 05, 2010, 10:39:28 PM

cuda-miner does less than half of what i get using m0's (or puddinpops older cuda-versions).
m0's = 45M
remote-cuda= 17M

puddinpop noted to expect this:

Quote

Also, there is an experimental remote CUDA client included in the release. Expect half the hash rate you get with the regular CUDA miner built into the standard client.

BitLex

hero member

Activity: 532

Merit: 505

Quote

Address XXXXXXXXXXX not found in block being solved

same here on both, cpu and cuda miner,
cuda-miner does less than half of what i get using m0's (or puddinpops older cuda-versions).
m0's = 45M
remote-cuda= 17M

FreeMoney

legendary

Activity: 1246

Merit: 1016

Strength in numbers

Quote from: doublec on December 05, 2010, 10:08:56 PM

I updated the server on 173.255.205.10 early since there were only 4 clients connected. Instructions updated here:

http://www.bluishcoder.co.nz/bitcoin-pool/

Basically you need the new client binary. The windows version is now called remoteminer-cpu.exe and the arguments to it require '=' instead of a space between the '-address' and its value (and '-server' and its value).

There's also a remoteminer-cuda.exe for those with a cuda compatible GPU.

Let see how well this handles load. If it's fine I'll take down the other server.

Me too, not found. Did you switch to contributed and rounding is causing this?

Contributed method is bad imo.

Topic: Join a pooled bitcoin mining effort - page 6. (Read 53380 times)