You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: