go-libaudit icon indicating copy to clipboard operation
go-libaudit copied to clipboard

Create a stress test

Open andrewkroh opened this issue 7 years ago • 3 comments

There should be a stress test framework to find the limits of the library with and without the parser in the loop.

andrewkroh avatar Apr 11 '17 22:04 andrewkroh

It would be nice to benchmark the parser by itself to see what kind of throughput it has. Based on those results we could consider whether it would be worth it to try writing a parser with https://www.colm.net/open-source/ragel/ or https://github.com/alecthomas/participle.

(edit: I did a ragel spike in https://github.com/andrewkroh/go-libaudit/tree/ragel-parser. Not much of a change in perf.)

andrewkroh avatar Jun 25 '18 21:06 andrewkroh

any updates on the test? I'm looking forward to see performance comparison of Auditbeat and similar tools like Falco

danmx avatar Jun 07 '20 10:06 danmx

@danmx I don't see something like that happening. The project suddenly seems to have some activity, other than that, it's been stale for around a year.

andanotherusername avatar Jun 07 '20 14:06 andanotherusername