Skip to content
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

Improve vault endpoint performance. #2475

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

vincentwschau
Copy link
Contributor

@vincentwschau vincentwschau commented Oct 4, 2024

Changelist

Fetch funding index update maps in bulk rather than one at a time per vault.

Test Plan

Unit tests.

Author/Reviewer Checklist

  • If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
  • If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
  • If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
  • If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
  • If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
  • Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

  • New Features

    • Introduced a new method to retrieve funding index maps for multiple effective heights, enhancing data retrieval capabilities.
  • Bug Fixes

    • Optimized the getVaultPositions function for improved performance in fetching funding index maps.
  • Documentation

    • Updated method signatures and interfaces for better clarity and usability.
  • Refactor

    • Streamlined data retrieval logic in the VaultController to enhance efficiency and readability.

@vincentwschau vincentwschau requested a review from a team as a code owner October 4, 2024 18:57
Copy link
Contributor

coderabbitai bot commented Oct 4, 2024

Walkthrough

The changes in this pull request introduce enhancements to the FundingIndexUpdatesTable and VaultController. A new method, findFundingIndexMaps, is added to the FundingIndexUpdatesTable to allow for the retrieval of funding index maps based on multiple effective heights. Additionally, the getVaultPositions function in the VaultController is restructured to optimize the retrieval of funding index maps by implementing a batch retrieval approach, improving efficiency in data handling.

Changes

File Change Summary
indexer/packages/postgres/src/stores/funding-index-updates-table.ts Introduced findFundingIndexMaps method and FundingIndexUpdatesFromDatabaseWithSearchHeight interface. Modified findFundingIndexMap to remove a constant.
indexer/services/comlink/src/controllers/api/v4/vault-controller.ts Restructured getVaultPositions for batch retrieval of funding index maps, simplifying internal logic and improving performance.
indexer/packages/postgres/__tests__/stores/funding-index-updates-table.test.ts Added a test case for findFundingIndexMaps to verify functionality with multiple effective heights.

Possibly related PRs

Suggested labels

feature:indexer/affiliates

Suggested reviewers

  • tqin7

Poem

🐰 In the fields where indices play,
New tests bloom in bright array.
Funding maps now dance with glee,
Vaults retrieve with harmony.
Hops of code, a joyful sight,
Enhancements bring the data light! 🌟


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 56d77c5 and aecac36.

📒 Files selected for processing (1)
  • indexer/packages/postgres/src/stores/funding-index-updates-table.ts (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • indexer/packages/postgres/src/stores/funding-index-updates-table.ts

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 5

🧹 Outside diff range and nitpick comments (3)
indexer/packages/postgres/__tests__/stores/funding-index-updates-table.test.ts (1)

246-278: LGTM! Comprehensive test case for findFundingIndexMaps.

This new test case thoroughly covers the functionality of the findFundingIndexMaps method, aligning well with the PR's objective of improving vault endpoint performance. It tests multiple scenarios including different block heights, multiple perpetual IDs, and updates at various effective heights.

To improve readability, consider extracting the expected values into constants at the beginning of the test case. This would make the assertions more clear and easier to maintain.

Here's a suggestion for improving readability:

const expectedFundingIndices = {
  '3': {
    [defaultFundingIndexUpdate.perpetualId]: Big(defaultFundingIndexUpdate.fundingIndex),
    [fundingIndexUpdates3.perpetualId]: Big(fundingIndexUpdates3.fundingIndex),
  },
  '6': {
    [defaultFundingIndexUpdate.perpetualId]: Big(fundingIndexUpdates2.fundingIndex),
    [fundingIndexUpdates3.perpetualId]: Big(fundingIndexUpdates3.fundingIndex),
  },
};

// ... (rest of the test case)

Object.entries(expectedFundingIndices).forEach(([blockHeight, indices]) => {
  Object.entries(indices).forEach(([perpetualId, expectedIndex]) => {
    expect(fundingIndexMaps[blockHeight][perpetualId]).toEqual(expectedIndex);
  });
});

This approach centralizes the expected values and makes the assertions more concise and easier to update if needed.

indexer/packages/postgres/src/stores/funding-index-updates-table.ts (2)

243-244: Optimize retrieval of minHeight

Currently, minHeight is obtained after sorting the entire array of heights, which has a time complexity of O(n log n). Since only the minimum value is needed, consider using Math.min to improve performance.

Apply this diff to optimize the retrieval:

 const heightNumbers: number[] = effectiveBeforeOrAtHeights
   .map((height: string) => {
     const parsedHeight = parseInt(height, 10);
     if (isNaN(parsedHeight)) {
       throw new Error(`Invalid block height: ${height}`);
     }
     return parsedHeight;
-  })
-  .sort();
+  });

-// Get the min height to limit the search to blocks 4 hours or before the min height.
-const minHeight: number = heightNumbers[0];
+// Get the min height without sorting the entire array.
+const minHeight: number = Math.min(...heightNumbers);

283-285: Add a semicolon at the end of the statement

In line 284, the statement is missing a semicolon, which could lead to linting errors or unintended behavior.

Apply this diff to add the missing semicolon:

 for (const funding of result.rows) {
   fundingIndexMaps[funding.searchHeight][funding.perpetualId] = Big(funding.fundingIndex)
-}
+};
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 264cb06 and 0c73339.

📒 Files selected for processing (3)
  • indexer/packages/postgres/tests/stores/funding-index-updates-table.test.ts (1 hunks)
  • indexer/packages/postgres/src/stores/funding-index-updates-table.ts (2 hunks)
  • indexer/services/comlink/src/controllers/api/v4/vault-controller.ts (3 hunks)
🔇 Additional comments (2)
indexer/packages/postgres/__tests__/stores/funding-index-updates-table.test.ts (1)

Line range hint 1-278: Overall, excellent test coverage and alignment with PR objectives.

The test suite in this file provides comprehensive coverage for the FundingIndexUpdatesTable, including various scenarios and edge cases. The newly added test case for findFundingIndexMaps complements the existing tests well and directly supports the PR's goal of improving vault endpoint performance through bulk fetching of funding index update maps.

The structure of the tests is consistent, making the suite easy to understand and maintain. This thorough testing approach will help ensure the reliability of the new functionality and reduce the risk of regressions.

indexer/services/comlink/src/controllers/api/v4/vault-controller.ts (1)

378-394: Performance Improvement with Bulk Fetching of Funding Index Maps

Fetching funding index maps in bulk using findFundingIndexMaps enhances performance by reducing the number of individual database calls. This optimization is beneficial when dealing with multiple subaccounts and aligns with the PR's objective to improve endpoint performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants