-
Notifications
You must be signed in to change notification settings - Fork 4
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
Inline ops that read settings #2
Conversation
5b62283
to
41338e7
Compare
src/conn/mod.rs
Outdated
Some(value) | ||
// set max_allowed_packet | ||
let max_allowed_packet = if read_max_allowed_packet { | ||
settings.as_ref().map(|s| s.1).unwrap() |
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.
Nitpick: you could get the result as a Row
and then use row::get("column_name")
. Might increase visibility, nothing blocking anyway.
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.
Good feedback, addressing.
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.
Nice! 👍
Cool, did a pass to the test suite using the same configuration defined in |
Measures taken on 100 coldstart connections to a remote RDS mysql 5.7 in us-east-1, accessed from Spain. Units are ms. Before patch: Average: 222.01605959 Standard deviation: 20.28249939282523 After patch: Average: 152.8317912 Standard deviation: 22.382571070107467 Inlining queries make connections that require reading server settings run ~30% faster.
Creating the patch first against the branch we use in prisma-engines.