Quote from: mdude77 on May 19, 2013, 06:53:42 PM

Quote from: gyverlb on May 19, 2013, 06:32:10 PM

Quote from: DrHaribo on May 19, 2013, 05:55:04 PM

Sorry, we just had a couple minutes of downtime again. bitcoind 0.8.1 seems to be a real cpu and memory hog sometimes, never saw such issues with 0.7.2. Going to try to free up more resources on the server where it runs.

Quote from: Xian01 on May 19, 2013, 03:24:07 AM

1. Ability to sort workers alphabetically

Yeah, I'll probably make that the way it is sorted.

Quote from: Xian01 on May 19, 2013, 03:24:07 AM

2. Display my reward of each mined block on the Blocks (Income) page

That's coming.

There's a problem with some very large (in bytes) transactions slowing bitcoind RPC interface (getblocktemplate mainly) currently, p2pool users are battling with it. I find the latest git version is twice faster (but still slower than the average we are accustomed to).

I don't think it's size related. I think it's time related. Like there's a leak somewhere or something. Mine starts low and slowly gets larger.

M

bitcoind getmininginfo result:

Code:

{
"blocks" : 236952,
"currentblocksize" : 49792,
"currentblocktx" : 122,
"difficulty" : 11187257.46136079,
"errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"pooledtx" : 1693,
"testnet" : false
}

Notice the pooledtx? There are lots of transactions waiting to go into a block. And I use aggressive settings (latest git with minrelaytxfee set to 0.005) to filter low fees transactions: blockchain.info reports more than 2300 tx totalling 13MB. So ordinary bitcoind installations are suffering right now.