-
Notifications
You must be signed in to change notification settings - Fork 58
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(kv): enable auto pipelining by default #680
Conversation
BREAKING CHANGE: auto pipelining is on by default now, see https://upstash.com/docs/oss/sdks/ts/redis/pipelining/auto-pipeline. This brings performance benefits to any code making multiple redis commands simultaneously. If you detect bugs because of this, please open them at https://github.com/vercel/storage/issues. You can disable this new behavior with: ```js import { createClient } from '@vercel/kv'; const kv = createClient({ url: .., token: .., enableAutoPipelining: false }); ```
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
🦋 Changeset detectedLatest commit: c16c2db The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@upstash/[email protected] |
Great to see auto pipelining in vercel storage! We have a patch for auto-pipelining JSON commands in upstash-redis, we will release version 1.31.3 soon. |
@CahidArda updated 👍 |
We're making this a major release for safety but we believe
most applications can upgrade from 1.0.1 to 2 without any changes.
Auto pipelining should work by default and improve performance.
BREAKING CHANGE: Auto pipelining is on by default now, see
https://upstash.com/docs/oss/sdks/ts/redis/pipelining/auto-pipeline. This
brings performance benefits to any code making multiple redis commands
simultaneously.
If you detect bugs because of this, please open them at
https://github.com/vercel/storage/issues.
You can disable this new behavior with: