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

Add discussions about VMs vs Docker #39

Open
maxammann opened this issue May 3, 2024 · 0 comments
Open

Add discussions about VMs vs Docker #39

maxammann opened this issue May 3, 2024 · 0 comments
Assignees

Comments

@maxammann
Copy link
Contributor

The discussion centers around the choice between using virtual machines (VMs) or Docker for fuzzing tasks, particularly concerning performance and scalability. One viewpoint suggests that VMs might slow down fuzzing speed and recommends Docker for smaller or less frequent fuzzing campaigns. However, another perspective highlights problems with Docker when scaling across many cores due to the limitation of a single shared kernel instance.

The consensus appears to be that the best approach depends on specific use cases. Docker might be more efficient for fuzzing activities on a single core without needing filesystem access. On the other hand, if the fuzzing requires scaling across many cores (more than 64), VMs might be preferable despite potential concerns about the efficiency of context switches and the benefit of having multiple kernel instances. Thus, the decision between VMs and Docker for fuzzing should be guided by the specific requirements and scale of the fuzzing task at hand.

@maxammann maxammann self-assigned this May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant