Topic: Primecoin chainspermin, p/sec, sievesize (Read 1437 times)

How many primecoins do you have? Curious what a first-adopter could accumulate

I would also love to know the answer to this question. Been mining ever since they came out and never understood what sievesize meant or what the best one is.

You're right. Big improvement in "primespersec". But I also wonder if this is the best setting because it changes the "chainspermin" too. I have the same question.

{
"blocks" : 88535,
"chainspermin" : 5,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 9.26852816,
"errors" : "",
"generate" : true,
"genproclimit" : 7,
"roundsievepercentage" : 30,
"primespersec" : 3561,
"pooledtx" : 0,
"sievepercentage" : 10,
"sievesize" : 4000000,
"testnet" : false
}


{
"blocks" : 88485,
"chainspermin" : 9,
"currentblocksize" : 1713,
"currentblocktx" : 2,
"difficulty" : 9.26707864,
"errors" : "",
"generate" : true,
"genproclimit" : 7,
"roundsievepercentage" : 30,
"primespersec" : 5856,
"pooledtx" : 2,
"sievepercentage" : 10,
"sievesize" : 1000000,
"testnet" : false
}


{
"blocks" : 88506,
"chainspermin" : 14,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 9.26766801,
"errors" : "",
"generate" : true,
"genproclimit" : 7,
"roundsievepercentage" : 30,
"primespersec" : 8849,
"pooledtx" : 0,
"sievepercentage" : 10,
"sievesize" : 100000,
"testnet" : false
}

I am using the HP8 client as well.

I have an i7 3770K overclocked @ 4ghz and I'm getting 5762 primespersec.

Hi guys,

I'm trying to work my way up to posting in the actual Primecoin thread but for now will have to post here.

I've made the switch to HP8 client and noted a large increase in p/s but I can't find an answer to a few basics of Primecoin.

To judge performace am I only interested in p/sec or does chainspermin matter as well?

What is sievesize? chainspermin and p/s change if I vary the sievesize but what does this actually mean? I've seen some wanting to go for the largest size possible such as 4 000 000 but my p/s goes down a lot if I try this. On my i7 3820 if I use the lowest sievesize, 100 000, I get the best results.

2 000 000:

    "blocks" : 83331,
    "chainspermin" : 8,
    "currentblocksize" : 1820,
    "currentblocktx" : 1,
    "difficulty" : 9.26782423,
    "errors" : "",
    "generate" : true,
    "genproclimit" : 7,
    "roundsievepercentage" : 30,
    "primespersec" : 3866,
    "pooledtx" : 1,
    "sievepercentage" : 10,
    "sievesize" : 2000000,
    "testnet" : false

100 000:

    "blocks" : 83318,
    "chainspermin" : 11,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 9.26746053,
    "errors" : "",
    "generate" : true,
    "genproclimit" : 7,
    "roundsievepercentage" : 30,
    "primespersec" : 7495,
    "pooledtx" : 0,
    "sievepercentage" : 10,
    "sievesize" : 100000,
    "testnet" : false