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

Sfast optimization for T2I , I2I and Upscale models #134

Open
wants to merge 41 commits into
base: main
Choose a base branch
from

Conversation

JJassonn69
Copy link
Contributor

Implementation was straight forward from the already written code. But the testing took most of the time. Maybe its because my A5000 was slow or something, it would take forever to load and compile the model for sfast.

for T2I most of the models worked.

Best was ByteDance/SDXL_Lightning with total iteration time of 441s, 1st warmup was 386s and second was only 55s. Inference time of 5.10s/it for first image and it sped it up 4.65it/s for subsequent images.

Worst was SG161222/RealVisXL_V4.0_Lightning with total iteration time of unknows, 1st warmup was 1600s and second was was incomplete even after 55minutes. Inference time of unknown for first image and it sped it up unknown for subsequent images.

for I2I I couldnot get SDXL or SD_turbo to work. Neither did timbrooks/instruct-pix2pix.

for upscale the only model available was stabilityai/stable-diffusion-x4-upscaler but that didnt compile with sfast, even single iteration of compile would take forever. I left it for an hour but it only moved couple of steps. So I will need to make more tests to see if the issue is with models or hardware.

Conclusion: some models took insanely long to pre trace so I dont think that would be a good for anyone. Maybe if there was a way to precompile and save to memory so that you could instantly switch between precompiled models instead of compiling it each time you load the models.

jjassonn and others added 30 commits July 26, 2024 01:30
… with creating go api bindings because of openapi json sceme having a null option.
* update to the frame interpolation pipeline, there is some minor issue with creating go api bindings because of openapi json sceme having a null option.

* minor changes to requirements

* update to requrements to fetch from --index-url

* simple patch to solve the go api bindings issue

* checking if it works in my system

---------

Co-authored-by: Jason Stone <ganesh.panth2012@gmail.com>
Bumps the go_modules group with 1 update in the / directory: [github.com/docker/docker](https://github.com/docker/docker).


Updates `github.com/docker/docker` from 24.0.7+incompatible to 24.0.9+incompatible
- [Release notes](https://github.com/docker/docker/releases)
- [Commits](moby/moby@v24.0.7...v24.0.9)

---
updated-dependencies:
- dependency-name: github.com/docker/docker
  dependency-type: direct:production
  dependency-group: go_modules
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* update to the frame interpolation pipeline, there is some minor issue with creating go api bindings because of openapi json sceme having a null option.

* minor changes to requirements

* update to requrements to fetch from --index-url

* simple patch to solve the go api bindings issue

* checking if it works in my system

---------

Co-authored-by: Jason Stone <ganesh.panth2012@gmail.com>
@JJassonn69
Copy link
Contributor Author

This is the testing result for the sfast uptimised models vs normal.
Screenshot 2024-07-31 at 12 04 04 AM

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