Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a stress test #2

Open
andrewkroh opened this issue Apr 11, 2017 · 3 comments
Open

Create a stress test #2

andrewkroh opened this issue Apr 11, 2017 · 3 comments

Comments

@andrewkroh
Copy link
Member

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

@andrewkroh
Copy link
Member Author

andrewkroh commented Jun 25, 2018

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.)

@danmx
Copy link

danmx commented Jun 7, 2020

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

@andanotherusername
Copy link

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants