Reply With QuoteI just grabbed one of my two choices, it was pretty good:
Min/Ave/Max DP distance: 0.02/15.44/122.61 GigaMD5
What are the minimum and maximum DP Distances values that you guys have noticed so far ?
My minimum is 0.13 GigaMD5.
My maximum is 30.21 GigaMD5.
I just grabbed one of my two choices, it was pretty good:
Min/Ave/Max DP distance: 0.02/15.44/122.61 GigaMD5
122.61 GigaMD5. Wow! Man, how much time did you spend on this?
1/4/16 thats what i read from my xml file
My computer has spent a lot of time, but I haven't spent that much. The clients have been running for a little over two days since I restarted after the last update. I run it with:
./md5crk > output.log &
Which in OSX or Linux puts the text that it normally puts in the console in the file output.log and then the & means that the program runs in the background. So for this I just looked in there for the min/max data.
The md5_perf.xml does just show the numbers as integers. That client has 0/15/123.
You can also run the client via ./md5crk -bg to run it in the background. Everything printed to the screen is in the md5_perf.xml file...
Originally posted by Welnic
My computer has spent a lot of time, but I haven't spent that much. The clients have been running for a little over two days since I restarted after the last update. I run it with:
./md5crk > output.log &
when i last checked the windows version if you run it with -bg the perf file does not get updated
You can also run the client via ./md5crk -bg to run it in the background. Everything printed to the screen is in the md5_perf.xml file...
It doesn, but only after a DP is found. Not very often I know - but -bg is ment for performance.Originally posted by alok
when i last checked the windows version if you run it with -bg the perf file does not get updated
should this not be a preformance talk topic
Posting Permissions