[9 TH] Bitparking Pool, DGM 0%,vardiff,stratum,Merge Mining

[kjlimo]

Thanks for always looking for new opportunities.  Can you post a link or explain in a couple words what advantages "stratum" would bring to your pool?

A description of stratum is here. It basically provides a more efficient way of receiving and sending work from/to the pool that the 'getwork' and longpoll protocols. For ASIC miners and other very fast devices this will cut down on bandwidth and make more efficient use of their machines. There should be less stales. 

Gotcha, so it's a "no brainer" with nothing to debate, just an upgrade.

Thanks for the quick response and again, thanks for being awesome!

[1714008627]

1714008627

[1714008627]

1714008627

[1714008627]

1714008627

[1714008627]

1714008627

[1714008627]

1714008627

[1714008627]

1714008627

[doublec]

Stratum support seems to be going OK. I've had to do a few server restarts to real with merge mining issues on the getwork server but other than that things are working fine. Some better luck would be nice! I have some more tweaks to do on the stratum side of things to make reporting shares more efficient and hope to get that done over the next couple of days.

[juhakall]

I decided to try this pool a few days ago, thinking it didn't have stratum support. But you sneaked in the support just before I joined . I hope you enable merged mining on stratum soon, though I see the altcoins are accumulating anyway.

[doublec]

There was a stratum restart a few minutes ago to improve performance on share submission. There will be another one in an hour to change over to another bitcoind. This should only be a 30 second outage.

[doublec]

The restart mentioned in my previous message is done. There shouldn't be any more planned restarts until the next round of stratum modifications for merge mining support.

[doublec]

The main pool page now shows the Getwork, Stratum and total hash rates. So far there is 50 GHash on the stratum server. I've also adjusted these rates to show GHash instead of the previous MHash. The URL http://mmpool.bitparking.com/stats2 shows this data in JSON format.

[osoverflow]

Is there any problem with the pool right now? I can't connect, not with stratum, nor without it. Thanks

----

I think the problem is with stratum. I fixed the protocol in cgminer to non stratum as a secondary (failover) pool, and now it works on it, but the stratum does not.

[doublec]

Is there any problem with the pool right now? I can't connect, not with stratum, nor without it. Thanks

It's working for me. Anyone else having issues?

[osoverflow]

This is what I'm getting:

stratum+tcp://mmpool.bitparking.com:3333   Dead

But on non-stratum:

http://mmpool.bitparking.com:15098   Alive

[doublec]

stratum+tcp://mmpool.bitparking.com:3333   Dead

This works for me with cgminer 2.11.0:

Code:

./cgminer -o stratum+tcp://mmpool.bitparking.com:3333 -u username -p d=16

Does it work for you? Is port 3333 blocked at your firewall? Can you connect to any other stratum server?

[kjlimo]

I need to switch the port I'm referencing?  So that I take advantage of the stratum?

Sorry, I missed that part.  I'll try to find some time tomorrow, but the green beer may keep me busy...

[osoverflow]

I can make a telnet to port 3333.

I have cgminer 2.9.5, maybe that is the problem. I'm going to build the 2.11.0

stratum+tcp://mmpool.bitparking.com:3333   Dead

This works for me with cgminer 2.11.0:

Code:

./cgminer -o stratum+tcp://mmpool.bitparking.com:3333 -u username -p d=16

Does it work for you? Is port 3333 blocked at your firewall? Can you connect to any other stratum server?

[osoverflow]

Ok, after building 2.11.1 version I see the stratum OK so I think the 2.9.5 version implementation of stratum does not work with bitparking pool.

[osoverflow]

May I ask you what is the purpose of difficulty? And if there is a rule to set it? I have two HD 5850 GPUs.

Thanks

[doublec]

May I ask you what is the purpose of difficulty? And if there is a rule to set it? I have two HD 5850 GPUs.

Usually pools provide shares to a miner set to difficulty '1'. This controls how fast you submit solutions to the pool. '1' was good for slower miners but with fast GPUs, FPGA's and ASICS it results in so much data being sent to the pool that your miner spends all its time sending and less time solving. By increasing the difficulty level you send less data and spend more time mining. It increases your variance a bit so you don't want to set it too high. For your setup the default of '4' should be fine.

[doublec]

Stratum server finds its first block. Block 226272.

[superfastkyle]

stratum server works fantastic just spent a day and a half updating about 20 rigs but it was worth it. Stales are between 0.17-0.30% how awesome is that. Also adding the merge mining code to the stratum server I assume will just take some extra time right? Its not like stratum isn't compatible with the alt chains

Stratum server finds its first block. Block 226272.

[doublec]

stratum server works fantastic just spent a day and a half updating about 20 rigs but it was worth it. Stales are between 0.17-0.30% how awesome is that. Also adding the merge mining code to the stratum server I assume will just take some extra time right? Its not like stratum isn't compatible with the alt chains

Great to hear it's working well for you! Yes, it'll just take some time to update my current merge mining code to provide the information the stratum server needs. There's nothing fundamental with stratum that would prevent it from working. I'm hoping to get it done in the next few days.

[davebodger]

I have the latest GUIminer working fine on Stratum to port 3333 - nice one.

However I cannot get it working via my Stratum proxy.
I have 5 machines (8 GPUs) and would like to route them via the proxy to save internet bandwidth.
Starting my proxy with "\Stratum\mining_proxy_1.2.0.exe -o mmpool.bitparking.com -p 3333"
gives :-

<several lines of normal startup stuff then.....>

Unhandled error in Deferred:

<loads of traceback info here then.....>

exceptions.ValueError : too many values to unpack

Should I be aiming the proxy at a different port?

[doublec]

Should I be aiming the proxy at a different port?

That looks fine. Is this slush's proxy? I'll download it and see if I can reproduce the issue.