-
Notifications
You must be signed in to change notification settings - Fork 394
feat(serve): Enhance multi-node deployment and worker configuration #457
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
Conversation
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.
the change of disagg_router.yaml
is unnecessary.
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.
Agreed with @hutm that we need to clean up the different ways env, flags, and config are manipulated in serving.py. But that can come as part of a later follow up.
if worker_envs: | ||
args.extend(["--worker-env", json.dumps(worker_envs)]) | ||
if resource_envs: | ||
args.extend(["--worker-env", json.dumps(resource_envs)]) |
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.
@mohammedabdulwahhab , @ishandhanani - still a little confused on the plural here, we are passing the full list of resource_envs to a variable that is worker-env -> singular - is that right?
its the full list for all workers that we pass here to a single process? - is this a global watcher watching all workers?
…i-dynamo#457) Co-authored-by: hongkuanz <[email protected]>
Overview
dynamo serve
to allow individual components to accept flags/configsuvloop.install()
back in. We used to have it in all of our old examples (see here)Details:
cc: #428 by @tlipoca9