Cache CLI calls for node instance description #952
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #949.
Description:
aws ec2 describe-instance-types --region us-west-2 --instance-types m5a.12xlarge
will run 10 times if the cluster has 10 nodes.databricks-azure
, even though we do not use CLI command, we would be reading theazure-instances-catalog.json
file for every node.This PR fixes this issue by caching the instance description calls in the CLI driver.
Changes
instance_descriptions_cache
to cache the instance type description inCMDDriverBase
_build_platform_describe_node_instance()
node.instance_type
._exec_platform_describe_node_instance(node)
that returns a single entry having the node's instance description.databricks-azure
, we would return the entireazure-instances-catalog.json
file.Testing
emr
STDOUT Before
STDOUT After
dataproc
STDOUT Before
STDOUT After
databricks-aws
STDOUT Before
STDOUT After
databricks-azure: (Multiple file reads)
STDOUT Before
STDOUT After
onprem
No Impact