-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat: jumpstart instance specific hyperparameters #4180
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
Changes from 2 commits
3f29553
2f75244
891359b
c11c270
3fb6497
b2aa6cd
e587c19
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,6 +35,7 @@ def _retrieve_default_hyperparameters( | |
tolerate_vulnerable_model: bool = False, | ||
tolerate_deprecated_model: bool = False, | ||
sagemaker_session: Session = DEFAULT_JUMPSTART_SAGEMAKER_SESSION, | ||
instance_type: Optional[str] = None, | ||
): | ||
"""Retrieves the training hyperparameters for the model matching the given arguments. | ||
|
||
|
@@ -63,6 +64,8 @@ def _retrieve_default_hyperparameters( | |
object, used for SageMaker interactions. If not | ||
specified, one is created using the default AWS configuration | ||
chain. (Default: sagemaker.jumpstart.constants.DEFAULT_JUMPSTART_SAGEMAKER_SESSION). | ||
instance_type (str): An instance type to optionally supply in order to get hyperparameters | ||
specific for the instance type. | ||
Returns: | ||
dict: the hyperparameters to use for the model. | ||
""" | ||
|
@@ -86,4 +89,19 @@ def _retrieve_default_hyperparameters( | |
include_container_hyperparameters and hyperparameter.scope == VariableScope.CONTAINER | ||
) or hyperparameter.scope == VariableScope.ALGORITHM: | ||
default_hyperparameters[hyperparameter.name] = str(hyperparameter.default) | ||
|
||
instance_specific_hyperparameters = ( | ||
model_specs.training_instance_type_variants.get_instance_specific_hyperparameters( | ||
instance_type | ||
) | ||
if instance_type | ||
and getattr(model_specs, "training_instance_type_variants", None) is not None | ||
else [] | ||
) | ||
|
||
for instance_specific_hyperparameter in instance_specific_hyperparameters: | ||
default_hyperparameters[instance_specific_hyperparameter.name] = str( | ||
instance_specific_hyperparameter.default | ||
) | ||
|
||
return default_hyperparameters | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nit: rename to just |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -314,7 +314,7 @@ def _is_valid_model_id_hook(): | |
|
||
super(JumpStartModel, self).__init__(**model_init_kwargs.to_kwargs_dict()) | ||
|
||
def retrieve_all_examples(self) -> Optional[List[JumpStartSerializablePayload]]: | ||
def retrieve_all_example_payloads(self) -> Optional[List[JumpStartSerializablePayload]]: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is this example backward incompatible? If so, please provide an alias (as in There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. sure, this was a mistake from a previous PR. I'd vote to keep as is, the risk of breaking customers is very low for this new feature. We can also deprecate the old method signature There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. no please make the method name consistent with the top level utility. You can choose to remove the old method, I agree that the risk to break customers is low, but get the Python SDK to sign off on that point in that case. Alternative, use an alias for the old method and add a deprecation warn. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let me keep this as is for now. We can consider changing it later. This is a low priority issue |
||
"""Returns all example payloads associated with the model. | ||
|
||
Raises: | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would we ever want to remove a hyperparameter for a specific instance? If so, overriding the defaults may not work.
In the generated metadata, shouldn't the instance-specific hyperparameter dict contain all the fields rather than overriden ones?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point. However, to keep consistency with the environment variable variants, I think it should be additive.
In the situation you describe, the instance family or default metadata should be scoped down so that no hyperparameters need to be removed. In other words, we can construct any arbitrary hyperparameters for instances using this metadata design.