Author

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 613. (Read 2591920 times)

member
Activity: 75
Merit: 10
Stale rate is still pretty dam high Sad

Code:
Version: 9.1

Pool rate: 335GH/s [b](23% stale) [/b]Share difficulty: 522

Node uptime: 1.640 days Peers: 6 out, 2 in

Local rate: 3.81GH/s (5.9% DOA) Expected time to share: 0.163 hours

Shares: 216 total (39 orphaned, 13 dead) Efficiency: 98.28%

Your efficiency is high enough Wink
But you should try version 9.2, the DOA rate is much lower for me.
hero member
Activity: 658
Merit: 500
Was using 9.0 fine and suddenly on reboot was spammed with this message and it closes instantly when using:


https://i.imgur.com/W4We3.png

Now I downloaded 9.2 just in case, but it connects quickly, but never do my miners seem to connect.. not even on the host machine. Anyone..?

Firewall? Looks like its blocked somehow.
hero member
Activity: 658
Merit: 500
9.2 is giving me a 100% orphan rate Last 10 shares in a row are orphans.. rolling back.

Double verified 100% orphan on 9.2. 20 more shares instant orphan.

9.1 and 9.0 are both fine though...?
sr. member
Activity: 364
Merit: 250
Was using 9.0 fine and suddenly on reboot was spammed with this message and it closes instantly when using:


https://i.imgur.com/W4We3.png

Now I downloaded 9.2 just in case, but it connects quickly, but never do my miners seem to connect.. not even on the host machine. Anyone..?
legendary
Activity: 1540
Merit: 1001
I grabbed the latest git this morning that includes the efficiency patch, that is the big change in 9.2.  After about 14 hours, I'm still looking at 24% stale rate.  However, cgminer is now reporting about 3% rejects, where before it was 10% - 20%.  So I think the stale rate is because of my conn problems.

M
hero member
Activity: 658
Merit: 500
9.2 is giving me a 100% orphan rate Last 10 shares in a row are orphans.. rolling back.
full member
Activity: 192
Merit: 100
P2Pool release 9.2 tag: 9.2 hash: b016b6b522286e4675b82b9c4206784937977f3e

Changes:
* Fixed some really inefficient checks

This has been confirmed (more or less) to help reduce your stale rate.

Before the switch DoA was at 1.5%. After the switch it climbed up to 5.2%. The latest fix brought it down to 2.5%.

CPU usage still seems high and p2pool is using 1.4 GB RAM, so hopefully there is still place for improvement Smiley

Comparing p2pool block receive times and blockchain.info times shows that 250 kB blocks are now distributed in 0-2 seconds. This is amazing!
hero member
Activity: 784
Merit: 500
Stale rate is still pretty dam high Sad

Code:
Version: 9.1

Pool rate: 335GH/s [b](23% stale) [/b]Share difficulty: 522

Node uptime: 1.640 days Peers: 6 out, 2 in

Local rate: 3.81GH/s (5.9% DOA) Expected time to share: 0.163 hours

Shares: 216 total (39 orphaned, 13 dead) Efficiency: 98.28%
hero member
Activity: 516
Merit: 643
P2Pool release 9.2 tag: 9.2 hash: b016b6b522286e4675b82b9c4206784937977f3e

Windows binary: http://u.forre.st/u/hvxnplnd/p2pool_win32_9.2.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.2
Source tarball: https://github.com/forrestv/p2pool/tarball/9.2

Changes:
* Fixed some really inefficient checks

This has been confirmed (more or less) to help reduce your stale rate.
legendary
Activity: 1792
Merit: 1008
/dev/null
I have two subnets.
Each subnet running bitcoind, but wallet.dat used in both cases is the same.
Also in each subnet running p2pool.
Can I setup two subnets are the same address for the award?
Are there problems?
no this is fine Wink
AV
hero member
Activity: 910
Merit: 1000
I have two subnets.
Each subnet running bitcoind, but wallet.dat used in both cases is the same.
Also in each subnet running p2pool.
Can I setup two subnets are the same address for the award?
Are there problems?
sr. member
Activity: 383
Merit: 250
forrestv: Much better latest git master after 6.5 hours.
Version: 9.1-5-gb016b6b Node uptime: 0.415 days Peers: 10 out, 24 in
Shares: 89 total (5 orphaned, 3 dead) Efficiency: 121.9%
Still got 27 Get Fails in that 6.5 hours, but no Rem Fails.
2.9% Rejects which is also much better.  Smiley

Edit:
htop at start showed 485M RES and 636M VIRT
htop after 6.5 hours  622M RES and 775M VIRT

Watching for 5 minutes I never saw CPU go over 56% Most of the time it is 20 or lower.

Still need to figure out why we get so many Get Fails. I know it is not hardware. I have a really fast server (lots of RAM, 8 CPU cores, and 16TB free space on Hardware Raid 6 ) and a fast Internet connection.

I got 2 Get Fails on solo with bitcoind in 24 hours for comparison.
legendary
Activity: 1680
Merit: 1035
With the block halving, my profit is gone, and I had to shut down my miner. I still have Bitcoin-qt and P2Pool running, thinking having a full node available will help other P2Pool users somewhat (have about 24 incoming connections). Someone let me know if I'm wrong about this?
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
You can run python and git on windows, though, so it should work (at least in theory).
Just installed git for windowz ;]
Code:
C:\msysgit\git\p2pool>run_p2pool.py --version
b016b6b

Sadly it is not showing full version, only git hash :/
Same after compilation to exe.
Looks like "manual" way is only way for dat windowz to show full version number.
hero member
Activity: 658
Merit: 500
I am only seeing 6 peers in 9.1 vs 10-15 on 9.0
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
OK, after 18 hours uptime I can't see any significant change - still at 25%+ orphan/dead rate with large memory usage. I have also noticed a lot of the "tx" comments in the logs, as well as the "punishing share for stale" thing - whats with that? Even with the high stale rate I notice we're still getting payouts on blocks (albeit lower since halving) so it's not all bad, although I find myself wondering what the payouts would be with a normal reject/orphaned/dead rate...... Sad

Right, just switched over to the newest git from Rav3n's skydrive - thanks for the heads up Rav3n. Lets see how this baby goes......

Well, after only being up for a few hours with this latest release I can already see a 200% improvement - 10 shares - 0 stales - 0 dead. Now THATS more like it, back to normal again, so far. What ever changes were implemented in this version seem to have worked wonders for my set up at least. Noticed some more additions to the logs that I've not seen before:

KNOWN: 141425
MINING: 60749

It's showing often, can someone explain these? I presume it's some kind of checking that has helped eliminate the bad shares?
legendary
Activity: 1379
Merit: 1003
nec sine labore
He meant windows.
I not see how it ca be done automagically.
I`m doing it by gitpulling on linux, see version number then compiling windows version using that data.

rav3n_pl,

sorry, I'm using linux only on my rigs.

You can run python and git on windows, though, so it should work (at least in theory).

spiccioli.
legendary
Activity: 1361
Merit: 1003
Don`t panic! Organize!
He meant windows.
I not see how it ca be done automagically.
I`m doing it by gitpulling on linux, see version number then compiling windows version using that data.
legendary
Activity: 1379
Merit: 1003
nec sine labore
Latest git 9.1-9-gb246991 works much better for me.
Memory usage on linux finally drop to around 500MB, no doas.
Windows binary (32 bit) on my skydrive.


Is there a way to see the git version when you download as zip?  once upon a time it was in the filenname, now everything is "p2pool-master".

M


mdude,

the best way is to issue a git clone the first time and then, cd into p2pool directory and issue a git pull when you need a new version.

you have to install git, but from then on it will update itself seamlessly.

spiccioli
legendary
Activity: 1540
Merit: 1001
Latest git 9.1-9-gb246991 works much better for me.
Memory usage on linux finally drop to around 500MB, no doas.
Windows binary (32 bit) on my skydrive.


Is there a way to see the git version when you download as zip?  once upon a time it was in the filenname, now everything is "p2pool-master".

M
Jump to: