So, if I'm understanding it the last 3 places are cut off or will they continue to be cut off as the number grows. The reason why I'm asking is to keep track of my place. What would the correct syntax to output it to a file and would the file have it cut off or would it be correct in the file?
No the last 3 places are not cut off and the number continues to grow without hiding any numbers.
It is hard to keep track of your place because keyhunt-cuda works by dividing the global range by your grid so each thread is assigned a small chunk and each is incremented.
example if your grid is 512,512 and your global range is 3FFFFFFFF (34 bit) then that means you have 512 * 512 = 262,144 threads
so with 3FFFFFFFF(17179869183) / 262,144 = 65,535.999996185302734375 then we round to 65,536
this means each thread searches a small range of 65,536 keys.
The math is still not mathin in my head. If it was truly 661.92Mk/s it would only take a second because it's smaller than my search range 17.1 million. But if your saying it's billion then it would be even faster. So am I double checking keys at that point? So what would i need to set grid size to not double check keys? From what I see is its correctly counting because it's under my seach range 17 million. Found at 15 million.