Re: Solving ECDLP with Kangaroos: Part 1 + 2 + RCKangaroo
If one really plans to break 135 there are much more factors in play in order to determine the optimal parameters to minimize the total runtime, and I'm not only talking about the command line parameters, but the kernel code itself. RC's software is just a proof of concept about his strategy, it doesn't take a genius to figure out his actual code is totally different and most likely heavily more optimized so that it fits well with his algorithm.
Yes RCKangaroo is not heavily optimized and it's actually just a proof of concept to demonstrate that K=1.15(0.99) is possible in practice, but even well-optimized version is not even twice more faster, so it's not so bad.
As for DP overhead, from the table above it may look like using DP=45 is a good idea
but of course it's not, as you have to use at least hundreds of GPUs for #135 and this table must be recalculated for the number of GPUs you use.