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

Speed printouts are inaccurate #14

Closed
deepfates opened this issue Jun 21, 2021 · 1 comment
Closed

Speed printouts are inaccurate #14

deepfates opened this issue Jun 21, 2021 · 1 comment
Labels
bug Something isn't working

Comments

@deepfates
Copy link
Owner

The print commands to stdout are not helpful to the end user. They need to be refactored to take into account the entire length of the process, including loading the db and processing the images.

Related: the GUI loads the db anew for each search, as well as importing all the modules and CLIP model. What if they were loaded separately, using a different Flow than the ones in 00_core?

@deepfates deepfates added the bug Something isn't working label Jun 21, 2021
@deepfates
Copy link
Owner Author

Fixed this temporarily by wrapping the whole queryFlow. In future, a better system of logging and display is obviously necessary. I've made an enhancement issue for that at #15 and for the GUI upgrade at #16. Closing this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant