06-11-2012, 02:30 PM
(06-11-2012, 02:18 PM)fizikalac Wrote: I have the same problem as this guy: http://erratasec.blogspot.com/2012/06/li...cking.html
Quote:Use --remove. Oh, I found the source of the problem: I was using original file on the faster processor, which is twice as large as the one cut down removed the "zeroed" hashes. Memory lookups on GPUs are slower with the larger amount of memory. Thus, shrinking the file makes a big difference in speed. I wonder if splitting the file into small chunks that fit better within the GPU cache might work better.
I get it, yes, but when you crack large amount of hashes like LinkedIn leak, you can experience such lag... Using more rules could help, yes, I will try that.
Thank you for the link, you have answered your own question !
Are you working on the linkedin list ? So am I, I'll PM you.