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

[reb0rn21]

My pps went down after I changed the sievesize from 1M to 2M.  Should I be worried, or is this "normal"?

its normal

[1542769285]

1542769285

[1542769285]

1542769285

[notlist3d]

-hp6 released!

Lots of changes in this release. Here's a list of notable changes:
 * Added fast divisibility tests before doing the expensive Fermat's test
 * Lots of other small optimizations
 * Introduced a new experimental tuning parameter "sievepercentage". Default value is 10, minimum is 1, maximum is 100.
 * Added new RPC command "getchainspermin"
 * Added the following information to "getmininginfo": chainspermin, difficulty, sievepercentage, and sievesize
 * Attempt to fix the random crash while mining

My PPS on mainnet went up 23% with this release with difficulty >= 9 on mainnet. This release attempts to fix the random crash while mining. I'm not sure if it's actually fixed because I have heard both positive and negative reports. The crash is more likely with high number of cores. 16 and 32 core machines are suffering the most.

The "sievepercentage" parameter is there for people to experiment with. It limits how many base primes are used to filter out candidate multipliers in the sieve. 8% seems optimal for testnet but I have no idea about mainnet.

This build is doing horrible for me. Dropped down to 9 blocks last hour, and 5 this one (almost at the end of the hour). Was getting between 8 and 20 the last build, even after diff 9. Gonna give it one more hour of variation, then switch back. My servers restart primecoind upon crashing, so could the reduction be from multiple crashes? Any explanation?

Can we change "sievepercentage" from debug console? My primecoin.conf is not working no matter what I try. I've literally tried everything.

Same here on not getting primecoin.conf to work.  But it's probley me.

[jubalix]

It is very much like comparing apples and oranges. For Primecoin, the integer part of difficulty determines the required probable prime chain length. E.g. if difficulty is 9.07233632, a probable prime chain of length 9 is required. The fractional part is used to determine how many length-9 chains are accepted. It scales logarithmically so that going from 9.8 to 9.9 is a lot harder than going from 9.1 to 9.2. The details for the fractional part are in Sunny King's paper.

The current algorithm also does more work for longer target chain lengths. That's why PPS numbers are also dropping.

Thanks Mikael, I read that it takes a 30 fold increase in processing power to increase difficulty by 1 . . . if so difficult to imagine difficultly ever climbing beyond 12 or 13.

999/(13*13) =  5.9 per block

i thing there are about 1000x optimization left in the code....at least

[Tamis]

My pps went down after I changed the sievesize from 1M to 2M.  Should I be worried, or is this "normal"?

it's normal !

[OnlyC]

sievepercentage=1
sievesize=1000000

with sievepercentage=1,  I got biggest PPS and more chainspermin. Is it good?

[FreeTrade]

Thanks Mikael, I read that it takes a 30 fold increase in processing power to increase difficulty by 1 . . . if so difficult to imagine difficultly ever climbing beyond 12 or 13.

999/(13*13) =  5.9 per block

i thing there are about 1000x optimization left in the code....at least

so . . . 999/(15*15) =  4.44 per block

[OnlyC]

Thanks Mikael, I read that it takes a 30 fold increase in processing power to increase difficulty by 1 . . . if so difficult to imagine difficultly ever climbing beyond 12 or 13.

999/(13*13) =  5.9 per block

i thing there are about 1000x optimization left in the code....at least

so . . . 999/(15*15) =  4.44 per block

I think diff at 12 is the time GPUminer approach

[rethaw]

Experimenting with sievepercentage and found 100% caused a segfault.

[maco]

sievepercentage=1
sievesize=1000000

with sievepercentage=1,  I got biggest PPS and more chainspermin. Is it good?

Good question.. can anyone attest to this?

[jubalix]

ok hp-6, has now gone a bit above hp-5

is it - command to %sieve etc?

[overc]

How much time it takes to found a block?
I just using this primecoin-hp on my i7 with the mining speed about 4000-5000 pps for couple of days and still nothing...
Is it how it should be?

[LlamaMaster]

How much time it takes to found a block?
I just using this primecoin-hp on my i7 with the mining speed about 4000-5000 pps for couple of days and still nothing...
Is it how it should be?

I've been consistently finding blocks once per day with my Core 2 Quad 9400 OC'ed to 3.5GHz on the second windows client.  My pps is usually around 2500, so I'm either very lucky or something is wrong on your end. 

[gigawatt]

I've been consistently finding blocks once per day with my Core 2 Quad 9400 OC'ed to 3.5GHz on the second windows client.  My pps is usually around 2500, so I'm either very lucky or something is wrong on your end. 

I can attest to you being lucky.  I've been running a constant ~2700 PPS for almost 48 hours and haven't found squat.
Running Sieve% 10, SieveSize 1000000

[maco]

Went from 900 PPS to 300 - 500 PPS for HP6. anyone with similar results? and why are we going down in PPS?

[jjiimm_64]

How much time it takes to found a block?
I just using this primecoin-hp on my i7 with the mining speed about 4000-5000 pps for couple of days and still nothing...
Is it how it should be?

I've been consistently finding blocks once per day with my Core 2 Quad 9400 OC'ed to 3.5GHz on the second windows client.  My pps is usually around 2500, so I'm either very lucky or something is wrong on your end. 

your very lucky:

primespersec: 21575
chainspermin: 56
immature: 12.34  (about 12 hours ago)

[jubalix]

is it


 primecoind  -sievepercentage 50 --daemon

? for  sievepercentage = 50%

[maco]

/primecoin-hp/src# primecoind stop
error: incorrect rpcuser or rpcpassword (authorization failed)

Your primecoin daemon was started with a different password in the config file. Just kill it off by typing:

Code:

killall primecoind

Same thing over, and over again. I have killed it, and hes coming back.

[rethaw]

/primecoin-hp/src# primecoind stop
error: incorrect rpcuser or rpcpassword (authorization failed)

Your primecoin daemon was started with a different password in the config file. Just kill it off by typing:

Code:

killall primecoind

Same thing over, and over again. I have killed it, and hes coming back.

Code:

ps aux | grep *.sh

Find the script that is restarting it and kill it using "kill pid".

[hasle2]

/primecoin-hp/src# primecoind stop
error: incorrect rpcuser or rpcpassword (authorization failed)

Your primecoin daemon was started with a different password in the config file. Just kill it off by typing:

Code:

killall primecoind

Same thing over, and over again. I have killed it, and hes coming back.

If you followed Mikaelh's build instructions then you have a script running that restarts primecoind when you kill it. You need to kill the run-primecoin script first then primecoind.

[dudeguy]

My pps went down after I changed the sievesize from 1M to 2M.  Should I be worried, or is this "normal"?

it's normal !

Question. Any way to change sieve % in Debug console (Windows QT)?