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.

Sign up for GitHub

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

Jump to bottom

Optimize max records to load #1175

Closed
YamatoSecurity opened this issue Sep 7, 2023 · 0 comments · Fixed by #1176
Closed

Optimize max records to load #1175

YamatoSecurity opened this issue Sep 7, 2023 · 0 comments · Fixed by #1176
Assignees
@YamatoSecurity
Labels
enhancement New feature or request
Milestone
v2.9.0

Comments

@YamatoSecurity
Copy link
Collaborator

MAX_DETECT_RECORDS, the variable that determines how many records to load and scan at a time is defined as 5000 but I performed some benchmarks to find the optimal number. I think it is difficult to find a perfect number but 1000 seems to be a better value:

Screenshot 2023-09-07 163125
@YamatoSecurity YamatoSecurity added the enhancement New feature or request label Sep 7, 2023
@YamatoSecurity YamatoSecurity added this to the v2.9.0 milestone Sep 7, 2023
@YamatoSecurity YamatoSecurity self-assigned this Sep 7, 2023
@YamatoSecurity YamatoSecurity mentioned this issue Sep 7, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@YamatoSecurity YamatoSecurity

Labels
enhancement New feature or request
Projects
None yet
Milestone
v2.9.0
Development

Successfully merging a pull request may close this issue.

optimize max detect records Yamato-Security/hayabusa
1 participant
@YamatoSecurity