[XPM] [ANN] Primecoin High Performance | HP14 released!

[Tamis]

blockchain download is VERY slow right now, my guess is that a lot of people just compiled and we are all downloading at the same time.

I'm sure there is a way to keep the already downloaded blockchain with hp9, but I wasn't sure so started fresh after compiling.

edit :

Here is what I get with HP10 on one server :

CPD went from 1.31 to 2.75
PPS went from 2k to 2.7k

Next is tweaking sieveextensions...

[1534303496]

1534303496

[1534303496]

1534303496

[1534303496]

1534303496

[1534303496]

1534303496

[1534303496]

1534303496

[mikaelh]

-hp10 released! Downloads are on the first page as usual.

Changes in -hp10:
 * Major rewrite of the sieve to support extending the sieve (originally implemented by jh000).
 * Added a new parameter 'sieveextensions' which controls how many times the sieve is extended.
 * Removed the problematic and unnecessary fast-division test.
 * Changed the value of nL1CacheElements to 224000 which is slightly faster (thanks to nushor on IRC).
 * The 'roundsievepercentage' parameter is gone. The round primorial is now automatically adjusted.
 * New RPC command 'listtopprimes' by Sunny.

[Trillium]

-hp10 released! Downloads are on the first page as usual.

Changes in -hp10:
 * Major rewrite of the sieve to support extending the sieve (originally implemented by jh000).
 * Added a new parameter 'sieveextensions' which controls how many times the sieve is extended.
 * Removed the problematic and unnecessary fast-division test.
 * Changed the value of nL1CacheElements to 224000 which is slightly faster (thanks to nushor on IRC).
 * The 'roundsievepercentage' parameter is gone. The round primorial is now automatically adjusted.
 * New RPC command 'listtopprimes' by Sunny.

Thanks for the update!

[reb0rn21]

gr8 work as usual !

I presume we gona see a lot more development in future, looks like there is always something new to add and optimize even just for CPU

[Entz]

Great work indeed, thanks!

CPD is more than double what it was before.

[atariguy]

blockchain download is VERY slow right now, my guess is that a lot of people just compiled and we are all downloading at the same time.

I'm sure there is a way to keep the already downloaded blockchain with hp9, but I wasn't sure so started fresh after compiling.

If you're using Windows, simply replace primecoind and primecoin-qt and start it.

[Tamis]

i7 3370k @ 4400 :

{
"blocks" : 132521,
"chainspermin" : 38,
"chainsperday" : 3.16242444,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 9.78874415,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"primespersec" : 3267,
"pooledtx" : 0,
"sieveextensions" : 6,
"sievepercentage" : 10,
"sievesize" : 1000000,
"testnet" : false
}

Very nice work mikaelh !

[atariguy]

Great work indeed, thanks!

CPD is more than double what it was before.

Just hope the same thing doesn't happen to the difficulty now... 

[ivanlabrie]

I start primecoin and it crashes...  

Used to work fine and suddenly started acting out...replaced with the new hp10 and same thing.
Gonna have to fiddle some more with it. ARGH

[Tamis]

Difficulty is clearly on the rise again !

[redphlegm]

Great work indeed, thanks!

CPD is more than double what it was before.

Just hope the same thing doesn't happen to the difficulty now... 

Pretty sure this will push us into 10-chain territory.

[cabin]

Is there a guide on how to compile this on windows?

[manawenuz]

I pushed some big optimizations for -hp10 to github so that more people can test them.

it was one hell of a optimiziation on my 2650s i went from ~2.6 to 5.9-6.0 ch/d
i got a meaningful boost on my 5636 and 5620s as well , but on my Pentium something something (socket 1156) i didn't get any boost.
i guess it's either because it's only dual core or that it lacks some instructions (i doubt it )

[jjiimm_64]

If you want to get an estimation of your block/day :
Take one minus the decimal part of the difficulty and multiply it with your chain/day.

block/day = (1 - dec(difficulty) ) * chainsperday

From your example :
    "chainsperday" : 0.28633614,
    "difficulty" : 9.68146938,
block/day = (1 - 0.68146938) * 0.28633614 = 0,091206828 = around one block every 11 days !

firstly, finally a forum search where i found what I was looking for

secondly..  since we dont use the whole number of the diff, can I assume that the chainsperday calculation takes into account the whole number?

with the example

From your example :
    "chainsperday" : 0.28633614,
    "difficulty" : 9.68146938,
block/day = (1 - 0.68146938) * 0.28633614 = 0,091206828 = around one block every 11 days !

what about "difficulty" : 10.68146938,?   what am i missing?

[glongsword]

...
secondly..  since we dont use the whole number of the diff, can I assume that the chainsperday calculation takes into account the whole number?
...
what about "difficulty" : 10.68146938,?   what am i missing?

I believe the chainsperday is the number of integer-part-of-the-difficulty-length chains the miner expects to find each day.  I have no idea how it actually works, so maybe this is a gross simplification, but I believe it finds about that number of 10 length chains in your example, but only (1-.68146938)*100% of those chains that it finds are going to be accepted by the other miners (they have to have some property that only that fraction of the chains satisfy).  At least that makes sense if the formula is correct, which I'm not sure of.

[SlyWax]

If you want to get an estimation of your block/day :
Take one minus the decimal part of the difficulty and multiply it with your chain/day.

block/day = (1 - dec(difficulty) ) * chainsperday

From your example :
    "chainsperday" : 0.28633614,
    "difficulty" : 9.68146938,
block/day = (1 - 0.68146938) * 0.28633614 = 0,091206828 = around one block every 11 days !

firstly, finally a forum search where i found what I was looking for

secondly..  since we dont use the whole number of the diff, can I assume that the chainsperday calculation takes into account the whole number?

with the example

From your example :
    "chainsperday" : 0.28633614,
    "difficulty" : 9.68146938,
block/day = (1 - 0.68146938) * 0.28633614 = 0,091206828 = around one block every 11 days !

what about "difficulty" : 10.68146938,?   what am i missing?

There is a small add-on I should do here, is that the formula doest take into account the chain of higher length than the current.
So to be exact you should add the difficulty difference between the two chain length times the chainsperday.
After Sunny white paper the difficulty difference between the two chain length should be around 36x.
I don't know if this number is still accurate between 9 and 10 chain length.

Anyway you should add :  chainsperday/36 (and again (chainsperday/36)/36 ) to your calculation, witch is not a big difference.

From the example : 0,091206828 + 0.28633614 / 36 = 0,091206828 + 0,007953782 = 0,09916061
So well around one block every 10 days

As for diff 10.68146938 the chainperday should not be the same.

[Dumbo]

so does anyone know how to replenish the keypool for solo mining on different servers?

I tried

Help>Debug>Console ...then Keypool = 1000

it threw a error -- > "Method not found"


Next I made a primecoin.conf file and put setkeypool = 1000 in that...

How do I know if that worked?

[Trillium]

Difficulty is clearly on the rise again !

http://192.241.170.170/

Actually, the difficulty is CLEARLY stable at the moment. It has increased <5% over diff 9 in the last two weeks.

The optimizations made in HP10 may or may not increase block rate and hence the network may increase the difficulty, although HP10 has been out for a while now and the diff has barely budged, so it's not looking like we'll see an increase.

[Tamis]

What do you mean out for a while ?

It was released yesterday !

[rdebourbon]

What do you mean out for a while ?

It was released yesterday !

The major sieve updates were made about 10 days ago according to git.. So those who build from source have had the update for a while..