-
Notifications
You must be signed in to change notification settings - Fork 126
chore: temporary fix to improve performances #1034
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
base: release/v2.1
Are you sure you want to change the base?
Conversation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
[]bunpaginate.PaginationColumnOption{ | ||
bunpaginate.WithNullsOrder(bunpaginate.NullsOrderLast), | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know that setting NULLS LAST
can affect the query plan but not being super familiar with ledger it's not particularly easy for me to grasp what kind of effect this will have.
Are we rolling this out to all customers? If it's temporary when do we roll it back?
Since the team spent the last week attempting to field customer questions about ledger performance and we struggled due to a lack of paper trail of the previous benchmarks and whatnot that had been done, I was thinking perhaps it would be nice if when you create PRs like this you could add some context?
I don't really care how it's done, but it's rough to follow these empty PR descriptions. Here are some ideas that might help remove some of the "black box" aspect of ledger:
- link to a related linear ticket or the Pylon thread with the customer conversation
- show the before/after
EXPLAIN
statements as part of the PR description - just describe what kind of impact you expect the change to have in a few words
c08b711
to
394973a
Compare
No description provided.