I'm not sure if I did this right, but I made a tweak to the "primemeter" section of the code to get a peek at what solving difficulty+1 would be like. If this is right, all I have to say is "oof".
If I've done this wrong, please tell me.I really
really hope I've done this wrong.
Original
main.cpp:
if (nMillisNow - nLogTime > 59000)
{
nLogTime = nMillisNow;
printf("%s primemeter %9.0f prime/h %9.0f test/h %4.0f %d-chains/h %3.6f chain/d\n", DateTimeStrFormat("%Y-%m-%d %H:%M:%S", nLogTime / 1000).c_str(), dPrimesPerMinute * 60.0, dTestsPerMinute * 60.0, dChainsPerMinute * 60.0, nStatsChainLength, dChainsPerDay);
}
Tweaked
main.cpp:
if (nMillisNow - nLogTime > 59000)
{
nLogTime = nMillisNow;
double next_prob = EstimateCandidatePrimeProbability(nPrimorialMultiplier, TargetGetLength(pblock->nBits));
double est_next = dChainsPerDay * next_prob;
printf("%s primemeter %9.0f prime/h %9.0f test/h %4.0f %d-chains/h %3.6f chain/d %u RoundPrimorial %3.6f est_next %3.6f next_prob\n", DateTimeStrFormat("%Y-%m-%d %H:%M:%S", nLogTime / 1000).c_str(), dPrimesPerMinute * 60.0, dTestsPerMinute * 60.0, dChainsPerMinute * 60.0, nStatsChainLength, dChainsPerDay, nPrimorialMultiplier, est_next, next_prob);
}
Result (1 vCPU VPS):
2013-08-22 15:23:44 primemeter 892352 prime/h 14610791 test/h 60 5-chains/h 0.153438 chain/d 47 RoundPrimorial 0.013593 est_next 0.088589 next_prob
2013-08-22 15:24:44 primemeter 878830 prime/h 14379729 test/h 0 5-chains/h 0.152076 chain/d 41 RoundPrimorial 0.013928 est_next 0.091584 next_prob
2013-08-22 15:25:44 primemeter 885159 prime/h 14521363 test/h 180 5-chains/h 0.152199 chain/d 43 RoundPrimorial 0.013710 est_next 0.090079 next_prob
2013-08-22 15:26:44 primemeter 877952 prime/h 14345645 test/h 60 5-chains/h 0.150436 chain/d 43 RoundPrimorial 0.013551 est_next 0.090079 next_prob
2013-08-22 15:27:44 primemeter 879141 prime/h 14404795 test/h 60 5-chains/h 0.152234 chain/d 43 RoundPrimorial 0.013713 est_next 0.090079 next_prob
So yeah,
0.152 chain/d now at diff 9, only
0.013 chain/d at diff 10?
I really hope I'm wrong.
edit: I did spot an inconsistency issue. chain/d is measured over the entire 60 second interval of various values for RoundPrimorial, but the est_next/next_prob values are based on the current value of it. I imaging it can skew the results +/- 10%.
