-
Notifications
You must be signed in to change notification settings - Fork 96
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
Benchmarks & speeds and improvements #90
Comments
Hi, I just ran Zircolite on 15 GB of EVTX files (Sysmon, Security etc.) :
For the same dataset, Hayabusa took 8 min. Both tools use alot of memory. The main part of Zircolite (the detection process) is only performed on one CPU Core. I am currently working on a way to speed things up by using all the cores. |
Almost same as hayabusa ..
Below 15 min is not bad at all. The memory usage is high 15GB EVTX ~30GB - 45GB memory
I will look closely the code. I assume only one python file.
Best
… On 21 Oct 2024, at 18:46, Wagga ***@***.***> wrote:
Hi,
I just ran Zircolite on 15 GB of EVTX files (Sysmon, Security etc.) :
With multiple files and the use of GNU Parallel, It took 1 min 41 s with 2723 rules
By using Zircolite on all the files at once, it took 9 min 54s with 2723 rules (from the sigma official repository) on Python 3.10 (newer version of Python will be faster).
For the same dataset, Hayabusa took 8 min. Both tools use alot of memory.
The main part of Zircolite (the detection process) is only performed on one CPU Core. I am currently working on a way to speed things up by using all the cores.
—
Reply to this email directly, view it on GitHub <#90 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEFRZHZQURQZLGUSLMAUPSLZ4UOUDAVCNFSM6AAAAABQJ53CJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRXGA2TSMJZGY>.
You are receiving this because you authored the thread.
|
Thanks.
For the aforementioned test, without GNU Parallel, memory usage peaked at 25 GB. |
Just to let you know that the future version of zircolite takes 1 min 51 s to execute with the same 15 GB dataset on the very same computer. |
@wagga40 is it 1 core or multiple core result 1 min 51 s ? sqlite insert looks last longer.. |
multiple cores. |
You should not focus to much on SQLite Insertion, on the actual version (single core) for the same dataset takes only 25 secs... Most of the execution time is on executing rules. |
When are you going to release new version :) ?
… On 25 Oct 2024, at 17:55, Wagga ***@***.***> wrote:
sqlite insert looks last longer..
You should not focus to much on SQLite Insertion, on the actual version (single core) for the same dataset takes only 25 secs...
—
Reply to this email directly, view it on GitHub <#90 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEFRZH6NM3TEGTXCGZ75PCLZ5JLU7AVCNFSM6AAAAABQJ53CJSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZYGA2DEMZSHE>.
You are receiving this because you authored the thread.
|
I still have some things I need to adjust but I think this week end. |
Hi,
I cam a cross your project today and wll have a try.
We wonder the benchmarks of the processing 2000 sigma rules over 5gig log ie ? Do you have such benchmarks ?
How we can improve the processing speed ? We can re-write critical part in c++ if it helps ?
Best
The text was updated successfully, but these errors were encountered: