-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
[Bug]: Generation sometimes slows to a crawl for all requests when there is a DRY sampler request #853
Comments
I think this has to be expected, since DRY relies on purely CPU based operation. Aphrodite needs to process one request at a time for the CPU part of the code, right? I presented two options to make DRY faster in another comment to the DRY PR, following the approach taken in ooba: allowing for a reduced dry_range and switching from tensors to lists in the CPU part of the code. |
@AlpinDale Thanks for your reactivity, very impressive ! I will look into it then. Also, do we agree that, as of now, the implementation considers the same |
I think you're right - that's a huge oversight. I'll fix ASAP. Also, I decided to try my hand at porting over the z-algorithm implementation at #856. Can you take a look? |
Fixed the sequence breaker ID issue at c6e0ae0 |
Right now, I do not see issues compared to the ooba implementation, looks faithful to the ooba implementation (just noticed 2 typos, see comments) |
DRY should be faster now but still very slow. I'm attempting to write kernels to bypass this issue. Progress will be logged here: https://github.com/AlpinDale/dry_sampling_kernel |
@Nero10578 did this PR fix the issue on your end? |
#868 partially solved this issue. DRY is a lot faster now, but not as fast as other samplers. I think we can close this issue once a new release is made. |
Your current environment
🐛 Describe the bug
Not sure how to show this but if there is a DRY sampler being processed by Aphrodite, occasionally it would slow generations down to a crawl for all the requests currently being processed and not just for the DRY sampler request.
Otherwise DRY sampler seems to be working great now!
The text was updated successfully, but these errors were encountered: