Date: Tue, 29 Jan 2013 11:46:57 +0100 From: atom <atom@...hcat.net> To: john-dev@...ts.openwall.com Subject: Re: DCC2 performance The default values are all set individually for each algorithm / gpu-vendor. There is no algorithm behind which tries to evaluate the theoretical best value. It is all hardcoded. If the desktop starts lagging I am lowering these defaults for gpu-accel and gpu-loops until the desktop runs lagfree (plus some spare value). This gives the -new- user a good first impression of stability and when he gains more experience with the program he finds out how to manually override this for maximum performance. Especially for slow hashes like DCC2 and WPA I am setting them to extreme low values. They produce more load to the overall System because there is no candidate attack amplifier on GPU. This generates more load to the Disc, since it has to load more data, and more load to the bus because it has to copy this data. On Tue, Jan 29, 2013 at 3:58 AM, Solar Designer <solar@...nwall.com> wrote: > Hi atom, > > On Mon, Jan 28, 2013 at 04:39:41PM +0100, atom wrote: >> But for oclHashcat-plus default workload settings are a trademark >> between cracking speed and desktop lags. That is for all hashes not >> just DCC2. > > Thank you for explaining this. > > I did not expect you'd be OK with the speed being as low as ~70% of max > by default. I thought the default would be above 90% of max. > > Alexander -- atom email: atom@...hcat.net web: http://hashcat.net/
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.