Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b52aafaf1acb0a20808421db8099ae72@smtp.hushmail.com>
Date: Fri, 8 Feb 2019 09:05:22 +0100
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Hyperscan regex 42x the performance of pcre

On 2019-02-07 12:08, Stephen John Smoogen wrote:
> On Thu, 7 Feb 2019 at 06:04, Jason Ellison <infotek@...il.com> wrote:
>>    After reading performance comparisons of various regex engines... hscan
>> performs 42 times faster than pcre.  I'm curious as to possible performance
>> benefits of including Hyperscan into john.
>>
>> https://rust-leipzig.github.io/regex/2017/03/28/comparison-of-regex-engines/
>>
>> https://www.hyperscan.io/
>> https://github.com/intel/hyperscan
>>
> 
> Is John sitting a long time in pcre? I mean if you are spending 80
> seconds making hashes and 1 second to regex and you cut it down to 0.1
> second.. does it help any?


JtR doesn't have or use regexes at all, except when built with 
(currently experimental) regex-library but in that case all regex logic 
is in that external lib.

Hyperscan sounds interesting though. Nothing stops us (well except 
manpower) from re-implementing regex mode with that instead.

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.