Quote
[ 99] 2^29.138 Dead:2 Avg:2^28.739 DeadAvg:2.2 (1.669 2.084 sqrt(N))
Is it, the 1.669 sqrt is what my test ran versus what is expected the 2.084 sqrt?
Topic: Pollard's kangaroo ECDLP solver - page 134. (Read 58708 times)
I ran a 100 key test at the 56 Bit level, CPU only (2 cores, 2048 kangaroos), with some mods I have made to original code. I ran it in with STATS mode to see how it compares...can anyone explain these results?
Is it, the 1.669 sqrt is what my test ran versus what is expected the 2.084 sqrt?
Is it, the 1.669 sqrt is what my test ran versus what is expected the 2.084 sqrt?
True, I guess that is the choice everyone has to make...more DP for longer runtime vs "performance". I saw MrFreeDragon running 2080Tis at DP 17 for I believe 80 bit range and still getting over 1200 Mkey/s. What does your 2080Ti's rate drop down to if you go down to DP 25?
I can answer you this question when the competition is done, all my 2080ti are in work.Any way there DP size is not so important thing.
I think luck is more important here and total of GPU rigs.
Sr. Member or higher? Interesting... DP 31, seems too high.
Suggested DP for RTX 2080ti is 32, i used 31 because have some rigs rtx2070 where DP=32 is bit high.Less DP need much more memory.
It just seems with a DP of 31, it'll take a lot longer. What is the expected RAM usage at DP 31, 1 Gb?
Yes, I experimented with the different DP settings. From suggested to raising and lowering.
For your 2070 at DP 31, what is your Mkey/s rate? At DP 25, mine get between 700 and 800 Mkey/s.
if you have only 2070 it is not a problem setup DP=25, but with DP=25 and rtx2080ti you get around 950Mkeys it is to small hashrate for 2080ti
and there difference betwenn when you launch 1 GPU or rig with 6-10GPU, the speed is not the same.
True, I guess that is the choice everyone has to make...more DP for longer runtime vs "performance". I saw MrFreeDragon running 2080Tis at DP 17 for I believe 80 bit range and still getting over 1200 Mkey/s. What does your 2080Ti's rate drop down to if you go down to DP 25?
Sr. Member or higher? Interesting... DP 31, seems too high.
Suggested DP for RTX 2080ti is 32, i used 31 because have some rigs rtx2070 where DP=32 is bit high.Less DP need much more memory.
It just seems with a DP of 31, it'll take a lot longer. What is the expected RAM usage at DP 31, 1 Gb?
Yes, I experimented with the different DP settings. From suggested to raising and lowering.
For your 2070 at DP 31, what is your Mkey/s rate? At DP 25, mine get between 700 and 800 Mkey/s.
if you have only 2070 it is not a problem setup DP=25, but with DP=25 and rtx2080ti you get around 950Mkeys it is to small hashrate for 2080ti
and there difference between when you launch 1 GPU or rig with 6-10GPU, the speed is not the same.
Sr. Member or higher? Interesting... DP 31, seems too high.
Suggested DP for RTX 2080ti is 32, i used 31 because have some rigs rtx2070 where DP=32 is bit high.Less DP need much more memory.
It just seems with a DP of 31, it'll take a lot longer. What is the expected RAM usage at DP 31, 1 Gb?
Yes, I experimented with the different DP settings. From suggested to raising and lowering.
For your 2070 at DP 31, what is your Mkey/s rate? At DP 25, mine get between 700 and 800 Mkey/s.
Sr. Member or higher? Interesting... DP 31, seems too high.
Suggested DP for RTX 2080ti is 32, i used 31 because have some rigs rtx2070 where DP=32 is bit high.Less DP need much more memory.
It just seems with a DP of 31, it'll take a lot longer. What is the expected RAM usage at DP 31, 1 Gb?
Sr. Member or higher? Interesting... DP 31, seems too high.
Suggested DP for RTX 2080ti is 32, i used 31 because have some rigs rtx2070 where DP=32 is bit high.Less DP need much more memory.
It just seems with a DP of 31, it'll take a lot longer. What is the expected RAM usage at DP 31, 1 Gb?
Sr. Member or higher? Interesting... DP 31, seems too high.
Suggested DP for RTX 2080ti is 32, i used 31 because have some rigs rtx2070 where DP=32 is bit high.Less DP need much more memory.
Who know what is problem can be with 1080ti and Kangaroo.exe
Code:
GPUEngine: Launch: an illegal instruction was encountered
OS: Windows 10, i was tryed different drivers.. allways the same error. That usually means the GPU code was compiled to target a compute capability higher than what your card supports. The GTX 1080 Ti supports up to 6.1, so it would need to be compiled with sm_61,compute_61 or lower.
I do not compile programm by self. I use release from github.
Maybe this error associated with pinned memory.
I look at code and didn’t see any unusual instructions there. Only using pinned memory...
maybe somebody want exchange mastersavefile (pazzle #110 (109 bit)) with the same DP size =31 and around the same DP counter and range 2000000000000000000000000000:3FFFFFFFFFFFFFFFFFFFFFFFFFFF? . I have mastersavefile(DP=31, DP Count : 2755716 2^21.394)
Exchange available only for Sr. Member and higher
Sr. Member or higher? Interesting... DP 31, seems too high.
Who know what is problem can be with 1080ti and Kangaroo.exe
Code:
GPUEngine: Launch: an illegal instruction was encountered
OS: Windows 10, i was tryed different drivers.. allways the same error. That usually means the GPU code was compiled to target a compute capability higher than what your card supports. The GTX 1080 Ti supports up to 6.1, so it would need to be compiled with sm_61,compute_61 or lower.
I do not compile programm by self. I use release from github.
Maybe this error associated with pinned memory.
I look at code and didn’t see any unusual instructions there. Only using pinned memory...
maybe somebody want exchange mastersavefile (pazzle #110 (109 bit)) with the same DP size =31 and around the same DP counter and range 2000000000000000000000000000:3FFFFFFFFFFFFFFFFFFFFFFFFFFF? . I have mastersavefile(DP=31, DP Count : 2755716 2^21.394)
Exchange available only for Sr. Member and higher
Who know what is problem can be with 1080ti and Kangaroo.exe
Code:
GPUEngine: Launch: an illegal instruction was encountered
OS: Windows 10, i was tryed different drivers.. allways the same error. That usually means the GPU code was compiled to target a compute capability higher than what your card supports. The GTX 1080 Ti supports up to 6.1, so it would need to be compiled with sm_61,compute_61 or lower.
Who know what is problem can be with 1080ti and Kangaroo.exe
Code:
GPUEngine: Launch: an illegal instruction was encountered
OS: Windows 10, i was tryed different drivers.. allways the same error. Hello, everybody.
Does it make sense to continue the test, or is it better to end with ctrl^c and run with other parameters such as-d 22 ? The range is not known, I am looking for approximately up to ^91 inclusive.
1. Is there a chance that a collision will be found in the remaining range (Expected operations: 2^46.56 - [Count 2^45.01 ) ?
2. I have to wait a very long time, please help me-please tell me what settings are better to use ?
Please.
Thanks
c:\******.exe -d 18 -t 0 -gpu *******.txt
Kangaroo v1.5
Start:7FFFFFFFFFFEEE928C00
Stop :8000000000023E137430000
Keys :4
Number of CPU thread: 0
Range width: 2^91
Jump Avg distance: 2^45.04
Number of kangaroos: 2^20.32
Suggested DP: 25
Expected operations: 2^46.56
Expected RAM: 15097.9MB
DP size: 18 [0xFFFFC00000000000]
GPU: GPU #0 Tesla T4 (40x64 cores) Grid(80x128) (129.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^20.32 kangaroos [6.0s]
[510.43 MK/s][GPU 510.43 MK/s][Count 2^44.99][Dead 0][21:43:51 (Avg 2.4d)][4072.4/5097.0MB]
There should be balance between DP size and GPU perfomance.Does it make sense to continue the test, or is it better to end with ctrl^c and run with other parameters such as-d 22 ? The range is not known, I am looking for approximately up to ^91 inclusive.
1. Is there a chance that a collision will be found in the remaining range (Expected operations: 2^46.56 - [Count 2^45.01 ) ?
2. I have to wait a very long time, please help me-please tell me what settings are better to use ?
Please.
Thanks
Code:
c:\******.exe -d 18 -t 0 -gpu *******.txt
Kangaroo v1.5
Start:7FFFFFFFFFFEEE928C00
Stop :8000000000023E137430000
Keys :4
Number of CPU thread: 0
Range width: 2^91
Jump Avg distance: 2^45.04
Number of kangaroos: 2^20.32
Suggested DP: 25
Expected operations: 2^46.56
Expected RAM: 15097.9MB
DP size: 18 [0xFFFFC00000000000]
GPU: GPU #0 Tesla T4 (40x64 cores) Grid(80x128) (129.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^20.32 kangaroos [6.0s]
[510.43 MK/s][GPU 510.43 MK/s][Count 2^44.99][Dead 0][21:43:51 (Avg 2.4d)][4072.4/5097.0MB]
Small DP size = more GPU memory = less GPU perfomance, big DP size = more time to find expected amount of DP
And i agree that if you don`t know exist key in this range or not you should not use Kangaroo algorithm.
Kangaroo algorithm used only in case that you know that key exist in range!
You check 4 keys but if you didn’t find first the other 3 will not start to search now just one by one . If you don’t know range of search it’s impossible to find keys
Hello, everybody.
Does it make sense to continue the test, or is it better to end with ctrl^c and run with other parameters such as-d 22 ? The range is not known, I am looking for approximately up to ^91 inclusive.
1. Is there a chance that a collision will be found in the remaining range (Expected operations: 2^46.56 - [Count 2^45.01 ) ?
2. I have to wait a very long time, please help me-please tell me what settings are better to use ?
Please.
Thanks
c:\******.exe -d 18 -t 0 -gpu *******.txt
Kangaroo v1.5
Start:7FFFFFFFFFFEEE928C00
Stop :8000000000023E137430000
Keys :4
Number of CPU thread: 0
Range width: 2^91
Jump Avg distance: 2^45.04
Number of kangaroos: 2^20.32
Suggested DP: 25
Expected operations: 2^46.56
Expected RAM: 15097.9MB
DP size: 18 [0xFFFFC00000000000]
GPU: GPU #0 Tesla T4 (40x64 cores) Grid(80x128) (129.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^20.32 kangaroos [6.0s]
[510.43 MK/s][GPU 510.43 MK/s][Count 2^44.99][Dead 0][21:43:51 (Avg 2.4d)][4072.4/5097.0MB]
Does it make sense to continue the test, or is it better to end with ctrl^c and run with other parameters such as-d 22 ? The range is not known, I am looking for approximately up to ^91 inclusive.
1. Is there a chance that a collision will be found in the remaining range (Expected operations: 2^46.56 - [Count 2^45.01 ) ?
2. I have to wait a very long time, please help me-please tell me what settings are better to use ?
Please.
Thanks
Code:
c:\******.exe -d 18 -t 0 -gpu *******.txt
Kangaroo v1.5
Start:7FFFFFFFFFFEEE928C00
Stop :8000000000023E137430000
Keys :4
Number of CPU thread: 0
Range width: 2^91
Jump Avg distance: 2^45.04
Number of kangaroos: 2^20.32
Suggested DP: 25
Expected operations: 2^46.56
Expected RAM: 15097.9MB
DP size: 18 [0xFFFFC00000000000]
GPU: GPU #0 Tesla T4 (40x64 cores) Grid(80x128) (129.0 MB used)
SolveKeyGPU Thread GPU#0: creating kangaroos...
SolveKeyGPU Thread GPU#0: 2^20.32 kangaroos [6.0s]
[510.43 MK/s][GPU 510.43 MK/s][Count 2^44.99][Dead 0][21:43:51 (Avg 2.4d)][4072.4/5097.0MB]
I will be off up to the end of the next week.
I'll add the support for the -ws for client backup, this should avoid this overhead due to path breaking.
Good luck for solving #110
I'll add the support for the -ws for client backup, this should avoid this overhead due to path breaking.
Good luck for solving #110
Have a nice trip.
I will be off up to the end of the next week.
I'll add the support for the -ws for client backup, this should avoid this overhead due to path breaking.
Good luck for solving #110
Happy holidays! I'll add the support for the -ws for client backup, this should avoid this overhead due to path breaking.
Good luck for solving #110
I will be off up to the end of the next week.
I'll add the support for the -ws for client backup, this should avoid this overhead due to path breaking.
Good luck for solving #110
I'll add the support for the -ws for client backup, this should avoid this overhead due to path breaking.
Good luck for solving #110
I need more tests.
I think path breaking (when you are not using -ws) can also impact but I'm not sure.
I think path breaking (when you are not using -ws) can also impact but I'm not sure.
I'm not really surpirsed.
The key you search is the worst case.
When searching a key near to the border, you have only one half of tame and wild that overlap.
In that case you need ~22 times more DP than expected, this can happen
If you count the total number of jumps:
Each time you restart from scratch a program (or a client), you have the overhead of nbKangaroo*2^dpbit, this is the average time that each kangqroo produce a DP.
This is why you need an nbKangaroo*2^dpbit the lowest possible compare to sqrt(N).
To improve the search on the border it is possible to have a non uniform sampling and increasing kangaroo density near the border, it compensates a bit.
Maybe i am wrong but it may be better to increase the range by N beginrange-n/2 and endrange +n/2.The key you search is the worst case.
When searching a key near to the border, you have only one half of tame and wild that overlap.
In that case you need ~22 times more DP than expected, this can happen
If you count the total number of jumps:
Each time you restart from scratch a program (or a client), you have the overhead of nbKangaroo*2^dpbit, this is the average time that each kangqroo produce a DP.
This is why you need an nbKangaroo*2^dpbit the lowest possible compare to sqrt(N).
Code:
Tame: [0.......................N]
Wild: [-N/2+k..............N/2+k]
k is the key to search
To improve the search on the border it is possible to have a non uniform sampling and increasing kangaroo density near the border, it compensates a bit.
This will require twice as much time to search, but it will exclude the option that the key will be at the border and need ~22 times more DP than expected.. no?
Jump to: