Where in my linux p2pool directory can I look to find the human-readable version number, e.g., currently, 9.4?

run_p2pool.py --version

This was while p2pool was already running normally:

Code:

proofer@miner:~/src/p2pool$ run_p2pool.py --versionfatal: Not a git repository (or any parent up to mount parent )Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).unknownproofer@miner:~/src/p2pool$:

The p2pool directory is renamed from the forrestv-p2pool-6880123 directory that was the expansion of the 9.4 linux tarball.

Git clone p2pool and copy data directory and use it All problems gone forever.

After 1d 15h 5m 39s, I have 211 shares, 22 orphaned, 3 dead - 11.85% stale rate. That's using the linux "do not use for mining" build in a VM, and p2pool v9.4. Decent in my mind, but not as good as it was pre fork.

Between my 3 miners, I have about 112k shares submitted, about 3k rejected, or 2.67% reject rate. That's pretty good for LP imho. Looking forward to stratum coming on.

After 1d 15h 5m 39s, I have 211 shares, 22 orphaned, 3 dead - 11.85% stale rate. That's using the linux "do not use for mining" build in a VM, and p2pool v9.4. Decent in my mind, but not as good as it was pre fork.

Between my 3 miners, I have about 112k shares submitted, about 3k rejected, or 2.67% reject rate. That's pretty good for LP imho. Looking forward to stratum coming on.

M

That's an excellent long term stale right.. I think mine is closer to 5%.

I have even better stats. On total 13187222 shares, 36281 stale shares = 0.275%.Using Ztex's BTCMiner on BitMinter pool.Unfortunately, my p2pool machine is too weak to get similar results on local p2pool with my FPGAs. Bitcoind latency is ~0.5s.

I have even better stats. On total 13187222 shares, 36281 stale shares = 0.275%.Using Ztex's BTCMiner on BitMinter pool.Unfortunately, my p2pool machine is too weak to get similar results on local p2pool with my FPGAs. Bitcoind latency is ~0.5s.

You can't compare stale rates of bitminter (or any non p2pool) with p2pool. They work differently.

My stratum miner is only .068% reject, but that number doesn't mean anything compared to p2pool.

I've come to the conclusion that latency plays a huge factor in stale rate. I think bitcoind was hogging my bandwidth, I turned off port forwarding for it, stopped using -n to connect to multiple p2pool pools, and turned off port forwarding to my backup p2pool.

After 10h 8m 45s, I have 49 shares, 2 orphaned, or 4.08% stale. Been ages since I've been that low.

I've come to the conclusion that latency plays a huge factor in stale rate. I think bitcoind was hogging my bandwidth, I turned off port forwarding for it, stopped using -n to connect to multiple p2pool pools, and turned off port forwarding to my backup p2pool.

After 10h 8m 45s, I have 49 shares, 2 orphaned, or 4.08% stale. Been ages since I've been that low.

M

I found the same thing.. it is vital to keep that latency down. It makes sense when you think about it too.. if bitcoin is taking 1 second all on its own then you could expect around 10% stales just from that since we have 10s long polls.

Where in my linux p2pool directory can I look to find the human-readable version number, e.g., currently, 9.4?

run_p2pool.py --version

This was while p2pool was already running normally:

Code:

proofer@miner:~/src/p2pool$ run_p2pool.py --versionfatal: Not a git repository (or any parent up to mount parent )Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).unknownproofer@miner:~/src/p2pool$:

The p2pool directory is renamed from the forrestv-p2pool-6880123 directory that was the expansion of the 9.4 linux tarball.

Git clone p2pool and copy data directory and use it All problems gone forever.

Excuse my noobness, but is this for Linux or Win? And how does one get this better "Git clone p2pool" - what's the procedure? I went to the site but couldn't work it out......dur.

Does any1 mining TRC found that something is wrong? NO block in 24hrs where expected time to block is about 0.5hr?

I was seeing a v8 trying to connect during the time I was getting tons of failure messages on the shares... which shouldn't have been possible...

so, I was thinking maybe someone was trying to join wrong, with too much hashrate or something...I have nothing to back that up tho, other than "wtf is up with this v8 node?"

Anyways, I separated my node from the rest to test a couple things out, see if I was still getting those share errors, and so far, it looks fine (except for my 2nd node not downloading shares from the 1st node)

I have seen some payouts come in on TRC recently, which I know didn't come from my nodes tho, so somewhere, I'm still getting some payout. No messages on the irc-announce tho, so dunno where they're getting inserted...