I understand your suggestion, but I think we should not enforce that decision, if a given user
wants to use a dataset-size of 100GB on a 32GB machine, then is up to the operator, there are many assumptions
that we could be doing wrong ( perhaps is adding Swap memory? or stressing an installation?).
I think the best we can do on that case is to warn the user about his decision.
if dataset_bytes > self.get_mem_total(): log("Dataset has been set to a value greater than the available RAM", level=WARN)
Also offering the option to manually adjust the dataset-size and innodb_buffer_pool_size to a specific memory amount
would be enough for covering most of the use cases.
Mario,
I understand your suggestion, but I think we should not enforce that decision, if a given user
wants to use a dataset-size of 100GB on a 32GB machine, then is up to the operator, there are many assumptions
that we could be doing wrong ( perhaps is adding Swap memory? or stressing an installation?).
I think the best we can do on that case is to warn the user about his decision.
if dataset_bytes > self.get_ mem_total( ):
log( "Dataset has been set to a value greater than the available RAM",
level= WARN)
Also offering the option to manually adjust the dataset-size and innodb_ buffer_ pool_size to a specific memory amount
would be enough for covering most of the use cases.
Opinions?