I just went from v5 to v7 and now my prime rate is halved. Anyone else having this? Is it because of the optomizations made (ie. more efficient/accurate)?
Also, I have set: -sievesize=4000000
but when I view stats with getmininginfo it always says its on 1M not 4M?
Well, there's a couple of things you can check (added these to the FAQ):
1. Make sure you're not using the 32-bit version which is slower.
2. Don't compare prime rate against a lower network difficulty. Difficulty went over 9 couple of days ago. Everyone's hash rate dropped by about 30%.
In general prime rate should not go down between releases as long as they are being compared against the same network difficulty. If someone has experienced a drop that is not explained by the previous two points, then please post some information about your system.
If -sievesize is not working, then you're putting it in the wrong place. EDIT: I also updated the FAQ concerning this.
I am definitely using the 64 bit version as I had previously.
My prime rate was 2400 with v5 then I extracted v7 and ran it, only gets 1200-1300 now. It only took me 1 minute to extract the new version and change the target I run, this is not comparing between days.
I was trying to get 4M sievesize with this shortcut command to start it:
C:\Windows\System32\cmd.exe /c start "runlow" /low C:\primecoin-0.1.1-hp7-winx64\primecoin-qt.exe -gen -setgenerate true -sievesize=4000000
But as I said it wasn't working: The problem was simply that
-setgenerate true was supposed to be
-setgenerate=true. Now the parameter after it (sievesize) works properly:
except... it crashes on 4M. So I have it running on 2M right now:
C:\Windows\System32\cmd.exe /c start "runlow" /low C:\primecoin-0.1.1-hp7-winx64\primecoin-qt.exe -gen -setgenerate=true -sievesize=2000000
Doublecheck that you don't have sievesize set in your primecoin.conf file?
I dont use or have a primcoin.conf file.
I just went from v5 to v7 and now my prime rate is halved. Anyone else having this? Is it because of the optomizations made (ie. more efficient/accurate)?
Also, I have set: -sievesize=4000000
but when I view stats with getmininginfo it always says its on 1M not 4M?
I believe that when you set sievesize from the command line, you need to leave a space between the switch and the value for it to parse correctly, i.e., "-sievesize 4000000". If you are setting it in your .conf file, then you need the '=' sign.
As I found, it seems that when using parameters in a shortcut's target field, you must use = sign instead of the space.
https://i.imgur.com/d7qiw8W.jpg