Skip to content
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

set a reasonable default platform in each container #82

Closed
ssube opened this issue Jan 24, 2023 · 1 comment
Closed

set a reasonable default platform in each container #82

ssube opened this issue Jan 24, 2023 · 1 comment
Labels
status/fixed issues that have been fixed and released type/bug broken features
Milestone

Comments

@ssube
Copy link
Owner

ssube commented Jan 24, 2023

When the client does not request a specific execution provider, the server is selecting the first available one from the list, which may not be a good one. Use the default provider/platform from the params.json file.

2023-01-24T17:57:01.996197433Z 100.64.0.21 - - [24/Jan/2023 17:57:01] "POST /api/txt2img?cfg=6.00&steps=25&scheduler=euler-a&seed=-1&prompt=an+astronaut+eating+a+hamburger&negativePrompt=&model=&platform=&upscaling=&correction=&width=512&height=512 HTTP/1.1" 200 -
2023-01-24T17:57:03.026471064Z request from 100.64.0.21: 25 rounds of EulerAncestralDiscreteScheduler using /data/models/stable-diffusion-onnx-v1-5 on DmlExecutionProvider, 512x512, 6.0, 442657531 - an astronaut eating a hamburger
@ssube ssube added status/new issues that have not been confirmed yet type/bug broken features labels Jan 24, 2023
@ssube
Copy link
Owner Author

ssube commented Jan 25, 2023

This is already the case, I had the server params set to platform.default: "amd", which attempted (and failed) to use the DmlExecutionProvider. The CUDA container should not have a params file with the default set to AMD.

@ssube ssube changed the title use default execution provider from params file when client does not specify one set a reasonable default platform in each container Jan 25, 2023
@ssube ssube added this to the v0.6 milestone Jan 25, 2023
@ssube ssube closed this as completed in f4fc627 Jan 31, 2023
@ssube ssube added status/fixed issues that have been fixed and released and removed status/new issues that have not been confirmed yet labels Jan 31, 2023
@ssube ssube mentioned this issue Feb 6, 2023
68 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/fixed issues that have been fixed and released type/bug broken features
Projects
None yet
Development

No branches or pull requests

1 participant