Use generic trades query for owner endpoint#110
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd the label add-to-gt-merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
6ef2cb1 to
b4fac6d
Compare
b4fac6d to
f4de41e
Compare
28254bc to
ff1f985
Compare

Summary
GET /v1/trades/{owner}through the genericget_tradesSDK path with an owner filterBenchmark context
Local benchmark against the bootstrapped DB showed the owner-specific SDK path taking roughly 3-4s for 20-row pages. Using the generic owner-filtered trades query reduced the same endpoint to roughly 1-2.7s while keeping the same pagination totals.
Validation
nix develop -c cargo fmtnix develop -c cargo checknix develop -c rainix-rs-static