[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[bryonp]

OMG!

Why not P2POOL！

Sure looks like somebody screwed up and put things in the wrong place:

Whoever did it must be kicking themselves right now.

Phaw

Forgive me guys... I dont understand? (please)

Also now that we have moved to the 9M range I have been getting more shares and almost no orphans or dead...?

1) he paid 27BTC in fees.  He should have only paid 0.0001BTC for a transaction of that size.
2) you're having a streak of good luck.

Well Son Of A Bitch.... Its about time for some good luck!
Thanks so much for your answers!!!!!!

[bitcoinbearhk]

sad still no one can answer my question why that my Cointerra are only mining at 1320 GH/s instead of 1600 GH/s ...... SOS SOS SOS

You're complaining about no answer after only an hour between posts?  Sheesh.

Any way, to answer your question, my terraminers are also running around 1.3TH/s, where on BTCGuild they used to run at 1.6.  Is that due to P2Pool?  Possibly, but I haven't really wanted to switch back over to test the theory.  Could also be due to them starting to overheat, as Terraminers are known to do.  I haven't had time to re-do the thermal paste to see on that either.

As for your share question, read the past 3-5 pages (I think, maybe more) and you should get your answers, that topic was recently covered.

Thanks buddy 

I repeat my question again and again only to get attention.  If the message is left behind for like several post, it's not gonna be noticed and answered

Great to know that there's someone also out there same as me using Terraminer on p2pool, and share the same problem.  I am pretty sure it's not due to the heat problem, cause I do switch back to CEX and the hash returns.  Also, I have applied Liquid Pro to my miners, and the heat problem is pretty much under control.

It is thus likely due to the compatibility between Terraminer and P2Pool.  The only thing is, whether the "reduced speed" is only an apparent reduction on the monitor, or an actual reduction...

I am sure there are more out there using Terraminers on P2Pool... would be grateful if we could share the tech on how to properly set them up with the node, or set the node to suit them...


I really love the P2Pool network, and will be pumping 20TH/s to support it once I've got the tech problem solved.

[bitcoinbearhk]

I have finally found the "potential" problem with my miners. It should be because the difficulty the p2pool giving my miner is too low.

There's a feature in p2pool about setting difficulty: [username]/[pool difficulty]+[local difficulty]

Should I be setting these??? If so, what value should i give for a 1600GH/s Terraminer?

[jonnybravo0311]

I have finally found the "potential" problem with my miners. It should be because the difficulty the p2pool giving my miner is too low.

There's a feature in p2pool about setting difficulty: [username]/[pool difficulty]+[local difficulty]

Should I be setting these??? If so, what value should i give for a 1600GH/s Terraminer?

There are literally pages of debates on this very thread about the value of setting share difficulties.  Here's the deal:

Using "/" sets the actual share difficulty.  Unless you set it over the p2pool minimum value, it has no effect.
Using "+" sets the pseudo-share difficulty.  All this does is make graphs look pretty.

Bitmain has stated that you should set *some* value for use with the S3.  They recommend either 256 or 512.  Maybe it's something to do with their drivers and the way they handle work from p2pool's varying difficulty and restarts.  Since nobody has the source code, nobody can do anything about it or make any kind of valid statement one way or the other.

I have personally seen absolutely no difference in my S3s on p2pool either setting the values or leaving them alone.  I do not own any Cointerra gear, so all I can say is for you to try it out.  Put something like ADDRESS/1024+1000 and see what happens.

I'm sure somebody will come along and try to say something different and ignite the entire debate again

[kgb2mining]

I'm going to try some different setting with my cointerras.

CT #1 I've set it to - {address}/1024+1536
CT #2 I've left it alone, meaning just the address.

I have restarted cgminer on both boxes at the same time to get a direct comparison over time.  I'll report back later with what I see, if any difference either way.

[jonnybravo0311]

I'm going to try some different setting with my cointerras.

CT #1 I've set it to - {address}/1024+1536
CT #2 I've left it alone, meaning just the address.

I have restarted cgminer on both boxes at the same time to get a direct comparison over time.  I'll report back later with what I see, if any difference either way.

Looking forward to your results.  Hopefully you will see some improvement.

[rav3n_pl]

/1024 give you nothing, because current share diff is way higher.

[jonnybravo0311]

/1024 give you nothing, because current share diff is way higher.

See my earlier comments.  While it means nothing to the node perhaps there is a benefit to the hardware by using static difficulty.  As I stated I saw none at all on the S3.  Maybe the cointerra rigs do... I doubt it but you never know until you experiment

[kgb2mining]

Results might have to wait, I think I might have an overheating controller on my first unit.  The CTA0 board temps keep going through the roof, then bouncing to almost nothing, a sign that the machine is effectively throttling itself from burning up.  I'm going to go replace the thermal grease and see what happens.

Initial comparisons on the other controller so far have been about equal to the other, non-modified Cointerra, about 600GH/s.

[PatMan]

Hmmmm...Has anyone else's namecoind borked since updating Xubuntu with the latest security updates? I'm getting "timeout getting getauxblock" all of a sudden......

Seem to remember getting the same after upgrading from 12.04 to 14.04 a while ago due to a change in the Ubuntu kernel.

[jonnybravo0311]

Hmmmm...Has anyone else's namecoind borked since updating Xubuntu with the latest security updates? I'm getting "timeout getting getauxblock" all of a sudden......

Seem to remember getting the same after upgrading from 12.04 to 14.04 a while ago due to a change in the Ubuntu kernel.

I didn't do a thing to my node and noticed namecoind was taking up large chunks of CPU and also timing out on the getauxblock calls.  Noticed it this morning.  I ended up just getting rid of the merge-mining altogether on my node at this point.  The only coin I actually have a ton of is FSC (well over a million of them), but that coin is deader than Elvis.

EDIT: I'm running my node natively on OSX Mavericks 10.9.4, so it's definitely not limited to Xubuntu.

[PatMan]

Thanks JB, so it's not just me then. I'll investigate further........

Edit: I notice forrestv made a change to the p2poool repo ( !) 7 days ago, increased maximum worker difficulty 1000x, that wouldn't be the cause......would it?

Edit2: Tried running namecoin on rav3n_pl fork with the same results, so it's not a p2pool issue. Had to close the namecoin wallet as it was eating cpu as well. Oh well, that'll have to stay off then.......... Very strange.

[bitcoinbearhk]

Results might have to wait, I think I might have an overheating controller on my first unit.  The CTA0 board temps keep going through the roof, then bouncing to almost nothing, a sign that the machine is effectively throttling itself from burning up.  I'm going to go replace the thermal grease and see what happens.

Initial comparisons on the other controller so far have been about equal to the other, non-modified Cointerra, about 600GH/s.

so as it seems, each half Cointerra having 680GHs when mining at p2pool instead of 800GHs is normal??? I wonder if it is just the p2pool share system makes the cointerra machine makes it think it is mining slower, but it is actually mining at 800GHs maybe???

[mdude77]

Results might have to wait, I think I might have an overheating controller on my first unit.  The CTA0 board temps keep going through the roof, then bouncing to almost nothing, a sign that the machine is effectively throttling itself from burning up.  I'm going to go replace the thermal grease and see what happens.

Initial comparisons on the other controller so far have been about equal to the other, non-modified Cointerra, about 600GH/s.

so as it seems, each half Cointerra having 680GHs when mining at p2pool instead of 800GHs is normal??? I wonder if it is just the p2pool share system makes the cointerra machine makes it think it is mining slower, but it is actually mining at 800GHs maybe???

I believe the S2s have a problem restarting work every 30 seconds, and that's why the hashrate decreases.  I'd imagine the same thing happens with other ASICs.

M

[bitcoinbearhk]

Results might have to wait, I think I might have an overheating controller on my first unit.  The CTA0 board temps keep going through the roof, then bouncing to almost nothing, a sign that the machine is effectively throttling itself from burning up.  I'm going to go replace the thermal grease and see what happens.

Initial comparisons on the other controller so far have been about equal to the other, non-modified Cointerra, about 600GH/s.

so as it seems, each half Cointerra having 680GHs when mining at p2pool instead of 800GHs is normal??? I wonder if it is just the p2pool share system makes the cointerra machine makes it think it is mining slower, but it is actually mining at 800GHs maybe???

I believe the S2s have a problem restarting work every 30 seconds, and that's why the hashrate decreases.  I'd imagine the same thing happens with other ASICs.

M

Is there a workaround for this problem?  P2Pool is so supper cool, but having 20% ripped off the mining speed is not cool.

[windpath]

Both shameless self promotion, and answers to a few questions I've been getting a lot...

http://www.cryptocoinsnews.com/news/p2pool-become-easier-coincadence-acquires-p2pool-org/2014/08/17

New p2pool.org to be launched by September.

Coin Cadence open source front end available by November.

Press Release:

https://www.evernote.com/shard/s91/sh/b7a22e98-1a1e-47fc-8828-59b4dd67cc6e/987b876f430c7b582d4a4b4e8e7c73ab

Also actively looking for developers with a realistic solution to small miner variance, drop me a line...

[bitcoinbearhk]

Both shameless self promotion, and answers to a few questions I've been getting a lot...

http://www.cryptocoinsnews.com/news/p2pool-become-easier-coincadence-acquires-p2pool-org/2014/08/17

New p2pool.org to be launched by September.

Coin Cadence open source front end available by November.

Press Release:

https://www.evernote.com/shard/s91/sh/b7a22e98-1a1e-47fc-8828-59b4dd67cc6e/987b876f430c7b582d4a4b4e8e7c73ab

Also actively looking for developers with a realistic solution to small miner variance, drop me a line...

Read... So, it would seems to me that a 10~20% decrease in efficiency for large miners such as Cointerra and S2 is a known issue and unresolved ..... 

Not sure if I should stay in P2Pool with my Cointerra gears in this case .... sad 

[windpath]

...

Read... So, it would seems to me that a 10~20% decrease in efficiency for large miners such as Cointerra and S2 is a known issue and unresolved ..... 

Not sure if I should stay in P2Pool with my Cointerra gears in this case .... sad 

While the issue with the S2 has been well documented here, you are the first case of a problem with Cointerra gear I have seen.

Cointerra is specifically listed in the wiki as working well.

https://en.bitcoin.it/wiki/P2Pool#Interoperability_table

I would also like to hear from other Cointerra miners on p2pool.

[bitcoinbearhk]

...

Read... So, it would seems to me that a 10~20% decrease in efficiency for large miners such as Cointerra and S2 is a known issue and unresolved ..... 

Not sure if I should stay in P2Pool with my Cointerra gears in this case .... sad 

While the issue with the S2 has been well documented here, you are the first case of a problem with Cointerra gear I have seen.

Cointerra is specifically listed in the wiki as working well.

https://en.bitcoin.it/wiki/P2Pool#Interoperability_table

I would also like to hear from other Cointerra miners on p2pool.

i have setup my own node on Windows 7, and mining for over a day.

hash show up on cointerra is a constant 1350 GHs instead of the normal 1600 GHs... checked not heat problem, can resume 1600 with regular pools......

desperate to find a solution.

[bitcoinbearhk]

...

Read... So, it would seems to me that a 10~20% decrease in efficiency for large miners such as Cointerra and S2 is a known issue and unresolved ..... 

Not sure if I should stay in P2Pool with my Cointerra gears in this case .... sad 

While the issue with the S2 has been well documented here, you are the first case of a problem with Cointerra gear I have seen.

Cointerra is specifically listed in the wiki as working well.

https://en.bitcoin.it/wiki/P2Pool#Interoperability_table

I would also like to hear from other Cointerra miners on p2pool.

i have setup my own node on Windows 7, and mining for over a day.

hash show up on cointerra is a constant 1350 GHs instead of the normal 1600 GHs... checked not heat problem, can resume 1600 with regular pools......

desperate to find a solution.

I saw this on wiki:

Requirement:
    Windows:
        Install Python 2.7: http://www.python.org/getit/
        Install Twisted: http://twistedmatrix.com/trac/wiki/Downloads
        Install Zope.Interface: http://pypi.python.org/pypi/zope.interface/3.8.0
            Unzip the files into C:\Python27\Lib\site-packages

Well I have not installed the Python 2.7, Twisted and Zope.  Will that be a problem resulting in my Cointerra's under performance???