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

Allow the "scan-socket" volume to be moved into memory and/or persistent volume storage #49

Closed
jdftapi opened this issue Jun 27, 2024 · 2 comments · Fixed by #50
Closed

Comments

@jdftapi
Copy link

jdftapi commented Jun 27, 2024

When running GDScan on a k8s node with suboptimal HDD storage performance, be it through storage type or through neighbouring pods, the performance of the scanner can be degraded by the HDD bottleneck due to the fact that the scan socket always resides on the node.

It would be great to have the possibility of putting the scan socket volume into Memory or onto a custom disk using a persistent volume claim.

@oOoHoCo
Copy link

oOoHoCo commented Jun 28, 2024

Hello there,

wouldn't it be a bit better to have the possibility to even move thos mounts to PVCs because if you have it in memory and want to scan large files (e.g. a zip file that contains logs ... will be huge when decompressed) the memory could pose a limit that you do not want.

Regards,

Ben

@jdftapi
Copy link
Author

jdftapi commented Jun 28, 2024

It would be great to have both possibilities, as the performance of the storage can be limited even on PVCs, depending on the environment.

For most use cases, PVC should be preferable, I agree.

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

Successfully merging a pull request may close this issue.

2 participants