Java-Grok IS java regex. It is just a DSL over Java regex. It takes grok expressions ( that can reference other expressions and be compound ) and parses/resolves them and then builds one big regex out of them. Also, Groks, once parsed / used are re-used, so at that point they are like compiled regex’s.
That is not to say that that takes 0 time, but it may help you to understand. https://github.com/thekrakken/java-grok/blob/master/src/main/java/io/krakens/grok/api/Grok.java https://github.com/thekrakken/java-grok/blob/master/src/main/java/io/krakens/grok/api/GrokCompiler.java On July 11, 2018 at 07:13:38, Muhammed Irshad (irshadkt....@gmail.com) wrote: Thanks a lot Kevin for replying. Which thread are you mentioning ? The stackoverflow link ? I could not see any such option. On Wed, Jul 11, 2018 at 3:04 PM, Kevin Waterson <kevin.water...@gmail.com> wrote: > Like the thread says, the two regex engines are wildly different, however.. > you can increase the threads using -w option in grok to increase the > threads. > > Kevin > > On Wed, Jul 11, 2018 at 5:35 PM Muhammed Irshad <irshadkt....@gmail.com> > wrote: > > > Hi All, > > > > I am trying to write Java custom parser for parsing AD logs. I am > expecting > > log flow of 10 million AD events per second. Is using Java regex to parse > > benefit over using Grok parser in terms of performance ? Is there any > > performance benchmark or insights regarding the same ? > > > > I found this stackoverflow > > < > > https://stackoverflow.com/questions/43222863/logstash- > grok-filter-is-slower-than-java-regex-pattern-matching > > > > > question which inspired me for this post. > > > > -- > > Muhammed Irshad K T > > Senior Software Engineer > > +919447946359 > > irshadkt....@gmail.com > > Skype : muhammed.irshad.k.t > > > -- Muhammed Irshad K T Senior Software Engineer +919447946359 irshadkt....@gmail.com Skype : muhammed.irshad.k.t
