[XPM] Primecoin Built-in Miner Sieve Performance Issue

[Eli0t]

Here's another binary I've made which targets simply x86-64 processors. This SHOULD work over a wider range of processors than my earlier releases. It may not work on 32-bit OSes (not sure).

https://www.dropbox.com/s/q7w4fosqjyqydff/release8_x86-64.zip

stuck at 2 blocks synced no matter how many connections i have

received block 9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488
SetBestChain: new best=9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488  height=1  difficulty=7 log2Work=13  log2ChainWork=13.044394  tx=2  date=2013-07-07 18:28:00 progress=0.000000
ProcessBlock: ACCEPTED
received block 7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34
SetBestChain: new best=7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34  height=2  difficulty=7 log2Work=13  log2ChainWork=14.022368  tx=3  date=2013-07-07 18:29:58 progress=0.000000
ProcessBlock: ACCEPTED
received block b22946daedabb93d4e9e28945278fd3d9f7ec601ce4aba1a25e6e203cf6fa41f
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 192.241.209.212:9911 (0 -> 100) DISCONNECTING

Try using -debug and -printtarget and post the ERROR messages about block #3 being rejected again

im now synced and would prefer not to go back to an unsynced state, maybe the next person with this problem can try that

[1714005801]

1714005801

[1714005801]

1714005801

[1714005801]

1714005801

[1714005801]

1714005801

[Jimmy2011]

I started the 5# release successfully after complete synchronization with the original client, and the block number increases well at a rate about one block every 15 seconds.

[Zalfrin]

Here's another binary I've made which targets simply x86-64 processors. This SHOULD work over a wider range of processors than my earlier releases. It may not work on 32-bit OSes (not sure).

https://www.dropbox.com/s/q7w4fosqjyqydff/release8_x86-64.zip

stuck at 2 blocks synced no matter how many connections i have

received block 9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488
SetBestChain: new best=9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488  height=1  difficulty=7 log2Work=13  log2ChainWork=13.044394  tx=2  date=2013-07-07 18:28:00 progress=0.000000
ProcessBlock: ACCEPTED
received block 7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34
SetBestChain: new best=7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34  height=2  difficulty=7 log2Work=13  log2ChainWork=14.022368  tx=3  date=2013-07-07 18:29:58 progress=0.000000
ProcessBlock: ACCEPTED
received block b22946daedabb93d4e9e28945278fd3d9f7ec601ce4aba1a25e6e203cf6fa41f
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 192.241.209.212:9911 (0 -> 100) DISCONNECTING

Try using -debug and -printtarget and post the ERROR messages about block #3 being rejected again

This gave me a little hint. FYI sunny, the code this was built from is here, it is slightly modified from your latest commit to include some additional suggested optimizations from Mike270. https://github.com/Zalfrin/primecoin

There may be a bug in the way the "phash" variable is replacing "pblock->GetHeaderHash();". Maybe phash needs to be updated within the loop starting on line 4640 of main.cpp

[UNOE]

I just realized I have 6 blocks but all 6 blocks have zero confirmations its this normal ?

[Zalfrin]

I just realized I have 6 blocks but all 6 blocks have zero confirmations its this normal ?

No, sounds like your qt is not following the block chain. Should increment by 1 for every block the network finds.

[gateway]

Here's another binary I've made which targets simply x86-64 processors. This SHOULD work over a wider range of processors than my earlier releases. It may not work on 32-bit OSes (not sure).

https://www.dropbox.com/s/q7w4fosqjyqydff/release8_x86-64.zip

stuck at 2 blocks synced no matter how many connections i have

received block 9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488
SetBestChain: new best=9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488  height=1  difficulty=7 log2Work=13  log2ChainWork=13.044394  tx=2  date=2013-07-07 18:28:00 progress=0.000000
ProcessBlock: ACCEPTED
received block 7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34
SetBestChain: new best=7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34  height=2  difficulty=7 log2Work=13  log2ChainWork=14.022368  tx=3  date=2013-07-07 18:29:58 progress=0.000000
ProcessBlock: ACCEPTED
received block b22946daedabb93d4e9e28945278fd3d9f7ec601ce4aba1a25e6e203cf6fa41f
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 192.241.209.212:9911 (0 -> 100) DISCONNECTING

Try using -debug and -printtarget and post the ERROR messages about block #3 being rejected again

This gave me a little hint. FYI sunny, the code this was built from is here, it is slightly modified from your latest commit to include some additional suggested optimizations from Mike270. https://github.com/Zalfrin/primecoin

There may be a bug in the way the "phash" variable is replacing "pblock->GetHeaderHash();". Maybe phash needs to be updated within the loop starting on line 4640 of main.cpp

I'm also suck at 2 blocks 3 days behind.. any thoughts?

[Zalfrin]

Here's another binary I've made which targets simply x86-64 processors. This SHOULD work over a wider range of processors than my earlier releases. It may not work on 32-bit OSes (not sure).

https://www.dropbox.com/s/q7w4fosqjyqydff/release8_x86-64.zip

stuck at 2 blocks synced no matter how many connections i have

received block 9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488
SetBestChain: new best=9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488  height=1  difficulty=7 log2Work=13  log2ChainWork=13.044394  tx=2  date=2013-07-07 18:28:00 progress=0.000000
ProcessBlock: ACCEPTED
received block 7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34
SetBestChain: new best=7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34  height=2  difficulty=7 log2Work=13  log2ChainWork=14.022368  tx=3  date=2013-07-07 18:29:58 progress=0.000000
ProcessBlock: ACCEPTED
received block b22946daedabb93d4e9e28945278fd3d9f7ec601ce4aba1a25e6e203cf6fa41f
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 192.241.209.212:9911 (0 -> 100) DISCONNECTING

Try using -debug and -printtarget and post the ERROR messages about block #3 being rejected again

This gave me a little hint. FYI sunny, the code this was built from is here, it is slightly modified from your latest commit to include some additional suggested optimizations from Mike270. https://github.com/Zalfrin/primecoin

There may be a bug in the way the "phash" variable is replacing "pblock->GetHeaderHash();". Maybe phash needs to be updated within the loop starting on line 4640 of main.cpp

I'm also suck at 2 blocks 3 days behind.. any thoughts?

Eli0t had success using the last official client from Sunny to sync up the blockchain, then switching over to my release for mining.

I'll be investigating the sync-up problem in my version... I'm working on getting a second computer to recreate the problem. The ancient Pentium 4M computer I tried out was not happy, but it didn't make it as far as downloading ANY of the block chain.

[tjb0607]

Here's another binary I've made which targets simply x86-64 processors. This SHOULD work over a wider range of processors than my earlier releases. It may not work on 32-bit OSes (not sure).

https://www.dropbox.com/s/q7w4fosqjyqydff/release8_x86-64.zip

stuck at 2 blocks synced no matter how many connections i have

received block 9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488
SetBestChain: new best=9657908608eeddce30390a30ac72b3348fd584c1b3cb917922707f9cfc01a488  height=1  difficulty=7 log2Work=13  log2ChainWork=13.044394  tx=2  date=2013-07-07 18:28:00 progress=0.000000
ProcessBlock: ACCEPTED
received block 7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34
SetBestChain: new best=7edd2add999ca4a7d3c6abbe827a9aa19ea3e0e782e80c299d22599a29ec1f34  height=2  difficulty=7 log2Work=13  log2ChainWork=14.022368  tx=3  date=2013-07-07 18:29:58 progress=0.000000
ProcessBlock: ACCEPTED
received block b22946daedabb93d4e9e28945278fd3d9f7ec601ce4aba1a25e6e203cf6fa41f
ERROR: AcceptBlock() : incorrect proof of work
ERROR: ProcessBlock() : AcceptBlock FAILED
Misbehaving: 192.241.209.212:9911 (0 -> 100) DISCONNECTING

Try using -debug and -printtarget and post the ERROR messages about block #3 being rejected again

This gave me a little hint. FYI sunny, the code this was built from is here, it is slightly modified from your latest commit to include some additional suggested optimizations from Mike270. https://github.com/Zalfrin/primecoin

There may be a bug in the way the "phash" variable is replacing "pblock->GetHeaderHash();". Maybe phash needs to be updated within the loop starting on line 4640 of main.cpp

I'm also suck at 2 blocks 3 days behind.. any thoughts?

Try running these commands in the console:

Code:

addnode 94.23.215.174 add
addnode 87.98.146.72 add

EDIT: Or, if that doesn't work, here's some more you can try until the blockchain starts synchronizing:

Code:

addnode 54.225.81.214 add
addnode 54.225.116.178 add
addnode 54.225.123.48 add
addnode 107.20.202.112 add
addnode 54.225.123.87 add
addnode 54.225.81.214 add
addnode 54.225.116.178 add
addnode 54.225.123.48 add
addnode 54.225.123.87 add
addnode 107.20.202.112 add
addnode 54.224.142.224 add
addnode 54.224.28.160 add
addnode 184.72.193.229 add
addnode 54.225.19.196 add
addnode 50.16.142.10 add
addnode 23.20.77.101 add
addnode 54.224.95.193 add
addnode 54.234.90.173 add
addnode 23.21.2.143 add
addnode 23.20.0.137 add
addnode 54.227.57.231 add
addnode 54.227.81.48 add
addnode 54.224.112.133 add
addnode 54.224.194.112 add
addnode 50.16.112.122 add
addnode 54.214.144.235 add
addnode 54.244.76.225 add
addnode 54.245.7.222 add
addnode 54.244.204.96 add
addnode 54.214.187.152 add
addnode 50.112.197.152 add
addnode 54.214.168.133 add
addnode 54.214.100.229 add
addnode 54.244.199.134 add
addnode 54.245.138.68 add
addnode 54.214.59.206 add
addnode 54.244.208.77 add
addnode 54.214.103.110 add

[UNOE]

Sadly I closed the client and then reopened and the blocks are gone.

Even though they where all there after a shutdown and restart before that now they are all gone after closing the program and reopening it.

[Aggrophobia]

Sadly I closed the client and then reopened and the blocks are gone.

Even though they where all there after a shutdown and restart before that now they are all gone after closing the program and reopening it.

Open it with rescan

[Zalfrin]

Sadly I closed the client and then reopened and the blocks are gone.

Even though they where all there after a shutdown and restart before that now they are all gone after closing the program and reopening it.

That's because they all got orphaned. Your client was off mining on it's own, unfortunately.

[gateway]

btw my issue was no primecoin.conf was created.. so it was stuck at 2 blocks.. once I manually created it it started getting blocks for anyone else dealing with this issue

[Zalfrin]

btw my issue was no primecoin.conf was created.. so it was stuck at 2 blocks.. once I manually created it it started getting blocks for anyone else dealing with this issue

That is.... intriguing. I wonder if it was that, or just restarting the client?

[gateway]

btw my issue was no primecoin.conf was created.. so it was stuck at 2 blocks.. once I manually created it it started getting blocks for anyone else dealing with this issue

That is.... intriguing. I wonder if it was that, or just restarting the client?

What I did.. download original client from primecoin.org, ran the installer, DID NOT run the app when it was, downloaded one from dropbox, copied over the files and ran it..

so maybe its not doing creating the primecoin.conf init if you do it that way.

BTW whats the latest release..   Core i7

[Zalfrin]

btw my issue was no primecoin.conf was created.. so it was stuck at 2 blocks.. once I manually created it it started getting blocks for anyone else dealing with this issue

That is.... intriguing. I wonder if it was that, or just restarting the client?

What I did.. download original client from primecoin.org, ran the installer, DID NOT run the app when it was, downloaded one from dropbox, copied over the files and ran it..

so maybe its not doing creating the primecoin.conf init if you do it that way.

BTW whats the latest release..   Core i7

I'm using release5 on my sandy bridge i5. anonppcoin compiled a version that was targeted specifically at the i7-family as well.

[gateway]

btw just talked to Luke-Jr, he started a bfgminer branch for prime if anyone wants to work on that or compile versions..

https://github.com/luke-jr/bfgminer/tree/prime

[x3maniac]

btw just talked to Luke-Jr, he started a bfgminer branch for prime if anyone wants to work on that or compile versions..

https://github.com/luke-jr/bfgminer/tree/prime

do you know if it is going to cpu only or with gpu support?

[UNOE]

Sadly I closed the client and then reopened and the blocks are gone.

Even though they where all there after a shutdown and restart before that now they are all gone after closing the program and reopening it.

That's because they all got orphaned. Your client was off mining on it's own, unfortunately.

It said I had 8 active connections ?

[Ptah]

This is my build, I used -O2 -march=native, I'm running a FX 8350, it gives me ~1250 PPS on that. I placed all the dlls in the rar. Please do your virus check and everything, I compiled that on a VM but still take precautions running a file made by another person.

https://www.dropbox.com/s/6hycwi0i4dzwu1i/Primecoin.rar

PII 6x 1045 @3GHz

5 threads 550-750 pps

THX

[n4ru]

So what's the most optimized miner out right now?