ModelArtifactConfig creation refactor #206
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.
As of #192,
StagingEngine
needs to havemodel_artifact_config
, which is created in the worker process. Creating the config in the constructor again, viaget_model_artifact_config
, is problematic for PT models since there is no build artifact for PT models (henceget_model_artifact_config
cannot be used).This PR does a refactor around how
ModelArtifactConfig
is constructed. Rather than creating it insidePagedCacheModel
, we are now creating it at the beginning of the engine initialization. So the created config can be passed to all ofStagingEngine
,StagingEngineWorker
, andSyncEngine
.Note that the same update needs to be applied to ollm in the next revision bump.
It also fixes the issue of
SamplingParams
not being verified correctly due to how it is initialized.@sunggg @yelite