primecoind -sievepercentage 50 --daemon
? for sievepercentage = 50% 
Topic: [XPM] [ANN] Primecoin High Performance | HP14 released! - page 80. (Read 397645 times)
is it
primecoind -sievepercentage 50 --daemon
? for sievepercentage = 50%
primecoind -sievepercentage 50 --daemon
? for sievepercentage = 50% 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. 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?
your very lucky:
primespersec: 21575
chainspermin: 56
immature: 12.34 (about 12 hours ago)
Went from 900 PPS to 300 - 500 PPS for HP6. anyone with similar results? and why are we going down in PPS?
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
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. 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?
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 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?
ok hp-6, has now gone a bit above hp-5
is it - command to %sieve etc?
is it - command to %sieve etc?
sievepercentage=1
sievesize=1000000
with sievepercentage=1, I got biggest PPS and more chainspermin. Is it good?
sievesize=1000000
with sievepercentage=1, I got biggest PPS and more chainspermin. Is it good?
Good question.. can anyone attest to this?
Experimenting with sievepercentage and found 100% caused a segfault.
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
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
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
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
sievepercentage=1
sievesize=1000000
with sievepercentage=1, I got biggest PPS and more chainspermin. Is it good?
sievesize=1000000
with sievepercentage=1, I got biggest PPS and more chainspermin. Is it good?
My pps went down after I changed the sievesize from 1M to 2M. Should I be worried, or is this "normal"?
it's normal !
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.
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
-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? 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.
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.
My pps went down after I changed the sievesize from 1M to 2M. Should I be worried, or is this "normal"?
its normal
My pps went down after I changed the sievesize from 1M to 2M. Should I be worried, or is this "normal"?
-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? 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.
Can we change "sievepercentage" from debug console? My primecoin.conf is not working no matter what I try. I've literally tried everything.
just tried to compile hp6, go error
any ideas on how to fix this???
skay fixed
Code:
:~$ cd ~/primecoin/src
:~/primecoin/src$ sudo make -f makefile.unix USE_UPNP=-
Building LevelDB ...
make[1]: Entering directory `/home/ubuntu/primecoin/src/leveldb'
g++ -I. -I./include -fno-builtin-memcmp -pthread -DOS_LINUX -DLEVELDB_PLATFORM_POSIX -O2 -pthread -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -D_FILE_OFFSET_BITS=64 -I/home/ubuntu/primecoin/src -I/home/ubuntu/primecoin/src/obj -DUSE_IPV6=1 -I/home/ubuntu/primecoin/src/leveldb/include -I/home/ubuntu/primecoin/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -c db/._builder.cc -o db/._builder.o
db/._builder.cc:1:1: warning: null character(s) ignored [enabled by default]
db/._builder.cc:1:2: error: stray ‘\5’ in program
db/._builder.cc:1:2: error: stray ‘\26’ in program
db/._builder.cc:1:2: error: stray ‘\7’ in program
.....
db/._builder.cc:1:9: error: ‘Mac’ does not name a type
db/._builder.cc:1:158: error: expected unqualified-id before numeric constant
db/._builder.cc:1:167: error: ‘Firefox’ does not name a type
db/._builder.cc:1:3827: error: ‘This’ does not name a type
make[1]: *** [db/._builder.o] Error 1
make[1]: Leaving directory `/home/ubuntu/primecoin/src/leveldb'
make: *** [leveldb/libleveldb.a] Error 2
skay fixed
I feel like I'm sort of flying blind on sievepercentage. I don't know what it's supposed to be changing so I don't know whether to tweak it up or down. Comparatively speaking, I don't know if running default hp5 is better / worse than default hp6 for me since pps isn't a great metric to use.
Any suggestions / insight?
Any suggestions / insight?
Jump to: