Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 24 May 2012 22:09:01 +0200
From: Frank Dittrich <>
Subject: Re: memory usage within JtR and possible ways to significantly
 reduce it.

On 05/24/2012 09:33 PM, jfoug wrote:
> The hot/cold does makes a lot of sense. Very good way to try to keep the
> locality.  For a 10 million candidate search, you still have 40mb of hot
> memory and 120mb of 'cold' memory, vs 160mb of arbitrary accessed memory.  I
> am not sure that reducing from 160mb to 40mb will have that 'huge' of a
> help, but it might.

I think this is more aimed at a smaller number of hashes.
If only about 25% of the memory is hot, then you have about 4 times the
number of hashes which can be cracked faster because all hot memory fits
into some cache.


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.