|
.98 is much better on p2pool. My Jupiter went from 440GH/s to 530GH/s. Nice work KNC and Con.
|
|
|
|
Node collection: This can be done and bigger miners are encouraged to do this to help out the smaller ones. You can do this by using the username "username/{difficulty}". So if I want to return one HUGE share that is worth 10x a small share, I log in with "-u username/1400000" I find a share 10x less frequently, but when I do it pays out a lot. people who find 50+ shares a day can do this and see a negligible change in variance and payout while encouraging smaller miners to keep mining by reducing small miner variance.
Maybe this should be set automatically by p2pool like the difficulty to keep the share difficulty lower and keep smaller miners on the pool? |
|
|
|
|
Any info on queue placement since a lot of orders were cancelled? I was in batch 5, but will I be moved to an earlier batch?
|
|
|
|
Thats confuse me. I have mine for 2 Days (Friday and Saturday) with 14 GH on mine p2pool node smileandgo.de:9332
The Node makes no pool shares. My miner have make over 32k accepted shares to the node.
And i become no payouts to my address or to the node address
You need to find a pool share. Think of it as a p2pool block maybe. When you find one your payout should be higher than an equivalent PPS payout to make up for the time you didn't find a pool share. That's how variance work - and you will have a lot of variance at that hashrate. What's your expected time to share? |
|
|
|
Is it also run 440GH/s on "normal" pools? Looks like flushwork takes like 1 sec No. 480-510GH/s. IIRC the graph number minus DOA, but you get some of the DOA back because everyone else has them too. Should check with forrestv, also note you are 110% efficiency in that p2pool output, meaning you're outperforming the pool on average latency wise and are expect to get 110% of what you would expect based on your hashrate. Is the CGminer claimed hashrate lower with p2pool then elsewhere? If so, something about the hardware design / firmware / or miner driver is brain damaged. Considering that my efficiency is over 100% and I generally pay up to a 3% pool fee elsewhere, I've left the Jupiter on p2pool - it's averaging out to 450GH/s so I shouldn't be too far off...if my understanding of efficiency is correct  The CGminer hashrate actually behaves opposite on other pools. It always reports lower than p2pool reports, but reports higher than other pools. On BTCGuild and Ozcoin CGminer shows 530GH/s and the pools 480-510. |
|
|
|
explain it.
e.g with a graphic.
I have understand:
every can make a node from the p2pool.
When you mine on your own node and you are faster than the "Expected time to block" you become shares on p2pool network.
When not, you loose all your mine shares. -> trash.
Only when your node can make a share, you and your miners become btc?
I don't think that's right, but I'm a bit sketchy on it myself. Someone jump in here and fix any errors. From my understanding, it's very similar to PPLNS (pay per last N shares) at any pool, except you are mining p2pool shares (at a 30 second target), instead of bitcoin blocks (at a 10 min target). The share chain "N" is 8640 shares long. When a new share is found the last share 8640 away from it is dropped. When a bitcoin block is found, you are paid based on the number and difficulty of shares you have found that are still in the last 8640 shares of the share chain. At a 30 second average per share and 8640 shares, that's 72 hours. So if you find a share it stays valid, or in the share chain for a payment, for 3 days. Or another way, when a block is found, payment is distributed for the last 8640 shares - which should span the last 3 days. IDK how the diff of the share works though. |
|
|
|
Just a quick update on my 10GH processing via P2pool with my BE. I guess Ive been lucky as everything has always worked perfect for me on P2Pool, until this last difficulty rise. I used to get payouts in virtually every new block found. Ive been told by respected members of the forum I will still get my fair payout, and so I am continuing to processes via P2Pool even though I have not had a payout in around four solid days. I trust the members that have given me this advise. I will ofc feel happy when I see a payment again....... ty all again.
UPDATE After around 1 week of solid processing at 10 gh/s via p2pool network I received 0.00337845 BTC; after missing 16 block payouts in a row. I'm sorry to say this can't be giving me my fair share for my work done on the p2pool network so I have moved off it. Do you have any node info - hash rate, stale rate, DOA, efficiency? |
|
|
|
Is it also run 440GH/s on "normal" pools? Looks like flushwork takes like 1 sec No. 480-510GH/s. |
|
|
|
Wow. The newest firmware from KnC (0.97) makes their miners work FLAWLESSLY with p2pool! The difference is staggering. Before p2pool was literally unusable with my Saturn - but now I am getting close to max hashrate  I wouldn't say flawlessly...but it does look much better. I'll run 24 hrs and post results. |
|
|
|
I think you are being touchy. I'm not seeing the criticism of the hardware companies where people are spending thousands of $, not by donation. P2pol was changed from 10 second work to 30 second work to help ASIC miners. The ASIC companies responded by making their hardware worse, that's my constructive criticism.  to you too. |
|
|
|
|
You all realize you are also losing work on traditional pools with KNC right? Watch your hash rate when new work is pushed, and then check all the bad work it sent off to the pool - especially if you are set to variable difficulty work. New work is pushed more often with p2pool so it has a greater effect. P2pool works fine, the hardware companies don't. Try demanding quality products for the thousands of $'s you spend instead of bashing the free software developed by people volunteering their time.
|
|
|
|
OP just use https://spideroak.com it's very similar to Dropbox except it runs a local app for encryption and allows you to select files/directories to sync automatically on changes. That and Time Machine have saved me from a few wallet disasters over the years. |
|
|
|
So as I originally said as I have 10 gh and now don't seem to find a share before p2pool finds a block I can't get paid out.
Look up, gmaxwell just explained it. You don't need to find a share every block, or even every 3 days. You will find a share and be paid, you will just have a lot of variance. |
|
|
|
Seems to contradict the findings of Afox. Perhaps some random variance?
BTW, does anyone know how to do p2pool with KNCminers? Any details on how that'd be achieved would be appreciated (especially on changes needed on the KNC miner itself, not so much so on what needs to be done in the host PC running the p2pool software).
KNC's don't work well with p2pool. The ridiculously slow flush work causes a lot of issues and around 150 Ghash loss on a Jupiter. |
|
|
|
The worst part for me is that the avalon miners on tradehill went for 2.21 btc a piece Today, for 60gh/s.
Where do you see this? |
|
|
|
not with their power consumption, only if you got free electric, which i have.
So buy them... |
|
|
|
update...1 saturn, 4 days, 3btc
You are doing quite well, my Jupiter has been hashing since the morning of the 9th and I'm at 4.8 Was only able to get ~120-150 the first few days and since .95 I've been seeing ~420GH/s. I'm really hoping we see a new firmware soon that fixes whatever is causing my now over 900,000 error'd shares. Set your min diff to 256 or 512 on the pool. The miner sends a lot bad shares when it changes diff. It actually seems to be working. Since switching, I've mined over 100k accepted shares with only 256 stale and no 'dupes' or 'other' errors. The best part is that for the first time ever I saw it break 500GH/s (currently at 495). I'm cautiously optimistic.I had tried setting the min diff @ 256 before .95 and didn't notice an improvement. edit... just as I typed this I started receiving 'other' errors again. Over 12k errors and counting. Hash rate down too. Try 512. You want it high enough that the pool won't change it to the miner, that's when it sends the 'other' errors for me. This is over 24 hrs for me since raising the min diff: 501.80 GH/s 11,395k (99.91%) 9984 / 9984 / 0 |
|
|
|
update...1 saturn, 4 days, 3btc
You are doing quite well, my Jupiter has been hashing since the morning of the 9th and I'm at 4.8 Was only able to get ~120-150 the first few days and since .95 I've been seeing ~420GH/s. I'm really hoping we see a new firmware soon that fixes whatever is causing my now over 900,000 error'd shares. Set your min diff to 256 or 512 on the pool. The miner sends a lot bad shares when it changes diff. |
|
|
|
|
Thanks, I fixed it. But either way, min or static, make it high enough that it won't change seems to be the solution. Unless KNC decides to fix it on their end.
|
|
|
|
|
Show Posts
