Skip to content

Conversation

@siddvenk
Copy link
Contributor

@siddvenk siddvenk commented Jul 9, 2024

Description

There is quite a bit of old/outdated logic scattered throughout djl_python and our default handlers. I'll be raising PRs to slowly clear out this outdated logic.

This change removes the "auto" logic for rolling batch from out python code. This logic has been fully moved to the LmiConfigRecommender on the java side. The logic here is not up to date anymore either.

@siddvenk siddvenk requested review from a team, frankfliu and zachgk as code owners July 9, 2024 22:10
from djl_python.rolling_batch.scheduler_rolling_batch import SchedulerRollingBatch
return SchedulerRollingBatch
elif rolling_batch_type == "scheduler":
def get_rolling_batch_class_from_str(rolling_batch_type: str):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should have deprecation warning or a fallback for auto. There are still some customer setting that to auto today.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"auto" is still valid, but we just handle it here instead https://github.com/deepjavalibrary/djl-serving/blob/master/wlm/src/main/java/ai/djl/serving/wlm/LmiConfigRecommender.java#L81.

I don't think the logic here is ever invoked for "auto" in the current state.

@siddvenk siddvenk merged commit ecdc519 into deepjavalibrary:master Jul 10, 2024
@siddvenk siddvenk deleted the hf-cleanup branch July 10, 2024 17:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants