masterOfDisaster
|
 |
July 15, 2013, 04:23:37 AM |
|
I'm getting about the same rate but my CPU is way down like less than 20% most of the time. Anyway to allow it to use full CPU. Win 8 by the way.
In the console of the primecoin-qt you can enter setgenerate true -1
That allows all cores to be used. Do you have a "primecoin.conf" file on that machine?
|
|
|
|
|
|
|
|
The network tries to produce one block per 10 minutes. It does this by automatically adjusting how difficult it is to produce blocks.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
Armchair Miner
|
 |
July 15, 2013, 05:53:55 AM |
|
I got an exception running it with maybe 12 threads on 4 core i7 2660. Sorry, removed the error message and restarted the primecoin-qt. Will report details if it happens again.
|
|
|
|
achillez
|
 |
July 15, 2013, 05:56:29 AM |
|
thx one other dumb Q. Do I have to do anything to enable hp3 or is it built by default?
|
|
|
|
jubalix
Legendary
Offline
Activity: 2506
Merit: 1022
|
 |
July 15, 2013, 06:10:17 AM |
|
update hp3 falls over alot
|
|
|
|
96redformula
|
 |
July 15, 2013, 06:12:42 AM |
|
update hp3 falls over alot
What do you mean falls over?
|
|
|
|
glongsword
|
 |
July 15, 2013, 06:16:12 AM |
|
update hp3 falls over alot
What do you mean falls over? I'm having the same problem on my two computers; It throws random errors and quits every few hours. I Have to manually start the program again and start mining.
|
|
|
|
mhps
|
 |
July 15, 2013, 06:40:36 AM |
|
New version is out. It mainly adds a tuning parameter called -sievesize. Use it like this: primecoind -sievesize=2000000
@mikaelh to make sure ... the change of sievesize is not what Sunny was talking about in https://bitcointalk.org/index.php?topic=253662.msg2716964#msg2716964 , right? I have reduced sievesize from 2.5M to 50000 in several steps and the PSS indeed rises (not linearly). But I hope it's not just an illusion.
|
|
|
|
8bitPunk
Member

Offline
Activity: 70
Merit: 10
|
 |
July 15, 2013, 07:42:05 AM |
|
New version is out. It mainly adds a tuning parameter called -sievesize. Use it like this: primecoind -sievesize=2000000
@mikaelh to make sure ... the change of sievesize is not what Sunny was talking about in https://bitcointalk.org/index.php?topic=253662.msg2716964#msg2716964 , right? I have reduced sievesize from 2.5M to 50000 in several steps and the PSS indeed rises (not linearly). But I hope it's not just an illusion. Sieve size isn't directly what Sunny was talking about, but it is related. If you lower the amount of work you perform or the shorten the time you spend working on it before giving up, then you will throw away a lot of potential solutions unnecessarily. Lowering sieve size to 50,000 will raise PPS but it is an illusion.
|
BTC 18bPunkuginRBm1Xz9mcgj8mWJnHDAW5Th | Ł LTCgXEdyBdoQ9WdF6JHi7Pa2EWtzbDjG76 | Ψ ATEBiTLkLpAYeW5hQknUfSvnb7Abbgegku
|
|
|
altsay
|
 |
July 15, 2013, 08:07:24 AM |
|
Optimal sievesize might be 1000000, some people discussed on this topic.
|
|
|
|
mhps
|
 |
July 15, 2013, 09:27:23 AM |
|
New version is out. It mainly adds a tuning parameter called -sievesize. Use it like this: primecoind -sievesize=2000000
@mikaelh to make sure ... the change of sievesize is not what Sunny was talking about in https://bitcointalk.org/index.php?topic=253662.msg2716964#msg2716964 , right? I have reduced sievesize from 2.5M to 50000 in several steps and the PSS indeed rises (not linearly). But I hope it's not just an illusion. Sieve size isn't directly what Sunny was talking about, but it is related. If you lower the amount of work you perform or the shorten the time you spend working on it before giving up, then you will throw away a lot of potential solutions unnecessarily. Lowering sieve size to 50,000 will raise PPS but it is an illusion. Thanks for the explanation and for making the HP client. It's hard to determine where the illusion starts.. all I see is more PPS with lower sievesize.
|
|
|
|
8bitPunk
Member

Offline
Activity: 70
Merit: 10
|
 |
July 15, 2013, 09:47:24 AM |
|
mikaelh is awake and coding  Latest commit: Precompute two's inverses for all base primes. Idea taken from luke-jrIf you're on linux and compiling from the repo: Remember folks, if you're doing this, keep your primecoind updated: cd ~/primecoin git pull cd src make -f makefile.unix USE_UPNP=- primecoind stop sudo mv /usr/local/bin/primecoind /usr/local/bin/primecoind.old sudo mv primecoind /usr/local/bin/primecoind primecoind --daemon
|
BTC 18bPunkuginRBm1Xz9mcgj8mWJnHDAW5Th | Ł LTCgXEdyBdoQ9WdF6JHi7Pa2EWtzbDjG76 | Ψ ATEBiTLkLpAYeW5hQknUfSvnb7Abbgegku
|
|
|
dego
|
 |
July 15, 2013, 09:58:25 AM |
|
compiled and running on Ubuntu 13.04 64bit on a Phenom 1090 hexacore, getting around 4500 - 5000 pps (as before).
What should thelatest changements result in?
|
|
|
|
8bitPunk
Member

Offline
Activity: 70
Merit: 10
|
 |
July 15, 2013, 10:06:51 AM |
|
compiled and running on Ubuntu 13.04 64bit on a Phenom 1090 hexacore, getting around 4500 - 5000 pps (as before).
What should thelatest changements result in?
I wouldn't expect any increase in PPS resulting from this change (remember PPS is not a good performance metric)... The efficiency is in how quickly the sieve is setup, ready to weave then find the prime chains. Within the gensieveroundlimitms parameter (default 1000 milliseconds) primecoind should spend less time setting up the sieve and more time finding the primes before it moves onto the next round.
|
BTC 18bPunkuginRBm1Xz9mcgj8mWJnHDAW5Th | Ł LTCgXEdyBdoQ9WdF6JHi7Pa2EWtzbDjG76 | Ψ ATEBiTLkLpAYeW5hQknUfSvnb7Abbgegku
|
|
|
dego
|
 |
July 15, 2013, 10:09:08 AM |
|
ok. So it will be very hard to see if there are perfomance inprovements on the real network...
|
|
|
|
mika1977
|
 |
July 15, 2013, 10:09:12 AM |
|
Around 100 hours without a single block this with 20k+ PPS. I try every build. Now with latest - hp3 Please somebody paste your config file, may be there is my mistake.
|
|
|
|
dego
|
 |
July 15, 2013, 10:13:13 AM |
|
rpcuser=username rpcpassword=password sievesize=1000000 gen=1
As I understand it right, adding sievesize=1000000 shouldn't be necessary as 1M is already the default sievesize... I had 5 blocks yesterday during ~15hrs mining at 4k - 5k pps. Today no blocks have been yet found during more than 3hrs @ 4.5k pps.
|
|
|
|
itod
Legendary
Offline
Activity: 1974
Merit: 1075
^ Will code for Bitcoins
|
 |
July 15, 2013, 10:18:24 AM |
|
Around 100 hours without a single block this with 20k+ PPS. I try every build. Now with latest - hp3 Please somebody paste your config file, may be there is my mistake.
On Linux: gen=1 rpcuser=primecoinrpcuser rpcpassword=primecoinrpcpassword On Win: no config file, starting the mining manually with setgenerate. If you have config file just delete it, maybe there really is something wrong in it, but i doubt it, probably just bad luck.
|
|
|
|
8bitPunk
Member

Offline
Activity: 70
Merit: 10
|
 |
July 15, 2013, 10:21:23 AM |
|
Around 100 hours without a single block this with 20k+ PPS. I try every build. Now with latest - hp3 Please somebody paste your config file, may be there is my mistake.
The config files are pretty hard to mess up, and even without one you can do: "setgenerate true" and it will be mining with all the defaults. What we are all seeing is the amount of computation required to generate a prime chain now that the difficulty is 8.8.
|
BTC 18bPunkuginRBm1Xz9mcgj8mWJnHDAW5Th | Ł LTCgXEdyBdoQ9WdF6JHi7Pa2EWtzbDjG76 | Ψ ATEBiTLkLpAYeW5hQknUfSvnb7Abbgegku
|
|
|
mika1977
|
 |
July 15, 2013, 10:32:53 AM |
|
this is my conf. file do i have to add sievesize=1000000 rpcuser=1234 rpcpassword=123 rpcport=8001 gen=1 server=1 daemon=1 rpcallowip=127.0.0.1 addnode=137.116.230.21 addnode=54.225.81.214 addnode=54.225.116.178 addnode=54.225.123.48 addnode=107.20.202.112 addnode=54.225.123.87 addnode=54.225.81.214 addnode=54.225.116.178 addnode=54.225.123.48 addnode=54.225.123.87 addnode=107.20.202.112 addnode=54.224.142.224 addnode=54.224.28.160 addnode=184.72.193.229 addnode=54.225.19.196 addnode=50.16.142.10 addnode=23.20.77.101 addnode=54.224.95.193 addnode=54.234.90.173 addnode=23.21.2.143 addnode=23.20.0.137 addnode=54.227.57.231 addnode=54.227.81.48 addnode=54.224.112.133 addnode=54.224.194.112 addnode=50.16.112.122 addnode=54.214.144.235 addnode=54.244.76.225 addnode=54.245.7.222 addnode=54.244.204.96 addnode=54.214.187.152 addnode=50.112.197.152 addnode=54.214.168.133 addnode=54.214.100.229 addnode=54.244.199.134 addnode=54.245.138.68 addnode=54.214.59.206 addnode=54.244.208.77 addnode=54.214.103.110 addnode=94.23.215.174 addnode=87.98.146.72 addnode=87.98.146.72 addnode=94.23.215.174 gen=1
|
|
|
|
|