-
Notifications
You must be signed in to change notification settings - Fork 30
fix: improving payload processing overhead when payload does not change #918
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
fix: improving payload processing overhead when payload does not change #918
Conversation
@launchdarkly/browser size report |
@launchdarkly/js-sdk-common size report |
@launchdarkly/js-client-sdk-common size report |
@launchdarkly/js-client-sdk size report |
🤖 I have created a release *beep* *boop* --- <details><summary>vercel-server-sdk: 1.3.34</summary> ## [1.3.34](vercel-server-sdk-v1.3.33...vercel-server-sdk-v1.3.34) (2025-09-10) ### Bug Fixes * improving payload processing overhead when payload does not change ([#918](#918)) ([be2ee75](be2ee75)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Requirements
Related issues
#907
Describe the solution you've provided
Vercel's Edge Config SDK returns the same object reference if the payload has not changed. A custom implementation of EdgeFeatureStore was added to take advantage of this and not re-reprocess the KV payload if it has not changed.