i mine with x6500 and mbpm with 100mhs on this pool, i get 8% doa, thats my only problem
What mining program are you using? |
|
|
|
Uh, what? p2pool is more susceptible to DoS than other pools... Would you mind explaining how/why? I usually think of a typical DDoS attack against a public mining pool address, perhaps you are referring to a different DoS method that I'm not considering. It's trivial to get the IPs of every p2pool miner, and spread the DDoS across them. Many (most?) mining pools can withstand far more bandwidth being thrown at them, than the equivalent in miners' connections, so the DDoS will require less bandwidth to pull off. Furthermore, since such a DDoS takes out the miners' connection, it effectively prevents any failover including solo mining. To contrast, not only do other pools have higher DDoS resistance in terms of bandwidth, but they generally keep their miners' IPs private, so when/if the pool goes down, the miners are free to failover to another pool. That's why you should use p2pmining.com to mine p2pool  |
|
|
|
Thats a great tool for checking server speeds thank you!!!
Your performance score of your server is 64/100, I tested a few other pools and most scored 90-100.
I also got the server not providing work fast enough errors on your server, but I was running queue 0 so that has a little to do with it.
I'm also on the west coast so my ping time are a little higher.
If you look in the performance review you can see what causes the 64/100 isn't the speed but the way p2pool forms it's webpages. |
|
|
|
I didn't jump ship yet  Just trying some experimenting. For me, cgminer 2.3 works better than 2.4. I must have some of the worst luck though. I jumped on Eclipse for a day and a few hours later that pool was down. Bah! I am thinking of starting a new p2pool with 2 min shares instead of 10second shares. This should reduce all the long polling and help with a lot of issues p2pool has. This may enable FPGAs to be usable with p2pool also. Any comments? Doesn't matter to me. If the server can't feed 'em fast enough though, it doesn't matter either way. It may be your local connection. The server is way under loaded. I don't have connection issues with my miners and I am half way across the country (USA) from my server. Check server speed at http://tools.pingdom.com/fpt/#!/HDAVmy8qr/p2pmining.com:9332 |
|
|
|
Getting FPGA's to mine on p2pool would be cool.
Is it possible to attack p2pool to slow work?
Is there any type of attack that can increase variance on a pool?
Have you updated bitcoind to 0.6.2 to prevent DoS?
I just compiled 0.6.99 a couple days ago I don't think a p2pool system can be DoS'd. |
|
|
|
I didn't jump ship yet Just trying some experimenting. For me, cgminer 2.3 works better than 2.4. I must have some of the worst luck though. I jumped on Eclipse for a day and a few hours later that pool was down. Bah! I am thinking of starting a new p2pool with 2 min shares instead of 10second shares. This should reduce all the long polling and help with a lot of issues p2pool has. This may enable FPGAs to be usable with p2pool also. Any comments? |
|
|
|
|
I think that this is a great test for the Bitcoin feasibility on a larger scale. This increase in transactions is nothing compared to the transaction volume once Bitcoin actually catches on. Bitcoin is going to evolve. The only guarantee in Bitcoin is change.
|
|
|
|
P2Pmining is currently the largest miner on P2Pool.
Is there some way you could set a static share difficulty or maybe just a higher dynamic difficulty based on your pool's overall hashrate? You could probably get away with 3000 difficulty shares at least. You can set share difficulty to what ever you want. If you want 3000 share difficulty just add +3000 to the end off your bitcoin-address-username. When you submit a 3000 difficulty share, it would be the same as if you submitted 3000 difficulty 1 shares. You will see more variance in your stats with higher difficulty shares, but it all works out the same in the end. I haven't tried experimenting with much higher difficulty to see if I get a smaller DOA rate. |
|
|
|
|
P2Pmining is currently the largest miner on P2Pool.
|
|
|
|
Maybe consider lower diff a bit and less longpool messages? I haven't share over last 24hrs...
I have only ~170MH/s and most of my worker get works are break by longpool reset.
In description it is about 10s between longpolls but in most cases i get longpool restart every 5s...
Also after upgrading to 11.1 i`m getting ALOT of dead on arrival (about 30% vs under 5% on 10.3), same worker and config.
Since you have a small rig, it might be worth mining at p2pmining.com. He runs a public, merged mining p2pool node with diff 1 shares designed for smaller miners. To get difficulty 1 share at p2pmining.com add a +1 to the end of your username/payout address. Larger miners may find it work better to submit higher difficulty shares. |
|
|
|
Just a comment: these monthly forced updates are not really practical for people who don't engulf their entire lives in Bitcoin. I was fortunate to have caught this update and the previous one because I just happened to check in here.
I will be away for the next 60 days. Hopefully my miners will still be working when I get back.
You can use P2Pmining.com and let me take care of the updates for you. |
|
|
|
|
I recently upgraded to the newest p2pool code. Others are reporting lower DOA rate with the new changes. We shale see.
|
|
|
|
|
What is the advantage, if any of using DGS vs PPLNS ? Or is this just two ways to skin the same cat?
|
|
|
|
SQL is fun Your love for it shows. I generally prefer to break up statements like this into a few separate queries and use the scripting language running the whole thing to glue the results together. I think it's much easier to read and maintain that way but that's me. I just started with the pool a couple days ago and I'm sorry if this is already answered but...how long after a block is confirmed do payouts go out? Also how does it work when I was only mining for some of the time during the first round? Finally, how do you mix the altcoin dividends into the payments? Do you sell them periodically? Thanks for this neat form of pool. After a block is confirmed 120 times your reward is available for payout. After your balance is greater than 0.5 then it is automatically paid. You can do an instant payout any time by signing a short message with your bitcoin address and submitting the signature. Alt coins are split between the miners who have registered there alt coin addresses. The way the alt coins are paid out is the same as bitcoins. This pool is PPLNS with a 24 hr history. That means any shares submitted in the last 24hrs when a block is found are used when calculating the reward. This prevents pool hoppers from gaining an unfair advantage. Thanks for trying my pool! |
|
|
|
Help simplify this SQL statement for daily miner payout graph data. It works, but is there a simpler way? Got crazy when I had to exclude orphaned blocks. SELECT DATE_FORMAT( FROM_UNIXTIME( t1.time ) , '%Y-%m-%d' )
DAY , UNIX_TIMESTAMP( DATE_FORMAT( FROM_UNIXTIME( t1.time ) , '%Y-%m-%d' ) ) TIMESTAMP, SUM(
SHARE * amount ) btc
FROM
(SELECT TIME, payouts.amount AS
SHARE , pool_blocks.amount
FROM `payouts` , `pool_blocks` ,
(SELECT MAX( TIME ) AS mtime
FROM pool_blocks)maxt
WHERE payouts.txid = pool_blocks.txid
AND pool_blocks.time > UNIX_TIMESTAMP( ) -60 *60 *24 *30
AND address = '1KgFh9kWBpz4TsX92xcx78VQ2Fo1jP2Ddx'
AND NOT (
maxt.mtime > pool_blocks.time
AND pool_blocks.confirmations =1
)
)t1
GROUP BY DAY
SQL is fun |
|
|
|
a that price why not FPGA? from what ive seen the good open source ones will keep their value
There are way more people buying GPUs than FPGAs, so it will be easier to sell later on. 7970 was only $450 from amazon. |
|
|
|
Just ordered a few more GPUs. A 5870,5970 and a new 7970.  |
|
|
|
Suggestions: Would you add ⊅BTC paid out per 24 hours, ⊅BTC paid out total? On the current miners page maybe list firstbits instead of full addresses? (So more stats can fit.  ) Would it be possible to have a subpool subsidy that a 6 GH miner could donate to those under 1 GH? Do you plan on having a drawing to give away a 5830 or 6870 for the subpool hashers who have hashed for at least, say one week between date to date? I will definitely put in the BTC paid data for each miner soon. I like your idea of using the firstbits for the addresses. I don't think that is possible with the current set up to address your third suggestion No plans an drawings yet. |
|
|
|
Here is the code in between p2pool code for further clarification: if pow_hash > target:
print 'Worker %s submitted share with hash > target:' % (request.getUser(),)
print ' Hash: %56x' % (pow_hash,)
print ' Target: %56x' % (target,)
elif header_hash in received_header_hashes:
print >>sys.stderr, 'Worker %s @ %s submitted share more than once!' % (request.getUser(), request.getClientIP())
else:
received_header_hashes.add(header_hash)
#Enter Share to database
try:
dbf_user = request.getUser()
dbuser_items = dbf_user.split('+')
db_diff = bitcoin_data.target_to_difficulty(target) * 1000
proxy_db = MySQLdb.connect(host="localhost",user="mysqluser",passwd="mysqlpassword",db="p2pmining")
pdb_c = proxy_db.cursor()
pdb_c.execute("""INSERT INTO miner_data (id,address,hashrate,timestamp,difficulty,ontime) VALUES (NULL, %s , %s , UNIX_TIMESTAMP() , %s, %s)""", (dbuser_items[0], db_diff * on_time, db_diff , on_time ) )
proxy_db.close()
except:
log.err(None, 'Error with database:')
#End Enter Share Code
pseudoshare_received.happened(bitcoin_data.target_to_average_attempts(target), not on_time, user)
self.recent_shares_ts_work.append((time.time(), bitcoin_data.target_to_average_attempts(target)))
while len(self.recent_shares_ts_work) > 50:
self.recent_shares_ts_work.pop(0)
local_rate_monitor.add_datum(dict(work=bitcoin_data.target_to_average_attempts(target), dead=not on_time, user=user)) Notoriety in the comments would be cool |
|
|
|
To promote openness, I thought I would release the Python code I add to the P2Pool code. The rest of the pool is in PHP. Later, I may record who actually finds shares and blocks so people interested in that data can see it. At the beginning of main.py In the WorkerBridge.got_response() in main.py after p2pool verifies that the proof of work hash is < the target. #Enter Share to database
try:
dbf_user = request.getUser()
dbuser_items = dbf_user.split('+')
db_diff = bitcoin_data.target_to_difficulty(target) * 1000
proxy_db = MySQLdb.connect(host="localhost",user="mysqluser",passwd="mysqlpassword",db="p2pmining")
pdb_c = proxy_db.cursor()
pdb_c.execute("""INSERT INTO miner_data (id,address,hashrate,timestamp,difficulty,ontime) VALUES (NULL, %s , %s , UNIX_TIMESTAMP() , %s, %s)""", (dbuser_items[0], db_diff * on_time, db_diff , on_time ) )
proxy_db.close()
except:
log.err(None, 'Error with database:')
###
That is it. |
|
|
|
|
Show Posts
