Pages:
Author

Topic: [XPM] [ANN] Primecoin High Performance | HP14 released! - page 69. (Read 397616 times)

hero member
Activity: 742
Merit: 500
I do not understand primecoin that well at the moment, the problem with v7 would that be reflected in primemeter stats in the debug file, does anyone know?

No, it won't show up in primes/sec or chains/min. I'm guessing it's reducing block rate by about 20%.

Is this only a problem in hp7? If it is, I assume that most folks would be better off by going back to hp6.
member
Activity: 75
Merit: 10
ah - thanks for your answer  Smiley. 20% seems about right to me from the blocks I solved with v7 vs v5. I had about half my instances on v5 and half on v7.

edit: NVM I understand the debug file and why it fluctuates. the stats are calculated based on last 60 seconds of mining, then multiplied by 60 to get per hour.
sr. member
Activity: 301
Merit: 250
I do not understand primecoin that well at the moment, the problem with v7 would that be reflected in primemeter stats in the debug file, does anyone know?

No, it won't show up in primes/sec or chains/min. I'm guessing it's reducing block rate by about 20%.
member
Activity: 75
Merit: 10
thanks for all the work mikaelh, I will send some XPC tomorrow because I've been using your miner. I compiled with your latest updates and will see how many blocks I solved in a while...

I do not understand primecoin that well at the moment, the problem with v7 would that be reflected in primemeter stats in the debug file, does anyone know?

BTW the measurements on the primemeter lines are about the same I think  for compiled with recent commits from bitbucket vs v7. . the numbers are "per hour" but fluctuate a lot which doesn't make sense really.

i

NEW
2013-07-25 11:00:44 primemeter  11620189 prime/h  99396927 test/h       480 5-chains/h
2013-07-25 11:01:44 primemeter   8731912 prime/h  73598147 test/h       300 5-chains/h
2013-07-25 11:03:26 primemeter   6473749 prime/h  53716243 test/h       420 5-chains/h
2013-07-25 11:04:26 primemeter  11358263 prime/h  94857756 test/h       360 5-chains/h
2013-07-25 11:05:26 primemeter  10517945 prime/h  86684575 test/h       540 5-chains/h
2013-07-25 11:06:26 primemeter   6861122 prime/h  56816904 test/h       300 5-chains/h
2013-07-25 11:07:26 primemeter   7530512 prime/h  62189498 test/h       480 5-chains/h
2013-07-25 11:08:26 primemeter  11711653 prime/h  97222796 test/h       480 5-chains/h
2013-07-25 11:09:26 primemeter  10724171 prime/h  91132990 test/h       600 5-chains/h
2013-07-25 11:10:26 primemeter  10896501 prime/h  95608657 test/h       540 5-chains/h
2013-07-25 11:11:26 primemeter  11080172 prime/h  92579202 test/h       660 5-chains/h
2013-07-25 11:12:26 primemeter  10947355 prime/h  90129236 test/h       900 5-chains/h
2013-07-25 11:13:26 primemeter  10639445 prime/h  87377427 test/h       600 5-chains/h
2013-07-25 11:14:26 primemeter  11264090 prime/h  94878948 test/h       360 5-chains/h
2013-07-25 11:15:26 primemeter  11257125 prime/h  93178274 test/h       420 5-chains/h
2013-07-25 11:16:26 primemeter  10974868 prime/h  93342587 test/h       540 5-chains/h
2013-07-25 11:17:26 primemeter  10785060 prime/h  94334568 test/h       720 5-chains/h
2013-07-25 11:18:26 primemeter   9667875 prime/h  83818672 test/h       420 5-chains/h
2013-07-25 11:19:26 primemeter  11297512 prime/h  96529571 test/h       540 5-chains/h
2013-07-25 11:20:26 primemeter  11927047 prime/h 101064994 test/h       480 5-chains/h
2013-07-25 11:21:26 primemeter  11032266 prime/h  96171180 test/h       480 5-chains/h
2013-07-25 11:22:26 primemeter  10354207 prime/h  89454202 test/h       480 5-chains/h
2013-07-25 11:23:26 primemeter  11900447 prime/h 102212426 test/h       540 5-chains/h
2013-07-25 11:24:26 primemeter  11404850 prime/h  98671475 test/h       480 5-chains/h
2013-07-25 11:25:26 primemeter   9602519 prime/h  84853689 test/h       300 5-chains/h
2013-07-25 11:26:26 primemeter   9281489 prime/h  78998684 test/h       360 5-chains/h
2013-07-25 11:27:26 primemeter   8884255 prime/h  75387586 test/h       240 5-chains/h

V7

2013-07-25 11:00:14 primemeter  12709168 prime/h 102728788 test/h       420 5-chains/h
2013-07-25 11:01:14 primemeter  12230125 prime/h  96631178 test/h       480 5-chains/h
2013-07-25 11:02:14 primemeter   9534801 prime/h  74242523 test/h       720 5-chains/h
2013-07-25 11:03:14 primemeter  11987920 prime/h  97475875 test/h       360 5-chains/h
2013-07-25 11:04:14 primemeter  12769249 prime/h 104281388 test/h       360 5-chains/h
2013-07-25 11:05:14 primemeter  12493744 prime/h  99081597 test/h       660 5-chains/h
2013-07-25 11:06:14 primemeter  11579987 prime/h  96437593 test/h       420 5-chains/h
2013-07-25 11:07:14 primemeter  12332598 prime/h  98128858 test/h       660 5-chains/h
2013-07-25 11:08:14 primemeter  11683786 prime/h  95558717 test/h       480 5-chains/h
2013-07-25 11:09:14 primemeter   8767002 prime/h  70311084 test/h       420 5-chains/h
2013-07-25 11:10:14 primemeter  12229069 prime/h  97593820 test/h       780 5-chains/h
2013-07-25 11:11:14 primemeter  12784167 prime/h 102993623 test/h       840 5-chains/h
2013-07-25 11:12:14 primemeter  11273512 prime/h  90101818 test/h      1020 5-chains/h
2013-07-25 11:13:14 primemeter   9378264 prime/h  75669719 test/h       180 5-chains/h
2013-07-25 11:14:14 primemeter  11606913 prime/h  97411733 test/h       420 5-chains/h
2013-07-25 11:15:14 primemeter  11406520 prime/h  94552468 test/h       480 5-chains/h
2013-07-25 11:16:14 primemeter  13122741 prime/h 106142671 test/h       600 5-chains/h
2013-07-25 11:17:14 primemeter  13195040 prime/h 106230149 test/h       660 5-chains/h
2013-07-25 11:18:14 primemeter  11849023 prime/h  96649509 test/h       660 5-chains/h
2013-07-25 11:19:14 primemeter  13291085 prime/h 106534624 test/h       660 5-chains/h
2013-07-25 11:20:14 primemeter  12262307 prime/h  97869387 test/h       540 5-chains/h
2013-07-25 11:21:14 primemeter  12022898 prime/h  97095967 test/h       240 5-chains/h
2013-07-25 11:22:14 primemeter  10369642 prime/h  82206150 test/h       420 5-chains/h
2013-07-25 11:23:14 primemeter  13693115 prime/h 109174861 test/h       300 5-chains/h
2013-07-25 11:24:14 primemeter   9506542 prime/h  78578050 test/h       360 5-chains/h
2013-07-25 11:25:14 primemeter   8806506 prime/h  72187974 test/h       240 5-chains/h
2013-07-25 11:26:14 primemeter   5864129 prime/h  45733931 test/h       300 5-chains/h
sr. member
Activity: 301
Merit: 250
I am currently testing the latest commits, it seems that the PPS indicator is very low compared to the value before, more than halved my numbers and chainspermin is 0 mostly all the time.
I will keep on testing, meanwhile, is anybody else testing the CURRENT version and seeing the same results out there ?

Can you post more information about your system and the which exact versions you are comparing?
hero member
Activity: 637
Merit: 500
I am currently testing the latest commits, it seems that the PPS indicator is very low compared to the value before, more than halved my numbers and chainspermin is 0 mostly all the time.
I will keep on testing, meanwhile, is anybody else testing the CURRENT version and seeing the same results out there ?
sr. member
Activity: 301
Merit: 250
@mikaelh: Why not merge your code with Sunny King's? He stated that it's due to licensing problems with libgmp (can't find the source), but I think that this is wrong. libgmp is LGPL, not GPL, and can therefore be used even in closed-source projects provided that you link to it only dynamically. Which primecoind does, so you would be fine even if primecoin would be closed-source.

Well, technically my Windows builds have been using static linking. It can be changed to dynamic linking. x86 will take a minor performance hit from that but x64 should be fine.

Even if the licensing concerns are solved through dynamic linking, it's still Sunny King's call whether he wants the code or not.
hero member
Activity: 518
Merit: 502
@mikaelh: Why not merge your code with Sunny King's? He stated that it's due to licensing problems with libgmp (can't find the source), but I think that this is wrong. libgmp is LGPL, not GPL, and can therefore be used even in closed-source projects provided that you link to it only dynamically. Which primecoind does, so you would be fine even if primecoin would be closed-source.
sr. member
Activity: 476
Merit: 250
That indeed explains a lot !
96 hours without a block...

I'm thinking about all those that are paying a fortune for vps and were mining at difficulty = 10
legendary
Activity: 1792
Merit: 1008
/dev/null
Does this mean that people with hp7 that find blocks are effectively at difficulty 10?

That would certainly explain my long dryspell...
yes
member
Activity: 95
Merit: 10
That guy, you know, with the face
Does this mean that people with hp7 that find blocks are effectively at difficulty 10?

That would certainly explain my long dryspell...
sr. member
Activity: 301
Merit: 250
I might have found a bug in hp7. I copied the hp7 code over to Reaper, and found some weird behavior. I noticed that many shares/blocks it found, had a difficulty with a fractional part of 0.

Function: FermatProbablePrimalityTestFast. It does a Fermat test, and if it fails, it calculates the fractional part. However, there's a fast division test before the Fermat test. If the fast division test is succesful, the function is returned from and the fractional part isn't calculated. If it just happened to be the last number in a chain, the fractional part isn't calculated and is left at 0. This means if the difficulty is for example 6.2, and the miner found a block of difficulty 6.3, it's possible that the fractional part was left uncalculated, and the miner thinks it's difficulty 6.0. The block doesn't get submitted and lots of profit has been lost.

The same applies to EulerLagrangeLifchitzPrimalityTestFast.

Right now I don't have git set up, I can't submit a patch.

Good catch! Letting that one slip was definitely a big oversight on my part. I pushed my own fix to bitbucket just now. I don't have time to do a release right now so it'll have to wait for a bit. In the meantime the fix is up there for testing.
member
Activity: 96
Merit: 10
Four desktops found nothing for 3 days.
Does the Primecoin client support pool mining now? thx

Only one pool exists for now: http://ypool.net/

Looks odd to me

I'm sure it took some hard work to be the first pool.
sr. member
Activity: 294
Merit: 250
+1 8bitPunk

I might have found a bug in hp7. I copied the hp7 code over to Reaper, and found some weird behavior. I noticed that many shares/blocks it found, had a difficulty with a fractional part of 0.

Function: FermatProbablePrimalityTestFast. It does a Fermat test, and if it fails, it calculates the fractional part. However, there's a fast division test before the Fermat test. If the fast division test is succesful, the function is returned from and the fractional part isn't calculated. If it just happened to be the last number in a chain, the fractional part isn't calculated and is left at 0. This means if the difficulty is for example 6.2, and the miner found a block of difficulty 6.3, it's possible that the fractional part was left uncalculated, and the miner thinks it's difficulty 6.0. The block doesn't get submitted and lots of profit has been lost.

The same applies to EulerLagrangeLifchitzPrimalityTestFast.

Right now I don't have git set up, I can't submit a patch.

Is this the specific change that causes the bug you are referring to: https://bitbucket.org/mikaelh/primecoin-hp/commits/64528eba386c948e4e63d50b9eb6c1a500bac4ca ?

Here's the original comment explaining why it should work: https://bitcointalksearch.org/topic/m.2787426

What are your thoughts?

mtrlt replied that this commit is not what he was referring to, and the commit is after the hp7 tag which mtrlt pulled into his project.

I believe he is referring to the code below - which appears around lines 556 & 606:
Code:
if (lRemainder % vPrimes[nPrimeSeq] == 0)
return false;

This code returns false without first calculating the fractional part, exactly as mtrlt explained. I'm testing a fix and will let mikaelh know if it works.
member
Activity: 70
Merit: 10
I might have found a bug in hp7. I copied the hp7 code over to Reaper, and found some weird behavior. I noticed that many shares/blocks it found, had a difficulty with a fractional part of 0.

Function: FermatProbablePrimalityTestFast. It does a Fermat test, and if it fails, it calculates the fractional part. However, there's a fast division test before the Fermat test. If the fast division test is succesful, the function is returned from and the fractional part isn't calculated. If it just happened to be the last number in a chain, the fractional part isn't calculated and is left at 0. This means if the difficulty is for example 6.2, and the miner found a block of difficulty 6.3, it's possible that the fractional part was left uncalculated, and the miner thinks it's difficulty 6.0. The block doesn't get submitted and lots of profit has been lost.

The same applies to EulerLagrangeLifchitzPrimalityTestFast.

Right now I don't have git set up, I can't submit a patch.

Is this the specific change that causes the bug you are referring to: https://bitbucket.org/mikaelh/primecoin-hp/commits/64528eba386c948e4e63d50b9eb6c1a500bac4ca ?

Here's the original comment explaining why it should work: https://bitcointalksearch.org/topic/m.2787426

What are your thoughts?

mtrlt replied that this commit is not what he was referring to, and the commit is after the hp7 tag which mtrlt pulled into his project.

I believe he is referring to the code below - which appears around lines 556 & 606:
Code:
if (lRemainder % vPrimes[nPrimeSeq] == 0)
return false;

This code returns false without first calculating the fractional part, exactly as mtrlt explained. I'm testing a fix and will let mikaelh know if it works.
sr. member
Activity: 266
Merit: 250
Four desktops found nothing for 3 days.
Does the Primecoin client support pool mining now? thx

Only one pool exists for now: http://ypool.net/

Looks odd to me
full member
Activity: 314
Merit: 100
I might have found a bug in hp7. I copied the hp7 code over to Reaper, and found some weird behavior. I noticed that many shares/blocks it found, had a difficulty with a fractional part of 0.

Function: FermatProbablePrimalityTestFast. It does a Fermat test, and if it fails, it calculates the fractional part. However, there's a fast division test before the Fermat test. If the fast division test is succesful, the function is returned from and the fractional part isn't calculated. If it just happened to be the last number in a chain, the fractional part isn't calculated and is left at 0. This means if the difficulty is for example 6.2, and the miner found a block of difficulty 6.3, it's possible that the fractional part was left uncalculated, and the miner thinks it's difficulty 6.0. The block doesn't get submitted and lots of profit has been lost.

The same applies to EulerLagrangeLifchitzPrimalityTestFast.

Right now I don't have git set up, I can't submit a patch.

Is this the specific change that causes the bug you are referring to: https://bitbucket.org/mikaelh/primecoin-hp/commits/64528eba386c948e4e63d50b9eb6c1a500bac4ca ?

Here's the original comment explaining why it should work: https://bitcointalksearch.org/topic/m.2787426

What are your thoughts?
legendary
Activity: 1764
Merit: 1018
Four desktops found nothing for 3 days.
Does the Primecoin client support pool mining now? thx

Only one pool exists for now: http://ypool.net/
sr. member
Activity: 784
Merit: 250
DIA | Data infrastructure for DeFi
Is anyone just running hp7 at default?

What, if any, are the preferred changes for i72600 and AMD FX830?
sr. member
Activity: 266
Merit: 250
I don't know how that can affect your wallet  Sad . I'm using different wallets in each miner and dump the private keys every time a block it's found, then I restore the keys on my "money PC" where I only run the official client. After that I stop primecoind on the miner, delete the wallet and restart the client.

I know this is a odd question ptox, but did that affect my wallet? I was using the same wallet for a couple of my servers. I used the keypool=10000 command. Because before HP6/7 I mined 2 blocks in 1 hour then upgraded to 6/7 and nothing so far. (the blocks occurred 2 days ago) and do you know if its okay to use keypool? or should I generate a new address? I was happy with HP5, and never had a single thing wrong with it.

According to the first post:

 Changes in -hp6:
 * Added fast divisibility tests before doing the expensive Fermat's test

I guess by just reverting to hp5 we can get around the bug while hp8 appears online.

So do we have to wait for the next update to get this problem solved?

I might have found a bug in hp7. I copied the hp7 code over to Reaper, and found some weird behavior. I noticed that many shares/blocks it found, had a difficulty with a fractional part of 0.

Function: FermatProbablePrimalityTestFast. It does a Fermat test, and if it fails, it calculates the fractional part. However, there's a fast division test before the Fermat test. If the fast division test is succesful, the function is returned from and the fractional part isn't calculated. If it just happened to be the last number in a chain, the fractional part isn't calculated and is left at 0. This means if the difficulty is for example 6.2, and the miner found a block of difficulty 6.3, it's possible that the fractional part was left uncalculated, and the miner thinks it's difficulty 6.0. The block doesn't get submitted and lots of profit has been lost.

The same applies to EulerLagrangeLifchitzPrimalityTestFast.

Right now I don't have git set up, I can't submit a patch.

Thanks mtrlt... the code you copied is all the commits up to the tag 'v0.1.1xpm-hp7' or including more recent commits in the last 16 hours?

Mikaelh has been changing this section of the code to avoid calculating the fractional part when the chain length was insufficient to pass the difficulty. e.g. commit 64528eb & 27c3cdf
Pages:
Jump to: