Analyzing the gc log file is slow when the size is above 50 mb

[logesh-encipherhealth]

I use a toolkit to analyze the GC log file it takes more than 50 secs on a Linux machine and takes more than 25 secs on Mac. I gave a zip log file the original size of the log file is 90 mb after compressed it gets 9 mb. Why it takes so much time?

[karianna]

How much memory are you giving GCToolkit when you run it?

[logesh-encipherhealth]

32 gb ram and i gave the maximum heap size of 8 GB

[karianna]

OK, and do you see any warnings in the warnings.log file? It can take a lot of time to process the log lines but if we are finding lines that we can't parse that takes even longer (but we log that fact)

[logesh-encipherhealth]

only 2 warnings came

[dsgrieve]

@logesh056 The bulk of the time is spent in doing regular expression matching. There has been some effort to make this more efficient. The issue for this is #203

[logesh-encipherhealth]

Okey 👍

[dsgrieve]

Hey, @logesh056. Take PR #295 for a spin. See if it helps any.

[logesh-encipherhealth]

sure @dsgrieve

[logesh-encipherhealth]

Hey @dsgrieve can you use hyperScan to find the ruleToApply?
It stores the expression in memory and it validates parseRule fast.

[dsgrieve]

I can look into it.