Quote from: BitcoinADAB on Today at 01:27:52 AM

Quote from: yoyodapro on Today at 01:18:45 AM

my server has over 40TB of storage space and 3TB of ram, im also using the work split option on the kangaroo clients to keep the ram table low. each work file gets to about 3GB then saves to the harddrive freeing up the ram

That sounds good.
But one should always know, that kangaroo is not deterministic.

Quote from: Jean_Luc on May 29, 2020, 12:39:51 PM

...
Anyway, I'm working on the merger to reduce memory consumption.
I added the plot of probability of success:

Quote from: Jean_Luc on May 29, 2020, 07:50:05 AM

Hi,

I did a small program to calculate chance of finding the key (without taking in consideration DP overhead) after a certain number or group operation.
Each value are the result of 100.000 trials so we can expect a precision of 0.3%.

0.5*sqrt(N) P=4.606 %
1.0*sqrt(N) P=17.162 %
1.5*sqrt(N) P=34.138 %
2.0*sqrt(N) P=52.314 %
2.5*sqrt(N) P=68.049 %
3.0*sqrt(N) P=80.350 %
3.5*sqrt(N) P=88.846 %
4.0*sqrt(N) P=94.103 %
4.5*sqrt(N) P=97.164 %
5.0*sqrt(N) P=98.746 %
5.5*sqrt(N) P=99.424 %
6.0*sqrt(N) P=99.752 %

I will increase accuracy and number of point and add a nice plot to the README of the Kangaroo program.

Kangaroo never stop if not found, if DP is wrong - no luck unfortunately, JeanLuck with 1 GPU make 1 Gkey/sec around. So if someone have a 40 petakeys per second hi work 40 time faster and hi have no server for hundreds of $, if someone deduct publick keys first, hi will be more like with expensive server.