Date: Mon, 20 Feb 2012 20:38:14 +0100 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: Recent github patches On 02/07/2012 09:33 AM, Samuele Giovanni Tonon wrote: > - i added mysql-sha1, which is basically sha(sha(p)) , > on my test i saw it going faster than on cpu. any test > is really appreciated A quad-core OMP build outperforms it, there's probably a lot of optimisations that can be made. Other than that it seems to work as it should (passes test suite). > find_best_workgroup is on by default you can make it run for your > preferred format and then suppress the test by doing > export LWS=num > be aware, best LWS changes from format to format . > > find_best_kpc is off by default; you activate it by doing > export KPC=0 and, after the test you can suppress it > by doing export KPC=num . > if you don't export a KPC it will use max_keys_per_crypt. > > be aware that kpc is highly dependant on the specification of > your hardware and the format you are using. I tried this a little. First thing I noticed is if I set LWS=0 it will crash. Re-reading what you write above, you actually never said that should work :) but maybe you could treat LWS=0 as "find best" instead of crashing. Anyway, I tried find_best_kpc and it picks very small numbers (like 69632) and end up a lot slower than just going with the default 2M. I also tried manually setting 4M and that worked fine and was faster than 2M. Maybe the find_best could be enhanced somehow. Another thing I noticed is that sometimes auto-LWS picks 32 and sometimes 64, for a particular format. Maybe this is not really a problem, I just report what I see. magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.