-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
kv: investigate kv95 regression around Feb 18 #62148
Comments
Hi @tbg, please add a C-ategory label to your issue. Check out the label system docs. While you're here, please consider adding an A- label to help keep our repository tidy. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
The regression on Feb 18 was due to #59992, and was fixed by #61777. This was verified by cherry-picking the fix onto the initial PR merge, and showing that it recovered performance with This means there were other performance regressions in the period after Feb 18 that counteracted #61777. Will open a separate issue for this. |
See https://groups.google.com/a/cockroachlabs.com/d/msgid/eng/CABz5gWE%3DsO75sEtqB3MjA6ZcDqzKk%3DQhoXLVsMXkUHbtmHVuzg%40mail.gmail.com?utm_medium=email&utm_source=footer (internal) and
https://roachperf.crdb.dev/?filter=&view=kv95%2Fenc%3Dfalse%2Fnodes%3D3&tab=aws (internal).
The text was updated successfully, but these errors were encountered: