As Kano said what matter is p2pools shares. 1 p2pool share ~= 600 difficulty 1 shares.
If you look in the p2pool window you should see a line that says something like:
"Shares 3068 (Oprhan 82, Dead 16) ...."
THOSE SHARES are the ones in the share chain. The payments are made on the % of shares you have in the share chain (total - orphan - dead) at the time a block is found.
Also in the p2pool window you should see a line that says something like:
"Expected time to share 3.8 minutes".
If you got 12MH/s mining on p2pool is likely going to be a futile frustrating experience.
I estimate @ current difficulty (630) it will take:
630 * 2^32 / 12,000,000 = 225486 sec = 3758 minutes = 62 hours = 2.6 days to find a share ... ON AVERAGE.
Individual share time is random but a range of 20% to 500% is pretty common. So up to 12 days to find a share. Also you would statistically have a ~10% chance of it being orphaned and thus end up worthless.
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 748. (Read 2591916 times)
March 14, 2012, 08:30:51 AM
March 14, 2012, 05:08:22 AM
None of those shares are at payment difficulty.
... and if that figure is correct (12 MH/s CPU mining) then you won't see a payment share for A VERY LONG TIME.
... and if that figure is correct (12 MH/s CPU mining) then you won't see a payment share for A VERY LONG TIME.
March 14, 2012, 03:12:08 AM
I'm not seeing any shares pass by on my pool. I'm using an account flag as: the account isn't an account that's on bitcoind (not sure if that might be a problem).
Logs: http://p2pool.tgservers.com:9332/web/log
Code:
-a {BTCADDRESS}Logs: http://p2pool.tgservers.com:9332/web/log
The address you specify via '-a' doesnt have to be in your local wallet. Its not in mine, and I receive payments fine on the offline address.
How long have you been mining with that address, did/how many shares did you find?
(I have to ask this, you know ;-) )
Ente
No matter what options I do, it wont take my shares. Although, my miner seems to show the shares are accepting, just not p2pool.
(Screenshot of shares being accepted): http://puu.sh/kJ2b
March 14, 2012, 03:09:32 AM
I'm not seeing any shares pass by on my pool. I'm using an account flag as: the account isn't an account that's on bitcoind (not sure if that might be a problem).
Logs: http://p2pool.tgservers.com:9332/web/log
Code:
-a {BTCADDRESS}Logs: http://p2pool.tgservers.com:9332/web/log
The address you specify via '-a' doesnt have to be in your local wallet. Its not in mine, and I receive payments fine on the offline address.
How long have you been mining with that address, did/how many shares did you find?
(I have to ask this, you know ;-) )
Ente
March 14, 2012, 02:36:35 AM
I'm not seeing any shares pass by on my pool. I'm using an account flag as: the account isn't an account that's on bitcoind (not sure if that might be a problem).
Logs: http://p2pool.tgservers.com:9332/web/log
Code:
-a {BTCADDRESS}Logs: http://p2pool.tgservers.com:9332/web/log
March 14, 2012, 02:33:05 AM
How common is this error?
I'm trying to get all my machines mining to a single p2pool wallet by running it on my windows VPS, but I get this error quite frequently:
http://i40.tinypic.com/119cj7s.png
I'm trying to get all my machines mining to a single p2pool wallet by running it on my windows VPS, but I get this error quite frequently:
http://i40.tinypic.com/119cj7s.png
Common. Don't use bitcoin-gt (GUI client) use bitcoind (command line daemon). I have never seen bitcoind crash.
DAT,
if you're on Linux, bitcoind on windows crashes as well, even if a little less than bitcoin-qt.
spiccioli
March 13, 2012, 09:30:56 PM
How common is this error?
I'm trying to get all my machines mining to a single p2pool wallet by running it on my windows VPS, but I get this error quite frequently:
http://i40.tinypic.com/119cj7s.png
I'm trying to get all my machines mining to a single p2pool wallet by running it on my windows VPS, but I get this error quite frequently:
http://i40.tinypic.com/119cj7s.png
Common. Don't use bitcoin-gt (GUI client) use bitcoind (command line daemon). I have never seen bitcoind crash.
In that case, I guess something more fundamental has gone wrong given my latest error:
March 13, 2012, 09:24:12 PM
How common is this error?
I'm trying to get all my machines mining to a single p2pool wallet by running it on my windows VPS, but I get this error quite frequently:
http://i40.tinypic.com/119cj7s.png
I'm trying to get all my machines mining to a single p2pool wallet by running it on my windows VPS, but I get this error quite frequently:
http://i40.tinypic.com/119cj7s.png
Common. Don't use bitcoin-gt (GUI client) use bitcoind (command line daemon). I have never seen bitcoind crash.
March 13, 2012, 09:16:10 PM
How common is this error?
I'm trying to get all my machines mining to a single p2pool wallet by running it on my windows VPS, but I get this error quite frequently:
http://i40.tinypic.com/119cj7s.png
I'm trying to get all my machines mining to a single p2pool wallet by running it on my windows VPS, but I get this error quite frequently:
http://i40.tinypic.com/119cj7s.png
March 13, 2012, 05:16:38 PM
Woot, just found my first block for P2Pool, and I have to say the bonus for block finding is quite nice =)
2012-03-13 18:11:38.693438 GOT BLOCK FROM MINER! Passing to bitcoind! http://blockexplorer.com/block/00000000000009f88414de4de93c17b5ddcff9f8d61133ff95a9fdebee6cc705
2012-03-13 18:11:38.693559
2012-03-13 18:11:38.736916 GOT SHARE! 2 e866bdc6 prev 70dbc5de age 2.19s
2012-03-13 18:11:38.747592
2012-03-13 18:11:38.747885 GOT BLOCK FROM PEER! Passing to bitcoind! e866bdc6 bitcoin: http://blockexplorer.com/block/00000000000009f88414de4de93c17b5ddcff9f8d61133ff95a9fdebee6cc705
Just happened to catch it as I was sitting down =)
2012-03-13 18:11:38.693438 GOT BLOCK FROM MINER! Passing to bitcoind! http://blockexplorer.com/block/00000000000009f88414de4de93c17b5ddcff9f8d61133ff95a9fdebee6cc705
2012-03-13 18:11:38.693559
2012-03-13 18:11:38.736916 GOT SHARE! 2 e866bdc6 prev 70dbc5de age 2.19s
2012-03-13 18:11:38.747592
2012-03-13 18:11:38.747885 GOT BLOCK FROM PEER! Passing to bitcoind! e866bdc6 bitcoin: http://blockexplorer.com/block/00000000000009f88414de4de93c17b5ddcff9f8d61133ff95a9fdebee6cc705
Just happened to catch it as I was sitting down =)
March 13, 2012, 12:02:50 PM
Edit: and I should also add that adding a resource scheduling and logging service on top of p2pool does seem a bit odd.
Other than the scheduling part it's all already there.
... and scheduling access to mining bitcoins on a 10 second LP pool?
I'd be interested to see how they do that
A BOINC worker can be anything, so you could for example just log shares submitted to the sharechain as "work done" and if there's no new client update, push just some dummy work (like a 0 byte file or so).Other than the scheduling part it's all already there.
... and scheduling access to mining bitcoins on a 10 second LP pool?
I'd be interested to see how they do that
You would in the end just use it as some automated/extended package manager, but it's probably easier to set up and to use than a "real" package manager that would just install but not run a program.
March 12, 2012, 09:39:45 PM
...
Most BOINC projects obviously are research, looking at the BOINC page ... a small few may not be but that is unclear.
Hmm why am I quoting myself Most BOINC projects obviously are research, looking at the BOINC page ... a small few may not be but that is unclear.
Yeah I use mediawiki on my client servers for documentation of stuff - so?
It's a standard linux package on most distros ...
That's linux for you - opensource is great isn't it
I'm just wondering where I said BOINC should be used for Research?
That first word was "Most"
Which is correct.You can even use mediawiki for documenting your own local acts of graffiti vandalism
Not what it's ideal is or what it is commonly used for - but certainly usable in that situation also.
Back to my original post:
Actually BOINC and Bitcoin seem to be completely opposite ideals IMO.
Edit: and I should also add that adding a resource scheduling and logging service on top of p2pool does seem a bit odd.
Other than the scheduling part it's all already there.
... and scheduling access to mining bitcoins on a 10 second LP pool?
I'd be interested to see how they do that
March 12, 2012, 09:16:28 PM
BOINC = "Berkeley Open Infrastructure for Network Computing"
It is a middleware that is often used for benevolent volunteer computing - however you can run arbitrary projects on it and it is only an infrastructure/middleware. See for example BURP: http://en.wikipedia.org/wiki/Big_and_Ugly_Rendering_Project - a nice project, but not much more of a help for mankind than Bitcoin itself.
This is like stating mediawiki (the engine behind Wikipedia) should only be used for useful, publicly open kowledge hubs. It's perfectly fine (and possible) though to use it in a private installation too, with limited access and whatnot. There is no central authority that says what you can do with BOINC projects, but there's no need to market a potential bitcoin BOINC application as research project or even advertise it at some BOINC communities.
It is a middleware that is often used for benevolent volunteer computing - however you can run arbitrary projects on it and it is only an infrastructure/middleware. See for example BURP: http://en.wikipedia.org/wiki/Big_and_Ugly_Rendering_Project - a nice project, but not much more of a help for mankind than Bitcoin itself.
This is like stating mediawiki (the engine behind Wikipedia) should only be used for useful, publicly open kowledge hubs. It's perfectly fine (and possible) though to use it in a private installation too, with limited access and whatnot. There is no central authority that says what you can do with BOINC projects, but there's no need to market a potential bitcoin BOINC application as research project or even advertise it at some BOINC communities.
March 12, 2012, 08:59:56 PM
Actually BOINC and Bitcoin seem to be completely opposite ideals IMO.
https://bitcointalksearch.org/topic/donatehome-bitcoin-and-shared-computing-merge-63245
... https://bitcointalksearch.org/topic/m.747009
Basically Bitcoin mining is for making Bitcoins and Bitcoins have a monetary value and also a high cost to generate.
Projects like Folding and SETI are purely for science sake
There may be some financial gain to be made from them, but the basis is knowledge not money.
In these 2 cases: knowledge to solve medical problems or gain more knowledge about space.
Research
Most BOINC projects obviously are research, looking at the BOINC page ... a small few may not be but that is unclear.
March 12, 2012, 07:39:38 PM
Actually BOINC and Bitcoin seem to be completely opposite ideals IMO.
March 12, 2012, 05:44:17 PM
Other approach: If we had many programming hours (bounty for additional programmers?) to throw at the current p2pool: What would we want changed and updated? Only the graphing part? I dont see any fundamental problems to be solved?
I do. Simplicity. Yes, I realize that it's already pretty simple, but for the average Joe that just wants to point his miner somewhere and be done with it, it's not.
The BTC blockchain could be bootstrapped via a (monthly changed) torrent file (see http://www.coregrid.net/mambo/images/stories/TechnicalReports/tr-0139.pdf) included in the worker program.
BOINC "points" would only be there for fancy stats or so...
The advantage would be, that monthly the most recent mining, pool + bitcoin software as well as a verified snapshot of the blockchain automatically get pushed to the miners (considered you trust the BOINC server operator). Surely nothing for the most paranoid out there (there it might be needed to distribute the stuff as source code + build script, which is not something the average Windows user will be able to pull off easily) but it should be enough to be able to download the BOINC client, sign up for a project + enter a payout address.
March 12, 2012, 10:57:56 AM
No you shouldn't have to port anything. PyPy should just work with normal Python code. It's simply a different implementation of the standard Python interpreter. No difference in the language it interprets, just how it does it.
For one thing it has a built-in Just-in-time compiler powered by LLVM, which means that instead of the writers of a Python implementation needing to worry about how to create an efficient Just-in-time compiler, the work of people from the LLVM project, who are already experts in constructing such a compiler, can be leveraged.
For one thing it has a built-in Just-in-time compiler powered by LLVM, which means that instead of the writers of a Python implementation needing to worry about how to create an efficient Just-in-time compiler, the work of people from the LLVM project, who are already experts in constructing such a compiler, can be leveraged.
This made me curious, so I am running p2pool with pypy as we speak. It seems to be working fine, but I'll watch it for a day or two and see if there are any abnormalities.
March 12, 2012, 10:27:47 AM
No you shouldn't have to port anything. PyPy should just work with normal Python code. It's simply a different implementation of the standard Python interpreter. No difference in the language it interprets, just how it does it.
For one thing it has a built-in Just-in-time compiler powered by LLVM, which means that instead of the writers of a Python implementation needing to worry about how to create an efficient Just-in-time compiler, the work of people from the LLVM project, who are already experts in constructing such a compiler, can be leveraged.
For one thing it has a built-in Just-in-time compiler powered by LLVM, which means that instead of the writers of a Python implementation needing to worry about how to create an efficient Just-in-time compiler, the work of people from the LLVM project, who are already experts in constructing such a compiler, can be leveraged.
March 12, 2012, 09:59:14 AM
Just as info.
I have been running bitcoind bitcoin-qt p2pool and multiple miners on different ARM boards.
While the miners and bitcoind and Bitcoin-QT run without problems and little Cpu and modest RAM usage on a 600Mhz ARM
p2pool consumes to much CPU power.
The consumption of CPu power is largely scaling with the amount of shares distributed by the miners connected.
I found a miner with ~ 400Mh/s to be to CPU consuming for a 600Mhz and a 1000Mhz ARM CPU.
If the CPU power isn't sufficient it triggers the effect that it works for a while ~45 min.
Afther that the amount of "Timed out while getting work from p2pool" raises significantly.
Other the whole time the p2pool client starts lagging behind the network's time/share count
and finally ends up going unsync afther ~ 60 min.
I will try on my pandaboard these days.
Interesting. Have you tried an alternative Python implementation like PyPy? I think that would be what I would try first, but also - in part - because I think PyPy is cool I have been running bitcoind bitcoin-qt p2pool and multiple miners on different ARM boards.
While the miners and bitcoind and Bitcoin-QT run without problems and little Cpu and modest RAM usage on a 600Mhz ARM
p2pool consumes to much CPU power.
The consumption of CPu power is largely scaling with the amount of shares distributed by the miners connected.
I found a miner with ~ 400Mh/s to be to CPU consuming for a 600Mhz and a 1000Mhz ARM CPU.
If the CPU power isn't sufficient it triggers the effect that it works for a while ~45 min.
Afther that the amount of "Timed out while getting work from p2pool" raises significantly.
Other the whole time the p2pool client starts lagging behind the network's time/share count
and finally ends up going unsync afther ~ 60 min.
I will try on my pandaboard these days.
.Other than that, I think it might be worth the effort to dig into the Python code and take a look at what it is that consumes so much CPU power/RAM. In my experience with Python, a very minor - and seemingly unimportant change - can easily cause a 10x speedup. Simply because the Python code itself is so opaque, in the sense that not many people know what a certain line of Python code actually translate into machine code wise. I can't help think that the current Python code *can* be made to run on older hardware, it just requires some CPU- and RAM-profiling of the code, and making the according adjustments. This has - understandably - not been forrestv's highest priority so far.
Well tonights tests will show if a dual core ARM is sufficient.
As far as i understand it PyPy is a language substitute for python.
Wich would meant i would have to port most of the software ?
I guess im lacking the time to do so.
I would also like a implementation nearer to hardware but that will take some efforts.
(assembler and C ftw
) March 12, 2012, 08:15:06 AM
Just as info.
I have been running bitcoind bitcoin-qt p2pool and multiple miners on different ARM boards.
While the miners and bitcoind and Bitcoin-QT run without problems and little Cpu and modest RAM usage on a 600Mhz ARM
p2pool consumes to much CPU power.
The consumption of CPu power is largely scaling with the amount of shares distributed by the miners connected.
I found a miner with ~ 400Mh/s to be to CPU consuming for a 600Mhz and a 1000Mhz ARM CPU.
If the CPU power isn't sufficient it triggers the effect that it works for a while ~45 min.
Afther that the amount of "Timed out while getting work from p2pool" raises significantly.
Other the whole time the p2pool client starts lagging behind the network's time/share count
and finally ends up going unsync afther ~ 60 min.
I will try on my pandaboard these days.
Interesting. Have you tried an alternative Python implementation like PyPy? I think that would be what I would try first, but also - in part - because I think PyPy is cool I have been running bitcoind bitcoin-qt p2pool and multiple miners on different ARM boards.
While the miners and bitcoind and Bitcoin-QT run without problems and little Cpu and modest RAM usage on a 600Mhz ARM
p2pool consumes to much CPU power.
The consumption of CPu power is largely scaling with the amount of shares distributed by the miners connected.
I found a miner with ~ 400Mh/s to be to CPU consuming for a 600Mhz and a 1000Mhz ARM CPU.
If the CPU power isn't sufficient it triggers the effect that it works for a while ~45 min.
Afther that the amount of "Timed out while getting work from p2pool" raises significantly.
Other the whole time the p2pool client starts lagging behind the network's time/share count
and finally ends up going unsync afther ~ 60 min.
I will try on my pandaboard these days.
.Other than that, I think it might be worth the effort to dig into the Python code and take a look at what it is that consumes so much CPU power/RAM. In my experience with Python, a very minor - and seemingly unimportant change - can easily cause a 10x speedup. Simply because the Python code itself is so opaque, in the sense that not many people know what a certain line of Python code actually translate into machine code wise. I can't help think that the current Python code *can* be made to run on older hardware, it just requires some CPU- and RAM-profiling of the code, and making the according adjustments. This has - understandably - not been forrestv's highest priority so far.
Jump to: