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

[maco]

you guys are a funny bunch.  I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.

The information is all available on ubu's sites, so no I don't need the professors teaching me linux.

all I am asking is for ideas to overcome it

[RandyFolds]

you guys are a funny bunch.  I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.

But did you edit primecoin.conf while primecoind was running? Could also just hard reboot, but I have no idea which build you'd end up running or how linux delineates that kind of stuff.

e: dude, I am making fun of myself. I had never used linux prior to firing up these DO droplets, but now I think I actually know the solution to your problem because I encountered it myself. Old primcoind wants old primecoin.conf.

[oroqen]

you guys are a funny bunch.  I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.

The information is all available on ubu's sites, so no I don't need the professors teaching me linux.

all I am asking is for ideas to overcome it

Seems like you may have changed rpcuser/password while daemon was still running, you could try killing it with "killall primecoind" and give it a second to close before running it again

[RandyFolds]

you guys are a funny bunch.  I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.

The information is all available on ubu's sites, so no I don't need the professors teaching me linux.

all I am asking is for ideas to overcome it

Seems like you may have changed rpcuser/password while daemon was still running, you could try killing it with "killall primecoind" and give it a second to close before running it again

See, that's what someone who know's how to use linux would tell you to do.

[maco]

you guys are a funny bunch.  I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.

The information is all available on ubu's sites, so no I don't need the professors teaching me linux.

all I am asking is for ideas to overcome it

Seems like you may have changed rpcuser/password while daemon was still running, you could try killing it with "killall primecoind" and give it a second to close before running it again

Thanks. I have tried that, but it still has the same problem. Says the info is incorrect.

I think I was using chemists build before this one. Problem is still open as I am working to find a solution. I don't think daemon is dieing, I am trying to kill the S.O.B!

[RandyFolds]

you guys are a funny bunch.  I have already noted I can access primecoin.conf
That was the whole point, because I have made the edit, and it still comes up.

The information is all available on ubu's sites, so no I don't need the professors teaching me linux.

all I am asking is for ideas to overcome it

Seems like you may have changed rpcuser/password while daemon was still running, you could try killing it with "killall primecoind" and give it a second to close before running it again

Thanks. I have tried that, but it still has the same problem. Says the info is incorrect.

I think I was using chemists build before this one. Problem is still open as I am working to find a solution. I don't think daemon is dieing, I am trying to kill the S.O.B!

Did you write a script to auto start it? If so, why not remove it and just reboot the instance?

[Tamis]

Ok i've been playing around with testnet and sievesize, the results are here : https://bitcointalk.org/index.php?topic=259641

[PSL]

Hm, I went for a reinstall for my server and it seems like there is some old data populating back.

I have used rm -f primecoin-hp/src  and rm --recursive primecoin-hp/src

However, when I reinstall and use these commands,

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


Any ideas how to fix the rpcuser problem?
I checked sudo nano ~/.primecoin/primecoin.conf  and it looks all fine.

Try this sequence:

Code:

mkdir ~/.primecoin
cat <<+++ > ~/.primecoin/primecoin.conf
rpcuser=USER
rpcpassword=PASSWORD
gen=1
+++
chmod 600 ~/.primecoin/primecoin.conf

git clone https://bitbucket.org/mikaelh/primecoin-hp.git

cd primecoin-hp/src
git pull
make -f makefile.unix clean
make -f makefile.unix USE_UPNP=-
strip primecoind
sudo cp -f primecoind /usr/local/bin/.

primecoind --daemon --server
watch 'primecoind listtransactions && primecoind getmininginfo'

[mikaelh]

/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

[Tuck Fheman]

On testnet, I found that a sievesize=6144000 outperformed every other sievesize I tried (incl. 6000000 & 6246400) by 30% using an i7.  

However, when i try to use this sievesize mining live, h5 crashes as soon as mining starts (every time).  It's unfortunate because it showed such promise on testnet.  

Blocks were coming in 4-5 chunks at a time steadily, even hit 6 blocks in 1 minute (no other setting hit above 4 blocks/min).

same here, 6144000 crashed h5 as soon as it attemps to mine on a i7 3770k with 16gb of ram.

Did you get better results on testnet with 4M than 1M ?

How do you activate testnet ? I can't check it on the debug window.

The best sievesize's I found were ...

Build - Sievesize - PPS  - Blocks in 10 minutes
HP3  - 1000000  - 7387 - 14
HP5  - 2000000  - 7092 - 14
HP5  - 4000000  - 7911 - 15 (3 at a time usually)
HP4  - 6000000  - 7819 - 15
HP4  - 6144000  - 7430 - 20
HP3  - 6553600  - 5042 - 20 (steady 2 per minute)
HP5  - 5000000  - 7815 - 22
HP5  - 6000000  - 6919 - 23
HP5  - 6144000  - 7876 - 29 (4 at a time usually + 6 in 1 minute) - same result using "-1" or "6" threads.

Nothing above 4608000 worked for me mining live w/HP5 and using higher settings live w/HP3 worked (without crashing) but was yielding very low PPS (in the hundreds) live.

I get a higher PPS @ 1M or 2M live on HP5.

I have no idea if the testnet actually "test" anything to be honest.    None of the data I collected translates over into real world mining ... especially since the client shuts down and no blocks are being found for days using the same settings that worked so well on the testnet.

So I'm trying the highest testnet settings that yielded the best results that will still work live and seeing how it goes. So far (6 hours or so, no blocks).

To answer your question ... add "-testnet" to the command line.

[Tamis]

Thanks for the details Tuck Fheman !

Here are my recent tests : https://bitcointalk.org/index.php?topic=259641.msg2772839#msg2772839

It's intersting to note that we do not have the same results with the same sievesize on testnet, that's could be cpu dependent or like you say testnet is not reliable at all.

[mikaelh]

HP5  - 6144000  - 7876 - 29 (4 at a time usually + 6 in 1 minute) - same result using "-1" or "6" threads.

Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.

[Tuck Fheman]

Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.

Thanks for that info!

[nmersulypnem]

Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.

Thanks for that info!

I think their might be some race conditions that don't exist on testnet.  Does anyone have timing numbers on how long the sieve takes to wieve and how long we have, on average, to find a block before someone else solves it?

[krikunalta]

hp5 client crashes on win 7 64bit random

[notlist3d]

hp5 client crashes on win 7 64bit random

Same here i went back to 4 after a few crashes.

[notlist3d]

Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.

Thanks for that info!

Sorry for such a newb question.  What is command to change sieve size?  I didn't see config file for it.

[Tamis]

Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.

Thanks for that info!

Sorry for such a newb question.  What is command to change sieve size?  I didn't see config file for it.

in primecoin.conf add "sievesize=...."

[notlist3d]

Use multiples of 200k for sieve size with HP5. One of the internal loops goes over 200k elements. If there's a small bug there somewhere, it might crash when sieve size is not a multiple of 200k.

Thanks for that info!

Sorry for such a newb question.  What is command to change sieve size?  I didn't see config file for it.

in primecoin.conf add "sievesize=...."

Maybe im nuts... but can u tell me where to find primecoin.conf.  Sorry again for taking up space in forum.

[Tamis]

something weird is happening with hp5, I set sievesize to 4.8M started mining and went for a nap.
Two hours later I find out the the client crashed. I try to restart it and it crashes again.
I rebooted the computer, same. I cannot put any sievesize higher than 3.6M or the client crashes as soon as it starts mining.
Was running fine a few hours ago at 4.6M and even found a block with this setting.