-
Notifications
You must be signed in to change notification settings - Fork 1.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
fix(cubesql): Don't clone response, improve performance #8638
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 8 Skipped Deployments
|
#[cfg(debug_assertions)] | ||
trace!("[transport] Request <- {:?}", response); | ||
#[cfg(not(debug_assertions))] | ||
trace!("[transport] Request <- <hidden>"); | ||
|
||
let load_err = match serde_json::from_value::<TransportLoadResponse>(response.clone()) { |
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.
serde_json::from_value requires passing the own of the value; it's why we used clone
here. The biggest problem is that we used it for successful responses, which is a large structure.
PR fixes that issue.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8638 +/- ##
=======================================
Coverage 82.50% 82.50%
=======================================
Files 209 209
Lines 76718 76718
=======================================
Hits 63300 63300
Misses 13418 13418
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
serde_json::from_value requires passing the own of the value; it's why we used
clone
here. The biggest problem is that we used it for successful responses, which is a large structure.PR fixes that issue.