-
Notifications
You must be signed in to change notification settings - Fork 22
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
Post-download progress #4
Comments
I had this for around 1 minute on after-download with 16GB DDR4 i5 11 4GB VRAM GTX1060 Also considering user onboarding process and stuff, probably everything will be settled after they interact with the UX. Or just got hold on a loading AI stuff. % is always confusing for me as a user. I'd prefer to know if I can use or not only. I don't think we need to know the exact moment of the process in detail. |
Hi, the download-progress section describe in the README is only a idea or is the next step? |
I don't understand this question or its relationship to this issue. |
Sorry if I don't explain myself well, I mean than in the README there is a section that refers to the download progress of the model. I would like to know if this issue is related with this task.
In cases where the model needs to be downloaded as part of creation, you can monitor the download progress (e.g. in order to show your users a progress bar) using code such as the following:
|
This issue is specifically about post-download progress, not download progress. I think the original issue explains that pretty well. |
In cases where the model is not currently available, the API gives notifications of download progress. This is meant to allow a user experience that displays a progress bar or similar.
However, in our prototyping in Chrome at least, there are other steps after the download: e.g. decompressing the model, and verifying the download. These can take some time (on the order of seconds). Should the API allow monitoring these steps, so as to let sites display their progress?
Let's keep this issue open to see if people run into this issue in practice when trying to build good user experiences. If so, we'll brainstorm what kind of API would be good to expose.
The text was updated successfully, but these errors were encountered: