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
Revisit reserved cache and memory size #1781
Comments
I had a quick conversation with Kristof about the reserved system resources. Currently we have always 100GB of ssd "reserved" for zos cache . Also a 10% with min value of 2GB of node memory is also reserved for the system. He thinks that's too much (specially the storage) and we need to revise those values. For storage, the 100G is just a subvolume quota but it's taken into consideration while calculating how much free storage is available for workloads. The problem is that the "reserved" storage amount is not reported by the node, instead it's right now known by the gridproxy and it always just assume this amount is used by the system. |
@xmonader I suggest the following to avoid minimum change to the grid
|
I think we need to implement this with #1830 because this will change what is being reported by the node as full capacity. |
Provisiond need to be aware that reserved cache size is dynamic and can change in runtime |
Currently zos reserve 100g of the ssd storage, we need to revise this value because it's too much.
Also revise the amount of reserved memory for the system
The text was updated successfully, but these errors were encountered: