Quote from: wyldfire on September 05, 2013, 07:01:47 PM

Quote from: y0m0 on September 05, 2013, 06:51:01 PM

Quote from: pgbit on September 05, 2013, 05:09:37 PM

Quote from: mtrlt on September 05, 2013, 04:43:12 PM

I've made the primality tester 4-5x faster, but I haven't managed to fix the "fractional assert" problem. Should I just release the faster version (many people won't be able to use it) or try to fix the bug first (will take time)?

If this is of any help, looking at the console as all the data flies by, my setup (i7 chip, win8, 64bit) reels out all the data, starting with 0 fermats/sec and 786 gandalfs/s, then as time passes, the gandalfs/s progressively drops and if the app doesnt crash earlier each time the console reports the gandalfs/s it shows a smaller and smaller number, reducing to 60 gandalfs/s then it usually gives up and passes onto windows error reporting. It always only shows 0 fermats/s - ? what is this meant to be?

I had this same issue with the gandalfs dropping and I managed to keep it at a regular average number by playing around with the "worksize" parameter in the primecoin.conf , got the best result with 64

I can confirm worksize of 64 was optimal for me too.

This does seem a improvement - thanks - this time runs from 1 - 5 mins.