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

Progress in app + sys mem fallback fix #76

Merged
merged 3 commits into from
Oct 13, 2024

Conversation

Ednaordinary
Copy link
Contributor

This adds a progress bar in the app as well as adding a fix for flooding into system memory.

Previously, cache "stepped up" as the process continued, which de-allocated when it reached the max amount. When sys mem fallback is enabled, the ceiling is raised so it doesn't de-allocate and instead enters system memory.

Step up effect is shown here:
Screenshot from 2024-10-12 20-33-23

This fix collects cache after each step, stopping this effect:
Screenshot from 2024-10-12 20-43-57

Also, added a progress bar and pipeline callback:
Screenshot from 2024-10-12 20-44-06

@Ednaordinary Ednaordinary mentioned this pull request Oct 13, 2024
@FurkanGozukara
Copy link

Awesome work

@feifeiobama
Copy link
Collaborator

Thank you for the pull request. Just one small concern: does it slow down the generation significantly by calling gc.collect() and torch.cuda.empty_cache() at every step?

@Ednaordinary
Copy link
Contributor Author

It does slow generation down, though I'm not sure by how much. Testing now.

@Ednaordinary
Copy link
Contributor Author

Without this PR: 441.83 sec
With this PR: 449.57 sec

About 8 second at 16 steps

@feifeiobama
Copy link
Collaborator

feifeiobama commented Oct 13, 2024

Without this PR: 441.83 sec With this PR: 449.57 sec

About 8 second at 16 steps

This seems acceptable, I will merge it. Thanks again.

@feifeiobama feifeiobama merged commit c8789cf into jy0205:main Oct 13, 2024
@dillfrescott
Copy link

Mine is still flooding into system memory and its slowing the generation down to nearly a halt.

I opened this issue about it: #86

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.

4 participants