-
Notifications
You must be signed in to change notification settings - Fork 259
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
feat: make dedupe faster at I/O level. #3028
Comments
Action required: Issue inactive for 30 days. |
Issue closed after 7 days of inactivity. |
/bounty $120 |
💎 $120 bounty • Tailcall Inc.Steps to solve:
🙏 Thank you for contributing to tailcallhq/tailcall!
|
/attempt #3028
|
The bounty is up for grabs! Everyone is welcome to |
/attempt #3028 Options |
@alpha-ulrich: Reminder that in 1 days the bounty will become up for grabs, so please submit a pull request before then 🙏 |
The bounty is up for grabs! Everyone is welcome to |
💡 @alpha-ulrich submitted a pull request that claims the bounty. You can visit your bounty board to reward. |
Currently, for all deduplicated requests, we create a clone of the response, but we don't modify the cloned response. This results in redundant copies in memory and unnecessary overhead.
Proposed Solution:
Instead of cloning the response, we can keep a single copy of the response in memory and use it to construct the final response in synth. This approach will optimize both memory usage and performance by reducing duplication and overhead.
A similar approach has been implemented in PR #3025.
The text was updated successfully, but these errors were encountered: