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

What is the main bottleneck that causes DNSAuth to lag behind? #16

Open
mrjones-plip opened this issue Aug 6, 2018 · 0 comments
Open

What is the main bottleneck that causes DNSAuth to lag behind? #16

mrjones-plip opened this issue Aug 6, 2018 · 0 comments
Labels
enhancement New feature or request question Further information is requested
Milestone
Phase 1

Comments

@mrjones-plip
Copy link
Contributor

When writing a lot of distilled pcaps to influxdb, DNSAuth can start to lag behind real time. What is the main bottleneck that causes this lag? CPU vs IO vs RAM? Is there a way of optimizing the code so that when large .gz are thrown at DNSAuth it ingests them faster?
@mrjones-plip mrjones-plip added enhancement New feature or request question Further information is requested labels Aug 6, 2018
@mrjones-plip mrjones-plip added this to the Phase 1 milestone Aug 16, 2018
@mrjones-plip mrjones-plip changed the title What is the main bottle neck that causes DNSAuth to lag behind? What is the main bottleneck that causes DNSAuth to lag behind? Aug 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Milestone
Phase 1
Development

No branches or pull requests
1 participant
@mrjones-plip