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 Neo4j #1452

Open
TheTechromancer opened this issue Jun 12, 2024 · 0 comments
Open

Optimize Neo4j #1452

TheTechromancer opened this issue Jun 12, 2024 · 0 comments
Assignees
@TheTechromancer
Labels
enhancement New feature or request

Comments

@TheTechromancer
Copy link
Collaborator

TheTechromancer commented Jun 12, 2024 •
edited
Loading

@t94j0 I did some testing with Neo4j, and you're right that it's slow to insert events. In big scans especially, when the events are really flooding in, the Neo4j queue can get backed up.

To fix this, we'll need to figure out how to batch the cypher statements.
@TheTechromancer TheTechromancer added the enhancement New feature or request label Jun 12, 2024
@TheTechromancer TheTechromancer self-assigned this Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TheTechromancer TheTechromancer

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@TheTechromancer