Quote from: minim1ner on June 26, 2014, 05:50:39 PM

Quote from: HunterMinerCrafter on June 26, 2014, 04:31:27 PM

My patch to fix the time warp will already do this as a side effect. (Remember from our pm?)

Yes, it just was quiet for a while, I thought development is stuck, or William rejected pull request or something.

I got busy this week and simply haven't had the time to finish verification on the patch. By this weekend we can launch a testnet with it, and if we are all happy with the change we can initiate the fork when we're ready.

Quote

Quote

On what spec cpu? That is a pretty good production rate if it is just one core!

No, I use all 4 cores @1.6 ghz.

Ahh, that sounds a bit more reasonable. I thought you meant you were getting those rates from a single ~2ghz core, which would be quite a bit better than I would expect. At 4 cores these numbers are very much in line with what I'd expect.

Quote

Quote

I'm not sure how those parameters would affect anything...

It will spam just to 3 connections, not to 10 or whatever.

Heh, the problem is I'm a well connected node and have multiple people syncing from me at any given moment. From people using your patch i see a getblocks request for, say, block 10,000... so I send them 500 blocks, and they turn around and 10 seconds later issue a getblocks request from block 10,050 or so, so i send them the same 450 blocks again with 50 new blocks.... rinse, repeat. This creates a lot of overheads!