-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Description
This feature request is included in this year's Diffusers Hacktoberfest 🎃!
Hacktoberfest's purpose is to give upcoming open-source developers the opportunity to learn about open-source and programming by fixing simple issues (like this one).
How to solve the issue:
-
- Every issue has a description further below explaining the problem. First, you should try to understand the issue.
-
- Second, follow the contribution guide to learn how to contribute to Diffusers.\
-
- Claim this issue for you by opening a PR that links to this issue and writing, "I am solving this issue in
<link-to-pr>".
- Claim this issue for you by opening a PR that links to this issue and writing, "I am solving this issue in
Issue
We want to run our fast tests run faster. But what is a fast test for a pipeline, though?
This class holds all fast tests here:
| class StableDiffusionXLPipelineFastTests(PipelineLatentTesterMixin, PipelineTesterMixin, unittest.TestCase): |
The idea of this issue is to try to identify if the pipeline components (such as the UNet, text encoders, VAE) could be made smaller without disturbing the correctness of the tests.
For example, could we reduce the number of blocks in the UNet? This is how the UNet is initialized:
| unet = UNet2DConditionModel( |
Similar idea could be applied to the VAE, and text encoders (one, two).
As a consequence of making the pipeline components smaller, the expected assertion values (example) might change but it should not impact the correctness of the test, whatsoever.
Cc: @DN6